# 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.

## Your client edits the page, not a form. Risky changes wait for you.

CMS Brew maps the text and images in your Svelte components and Markdown, and the client edits them on the page or in chat. Per-field guards decide what publishes on its own and what waits for you.

- No integration, SDK, or script tag, so Svelte support is never the missing feature
- Markdown, frontmatter, and dynamic routes like blog/[slug]
- New pages, layout, and code go to you, in the client's words

## CMS Brew vs Traditional headless CMS, side by side

| | CMS Brew | Traditional headless CMS |
| --- | --- | --- |
| Integration work | Connect the GitHub or GitLab 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. |

## Where the other option wins

If a site needs thousands of structured entries, localization pipelines, or content shared across several apps, a traditional 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.

## FAQ

### Does CMS Brew work with my existing Svelte components?

Yes. CMS Brew maps the editable text and images in the files your site is built from, including .svelte pages and components and markdown content, and it handles dynamic routes like /blog/[slug] per page. It is built for editing the content of existing pages; a brand-new page or section is an out-of-scope request that gets escalated to you.

### Do I need to install a SvelteKit integration or adapter?

No. Nothing is installed in your project and no script is added to the site. CMS Brew works from the repository side: it reads your files, and publishes arrive as normal Git commits your host rebuilds from.

### Which hosts does CMS Brew support?

Vercel, Netlify, and Cloudflare, with live previews built into the editor. Because every publish is a plain commit, publishing works with any host that rebuilds your site from Git.

### What happens when the client asks for a new page or a redesign?

The editor refuses it and routes it to you with the client's original message attached, by email or Slack if you have escalations configured. The client gets a clear answer, and you get the work request instead of a surprise on the live site.

### Does CMS Brew also work for my non-SvelteKit sites?

Yes. The same account covers Next.js, Astro, Vue, Nuxt, Remix, Gatsby, and Hugo sites, so one tool can carry your whole client portfolio. Pricing is per connected site: $39 per month includes 5.

---

- [Home](https://cmsbrew.com/)
- [Features](https://cmsbrew.com/features)
- [Full product details](https://cmsbrew.com/llms-full.txt)