Build on Cedros
Build the difference. Reuse the foundations.
Start with a website platform that already has publishing, customer tools, and an assistant. Add the custom experience your business needs through pages, themes, and extensions.
Explore plans /pricing See the platform /about
Four ways to make it yours
Custom pages
Create interactive React pages for calculators, onboarding, product experiences, and other bespoke interfaces. Keep the implementation within the runtime’s supported dependencies and provide its other content surfaces.
Shared templates
Define a page family once, then give each page its own content. Designers can improve the shared layout while authors work in the fields that matter for their page.
Themes and brand settings
Set the site’s visual foundations through theme tokens and brand settings. Keep colors, typography, and shared surfaces consistent while allowing the content to change.
Extensions
Use existing Cedros extensions or build functionality against the extension contract. Define the required data, capabilities, and services so custom behavior has a clear place in the platform.
Bring code with a clear adaptation path
An existing React experience may fit a custom page; server-side behavior may belong in an extension. Review dependencies, persistence, permissions, and integrations before deciding how to convert a codebase.
Keep the next surface in reach
Cedros also provides app-building workflows and multi-surface content representations. Native delivery requires its own configuration, testing, and developer accounts where store distribution is involved.
Useful to know
Do I have to code to use Cedros?
No. Use Page Builder and built-in tools for standard work. Custom code is available when the project requires it.
Can I deploy an arbitrary backend unchanged?
No. Cedros has a supported runtime and extension contract. Adapt custom behavior to those boundaries.
Can my coding assistant work with Cedros?
Compatible clients can use the site’s MCP endpoint and scoped business tools. The built-in assistant can also help with supported authoring workflows.
Start ahead, then keep building.
Use Cedros for the common foundations and your code for what makes the product different.
Talk about your website /contact
