A CMS built around your content, not the other way around.
Your editors get live preview, flexible blocks, and versions. Your site gets structured content that can power new pages. We build on Payload when you start fresh, and on headless WordPress when your team wants to keep the editor it knows.
The modern CMS, now part of Figma.
Payload is an open-source CMS written in TypeScript. Its admin is a React app, so every screen can be shaped to how your team works.
Live preview
Editors see the real page update beside the form they're editing, before anything is published.
Flexible content blocks
Editors build pages from blocks designed for your content, so a new page doesn't need a developer.
A clean admin you can customize
Minimal by default. Fields, views, and dashboards can be tailored for each kind of editor.
Built-ins you can extend
Multilingual content, forms, media, drafts, and versions come built in, and each one can be extended.
Prefer the WordPress editor? Keep it.
Headless WordPress keeps the editor your team knows and moves the public site to the same fast front end. WordPress becomes a content store behind Cloudflare Access instead of a public server.
- Editors keep the screens, workflow, and training they already have
- The login and the plugins are off the public internet
- Visitors get the same fast pages a Payload site would serve
- The public site no longer depends on a theme or the plugins that render it
Which one fits.
Both get the same front end, hosting, and measurement. The difference is the editor and how your content is shaped.
Headless WordPress, when
- Your editors publish in WordPress every day and want to keep it
- You depend on an editorial workflow that already works
- You want a faster, safer site now and a CMS decision later
Payload, when
- You're starting fresh or ready to leave WordPress
- Your content has structure: programs, locations, events, contracts
- You want the admin shaped to your team instead of to a theme
Your team's AI tools, connected to your site.
Your team already uses Claude, ChatGPT, or Codex. A custom MCP server lets those tools work on your site: find a page, draft an update, translate it, and save it for review. It runs on Cloudflare behind the same sign-in as your CMS, and it only offers the handful of jobs you agreed to.
- Works with Payload and with WordPress
- Drafts, updates, and translations are saved for a person to approve
- Each tool does one agreed job, such as drafting an event page
- Keys stay on the server, never in the chat or the CMS
The server drafts and proposes. It does not publish by itself, and it is not a general-purpose login to your CMS.
Update the office hours on the Contact page, in English and Spanish, and hold it for my review.
- Found the page and its Spanish translation
- Drafted the update in both languages
- Saved as drafts. Nothing is published
New features are normal work, not a rebuild.
A CMS built around your content makes the next feature smaller. These are the requests that tend to follow launch.
Connect any tool
Your CRM, email platform, and the tools you already use. Integration keys stay out of the CMS database, with the least access that works.
Structured content
Programs, locations, events, and contracts are entered once as records. Listing pages, maps, and search pages are built from them.
A custom MCP
Your team's AI tools can draft, update, and translate content through a custom MCP server. Publishing waits for a person to approve it.
Built on Launch, which you can read before you hire us.
We don't start a project from an empty folder. Launch is our open-source set of reference sites: the same demo site built on Payload, on headless WordPress, and on traditional WordPress, each with the CMS locked behind Cloudflare Access. Your project starts from the one that fits, so the first weeks go to your content and design instead of plumbing.
- Reference sites for Payload, headless WordPress, and traditional WordPress
- CMS admin and API behind Cloudflare Access in every one
- Fast front ends on Cloudflare Workers
- The MCP server and a shared content model are part of the same repository
Launch is early and changes often. It is MIT licensed, so the starting point of your site is code any developer can read and keep working on.
The same repository holds the MCP server and a shared content model.
Frequently asked questions
Should we choose Payload or headless WordPress?
Does Payload cost anything to use?
Can you move our content out of WordPress?
How much training do editors need?
Pick the editor first. The site follows.
Tell us who publishes, how often, and what the current editor makes hard. We'll recommend Payload or headless WordPress and say why.