Best CMS
for vibe-coded apps
Updated 2026-09-18. Sanity is the pick for most projects. Here is how the options compare, and how to run whichever you choose through a single Squiid key.
Short answer
- Our pick: Sanity. Schemas defined in code, which means your coding agent can edit the content model in the same repo as the app, plus a real time editing studio for non-developers.
- Runner-up: Contentful. The mature enterprise option with strong roles, localisation and publishing workflow. Pick it when a marketing team with process is the actual user.
- Pick something else when: No CMS at all when you are the only editor. Markdown or MDX files in the repository are free, version controlled, reviewable in a pull request and directly editable by your coding agent, which no hosted CMS can match.
Be honest about who edits the content. If it is you, put markdown in the repo and let your agent edit it. If it is a colleague who will never open a terminal,, use Sanity, because the schema still lives in code where the agent can change it while the editing happens in a friendly studio.
How to choose a CMS for an AI-coded app
Who is actually editing?
A CMS exists so that people who do not write code can change words. If nobody like that exists yet, a CMS is an extra service, an extra bill and an extra API call on every page render for no benefit. Files in the repo are the better default until there is a second editor.
Is the content model in code?
When the schema lives in your repository, your agent can add a field and update the templates in the same change. When it lives in a web dashboard, every content model change becomes a manual step outside version control that the agent cannot perform.
Build time or request time?
Fetching content at build time gives you fast static pages but requires a rebuild to publish. Fetching at request time publishes instantly but adds an API call and a failure mode to every page view. Most sites want build time with on-demand revalidation.
Images and assets
Check whether the CMS hosts and transforms images, because if it does not you are adding storage and a transformation pipeline. This is often the deciding factor for a content heavy marketing site.
How hard is it to leave?
Content outlives tooling. Confirm you can export everything as structured data, ideally as portable text or markdown rather than a proprietary rich text blob. Ask this before you put two years of writing into a system.
Compare the options
Every CMS option Squiid carries in the CMS category, with what each one is best at and how it bills.
| Service | Best for | Pricing | On Squiid |
|---|---|---|---|
| Contentful | Enterprise headless CMS with localisation and publishing workflows | both | Roadmap |
| Sanity | Structured content platform with a customisable editing studio | both | Roadmap |
Why run your CMS through Squiid
One login instead of one per vendor. Squiid carries 2 CMS options here and every other layer of the stack beside it. You create one account, click the service you want, and Squiid provisions it upstream. No separate signup, no separate password, no second dashboard.
One bill, at the provider's price. Usage is paid from prepaid Squiid credits at par: $1 of credit is $1 at the provider, with no markup on what the provider charges. The free plan is $0/month with a 15% fee on credit top-ups and a $50 minimum top-up. Solo is $19.97/month and its top-up fee starts at 8%, falling to 6.5%, 5% and 3.5% as trailing 30-day API spend passes $100, $500 and $2,000. Team is $29.97 per seat per month for seats 1-5, $24.97 for seats 6-20 and $19.97 above that, with the same ladder one point lower. Custom pricing is 3% or less against a commitment. Services that are sold as a monthly subscription, such as Sanity's paid plan, pass through on your Squiid invoice at the provider's own price with no fee on top.
Squiid holds the upstream key. The provider credential lives in Squiid, not in your repo, not in a chat window and not in a screenshot. Your project gets one variable, SQUIID_API_KEY, and that is the only secret an agent ever needs to see. Rotating it is one click and does not touch the provider.
It works with every coding agent. Point the SDK base URL at https://api.squiid.io/v1/<service>/ and send Authorization: Bearer $SQUIID_API_KEY. Claude Code, Cursor, Codex, Gemini CLI, Copilot, Windsurf, Cline, Devin, Replit, v0 and Lovable all read environment variables the normal way. See the gateway convention.
Running out pauses, it never deletes. Squiid warns you at 75%, 90% and 100% of your balance. At zero, calls pause instead of overdrawing, and your data stays where it is. Auto top-up is optional and takes a hard monthly cap. See spend controls.
Set it up in 3 steps
Add Sanity in the dashboard
Create a Squiid account, open the catalogue, and click add on Sanity. Squiid creates the upstream account or project for you and holds the credential.
Put one variable in .env
Copy your Squiid key and add SQUIID_API_KEY=sq_live_… to your project's .env. Delete any provider keys you were carrying. Nothing else changes.
Point your agent at the gateway
Tell your agent that calls go to https://api.squiid.io/v1/sanity/ with Authorization: Bearer $SQUIID_API_KEY. Most SDKs take a base URL option, so it is a one-line change.
In practice that is one line in your project:
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxThen every call your app or your agent makes goes to the gateway with that one key:
curl https://api.squiid.io/v1/sanity/... \
-H "Authorization: Bearer $SQUIID_API_KEY"Questions people ask
Do I need a CMS for an app I vibe-coded?
Only if someone who does not use a code editor needs to change content. Otherwise markdown or MDX files in your repository are free, version controlled and directly editable by Claude Code or Cursor, which is usually faster than any dashboard.
Sanity or Contentful?
Sanity when you want the content schema in code so your agent can evolve it alongside the app. Contentful when a marketing team needs roles, approval workflow and localisation. Both are available on Squiid under one key and one invoice.
Can a coding agent update CMS content directly?
Yes, through the CMS write API. Give the agent SQUIID_API_KEY and the gateway path rather than a CMS write token. That way the token cannot be exfiltrated from a prompt, and you can rotate access in one click.
Will a CMS slow my site down?
Only if you fetch on every request. Fetch at build time and use on-demand revalidation when content changes, so visitors get static pages and editors still see updates within seconds of publishing.
How is a CMS billed through Squiid?
Most headless CMS vendors sell monthly plans. Those pass through on your Squiid invoice at the provider price with no fee added. API usage above plan limits draws on prepaid credits at the provider rate.
One key for your CMS.
And everything else.
Add Sanity and 107 other services to one account, one key, one bill and one dashboard.