CMS for SvelteKit sites, nothing to integrate.
No integration, no SDK, no schema. Your client edits the SvelteKit site by chat, and every publish is a plain commit your host rebuilds from.
No credit card, cancel anytime.
The SvelteKit handoff problem
SvelteKit is a pleasure to build with, and the CMS ecosystem still treats it as an afterthought. Most headless CMS tooling is React-first, so official SDKs and visual editors arrive late or not at all for Svelte. The fallbacks each tax you differently: a headless API means schemas and fetch rewrites, a Git-based admin panel means a config file and a form UI your client never learns, and doing the edits yourself makes every wording change your job.
CMS Brew works from the repository side instead. Content stays in your Svelte components and markdown, exactly where SvelteKit reads it. CMS Brew maps the editable text and images automatically, your client edits in chat, and each publish is one commit that triggers your normal build.
Nothing added to your site
No integration, no SDK, no script tag. The repo stays a plain SvelteKit project; CMS Brew reads it and commits to it from outside, so Svelte support can never be the missing feature.
Made for how SvelteKit stores content
Pages, components, markdown, frontmatter, images. CMS Brew maps your existing files, handles dynamic routes like blog/[slug], and scopes edits per page, so the client edits the page they mean.
Safe enough for clients
Per-field guard levels decide what publishes freely and what waits for review, and requests for new pages, layout, or code are refused in the chat and escalated to you with the client's words attached.
Side by side
CMS Brew vs Headless CMS
| CMS Brew | Headless CMS | |
|---|---|---|
| Integration work | Connect the GitHub repository. That is the setup. | Install an SDK, define a schema, rewrite pages to fetch from an API. |
| Svelte support | Not a feature, a non-issue: CMS Brew edits the repo, not the runtime. | Often secondary: SDKs and visual editors are React-first. |
| Where content lives | In your repository, in the files SvelteKit already builds from. | In the vendor's database, behind their API. |
| What the client learns | Nothing. They type what they want changed. | The studio UI and your content model. |
| Review before publish | Per-field guards and a review queue, included. | Roles and approval workflows, usually on higher tiers. |
| Cost model | $39/mo for 5 sites, unlimited editors. | Per-seat pricing that grows with every editor you invite. |
The honest trade-off
If a site needs thousands of structured entries, localization pipelines, or content shared across several apps, a real headless CMS earns its schema, even with thinner Svelte tooling. For the delivered client site with a handful of pages, moving content out of the repo is cost without payoff.
How it works
Three steps, then it's live.
- 01Connect
Point it at the site you built
CMS Brew turns it into a simple list of things your client can edit. No rebuild, no plugin.
- 02Edit
Clients edit in plain words
Your client opens a chat and says what to change: a phone number, a headline, a photo. They see it live before it ships.
- 03Publish
Safe changes go live
Safe edits publish in one click. Bigger requests, like a new page or code, come straight to you.
FAQ
What people ask before switching.
Stop being the person who updates the phone number.
Give your client the keys to the content. Keep the keys to the code.
Prefer to talk first? Book a 30-minute call