A CMS staging environment for every client website.
Development and Production on every website. Your team edits in Development, gathers the work into a Release that reads like a pull request, and publishes website changes with approval before they touch the live site.
Environments
Development and Production, on every website.
A CMS with development and production environments built in. Content never jumps straight to the live site: Production only changes when a Release merges.
Edit here
Development
- Pages, sections, content models and forms you are working on
- Checkouts locked to the person editing them
- Test leads that clear after 30 days
- Its own domains, API keys and webhooks
Live site
Production
- The live site the public API serves
- Read-only for pages, content and form definitions
- Real leads the team works every day
- Its own domains, API keys and webhooks
Shared by both
- Team members and their access levels
- The media library
- Website settings (name, status, primary domain)
Content release management
From a checkout to the next Production version.
Content release management that feels like a pull request: you own what you ship, the diff shows what will change, and merging is the only way Production moves forward.
- 1
Clone to Development
Copy a live page, item or form into Development with the same id. It locks to you until the Release merges or you discard it.CheckoutSame id - 2
Edit safely
Change structure or content in Development. Collaborators you invite save against a version check, so nobody overwrites anyone else.PagesItemsForms - 3
Open a Release
Pick which of your checkouts to ship. Dependencies are enforced: a page can't merge before a model change it needs.StructureContentAPI impact - 4
Review the diff
Every change is added, modified or removed, with who made it. Breaking changes (a renamed field, a removed section) are flagged.BreakingBefore / after - 5
Merge to Production
All-or-nothing: it applies every change, creates the next Production version, clears the locks and calls the Production webhooks.v15Cache cleared
Content approval workflow
Publish website changes with approval, when you need it.
A content approval workflow CMS teams can turn on per person. When “Releases need approval” is on for a member, someone else with permission must approve before their Release can merge. When it’s off, they can release straight away — still recorded in history.
Per member, not global
A website Admin sets the toggle on each person. Clients who edit content can wait for a review; your developers can ship without one.Needs approvalRelease nowSomeone else signs off
The author never approves their own Release. Anyone with release.approve can review the diff and approve or send it back.DraftWaiting for reviewApprovedMerge is publishing
There is no separate draft toggle on the live site. Merging the Release applies every change, bumps the Production version and invalidates the cache.v13v14v15
Who can approve is set with team access: give someone Developer or Admin on the modules they review. See roles and permissions.
FAQ
Questions about staging and Releases.
How Development and Production work, what a Release ships, and what stays out of one.
Get started
Build your next client site on mywebcms.
Start from a screenshot, give your client one simple place to run it, and ship it on any stack you like.
- Two steps to your first website:
- 1Create your workspace
- 2Add a client website
Everything that comes with mywebcms
Tap any feature to learn more.