Ship marketing pages without waiting
Acme Cloud gives your team a page builder their engineers never have to touch without waiting on a deploy. Editors compose pages from typed sections; the site still builds to static HTML.
Trusted by teams shipping every day
Everything the Acme Cloud team keeps asking engineering for
Eleven section types cover the range a real site needs — simple content, repeatable lists, nested panels and interactive UI.
Static by default
Pages render to plain HTML at build time. No runtime rendering cost, no cold starts.
One block, one component
Every CMS block maps 1:1 to a typed React component. The schema cannot drift.
Live preview
Edits stream into the real frontend as you type, rendered by the production components.
Draft and publish
Versioned drafts with autosave. Nothing goes live until someone hits publish.
Many sites, one library
Each brand is a tenant with its own content, palette and navigation — sharing these components.
Structured data included
FAQ and pricing blocks emit schema.org JSON-LD automatically for SEO and AEO.
Built for the whole team
Add a section, fill in the fields, watch it render. No tickets, no deploy queue, and no way to break the layout — every section is a component with a contract.
- Reorder sections by dragging
- Duplicate a section to A/B a variant
- Autosaved drafts, published on your schedule
Pricing Plans
Simple, predictable pricing
Every plan includes the full component library and unlimited pages.
Starter
The essentials for a small team getting a first site live.
$0 /month
Add-on packs available to customise plan
- Up to 3 editors
- 25 published pages
- Community support
Growth
Everything a growing team needs to publish without limits.
$79 /month
Add-on packs available to customise plan
- Unlimited editors
- Unlimited pages and drafts
- Scheduled publishing
- Priority support
Enterprise
Governance and oversight for a multi-brand operation.
Custom billed annually
Add-on packs available to customise plan
- SSO and audit logs
- Multi-brand workspaces
- Dedicated environment
- 99.95% uptime SLA
Paying big? Try Transformation. With pay per use pricing
Customisation of the plan and solution to meet special risk and compliance management needs.
We went from a two-week turnaround on landing pages to publishing the same afternoon. The engineers never had to touch it.
More from teams who made the switch
Our designers finally own the design system, and the CMS just reflects it. Nobody files a ticket to change a headline any more.
Frequently asked questions
No. Editors see a list of named sections with plain-language fields. The component code, prop types and styling stay entirely on the engineering side.
See the editing loop in two minutes
How the pieces fit together
The content model lives in the CMS, the rendering lives in a shared component library, and each site is a thin layer that maps one to the other.
The three packages
- packages/ui — typed React section components, the single source of truth for props
- apps/cms — Payload blocks generated from those prop types, scoped per tenant
- apps/web — Astro routes that dispatch each block to its component
Add a prop to a component and the CMS stops compiling until the field exists. That is the whole trick.
The dispatch itself is unremarkable, which is the point:
const Component = blockRegistry[block.blockType]
return <Component {...block} />Curious about the implementation? Read the source or open apps/web/src/components/BlockRenderer.astro.
Get started
Give the Acme Cloud marketing team the keys to their own pages
Spin up the sample locally, add a section, and watch it appear on the frontend.