Product

Version the whole project, then promote.

Build the next structure and its content in a release, preview it, and switch atomically.

Creating a release in ZevContent, with a Start from menu set to the live release so the new one begins as a copy

How it works.

Start a release from what is live

It begins as a copy, including every link between entries, so nothing is half-migrated.
Preview it

Point a preview deployment at the release. Nobody else sees a thing until you promote it.
Promote in one step

Readers see the old version, then the new one. Never half of each.

Preview before promoting: Point a deployment at a release with one query parameter.
Atomic switch: Readers see the old version, then the new one. Never half of each.
Clone and edit: A release starts as a copy, including every link between entries.
One event when it lands: release.published tells a cache that everything may have changed.

1: query parameter to preview the next version
1: step to promote it
0: readers who see half of each

Next, in the product.

Custom contentYour own types and fields.WebhooksNineteen events, every one signed.BlogArticles, authors, categories, SEO.

Read it as.

DevelopersREST, JSON, and a schema you can read.FoundersRun a real site without hiring for it.

Start with a project and a key.

Free while we are in beta. Paid plans when we ship them, and never a surprise bill.

Start free Read the docs