Plug BetterCMS into your stack
First party adapters for Astro and Next.js, a typed Delivery API for every other framework, an MCP server for assistants, and a publish webhook for your host.
Available today
Each one has a setup page with the real package, the real config and what it does not do.
9 available, 11 planned
- Framework
Astro
First party adapter: a bettercms() integration, typed loaders, draft preview, and components that render page blocks.
- Framework
Next.js
First party App Router adapter: typed cache aware reads, tag revalidation, draft mode, and a generated llms.txt route.
- Hosting
Vercel
A deploy hook rebuilds the site on publish, or a revalidate route updates one page in about a second.
- Hosting
Netlify
A build hook rebuilds the site on publish. Three steps, no plugin, and one caveat about build minutes.
- Hosting
Cloudflare
Pages hosts the frontend and rebuilds from a deploy hook. Turnstile gates form submissions.
- Workflow
GitHub
Connect a repository for managed builds and previews. The build Action regenerates types and writes a content snapshot.
- AI
MCP server
An assistant authors models, entries, forms and components under a short lived, per project key. No tool deletes anything.
- Developer tool
Delivery API and SDK
REST reads with a typed client: one page, a paginated list, or an iterator that follows pagination for you.
- Developer tool
TypeScript codegen
Generates an interface per content model plus a schema registry, so your types cannot drift from your models.
Nothing in this category is built yet. What is planned, and why, is listed below.
Planned, not built
Listed so you do not have to ask. None of these has a page, because there is no setup to describe yet.
- Planned
Nuxt
No adapter. Reads content today through @bettercms-ai/sdk.
- Planned
SvelteKit
No adapter. Reads content today through @bettercms-ai/sdk.
- Planned
Remix
No adapter. Reads content today through @bettercms-ai/sdk.
- Planned
AWS
No documented setup. The publish webhook can call any AWS build URL.
- Planned
Slack
Not built. No Slack app and no Slack payload format.
- Planned
Zapier
Not built. Outbound webhooks and the Management API are the way in.
- Planned
Figma
Not built. No BetterCMS package talks to the Figma API.
- Planned
Cloudinary
Not built. BetterCMS has its own media transform endpoint.
- Planned
Algolia
Not built. BetterCMS ships its own site search.
- Planned
Stripe
Not on the roadmap. BetterCMS has no commerce layer.
- Planned
Segment
Not built. BetterCMS emits no analytics events of its own.
Missing one? Use the Delivery API
Any framework without an adapter reads published content through @bettercms-ai/sdk, a typed client with no framework attached.
Caching and draft preview are yours to handle on that path. The Astro and Next.js adapters do both for you.
import { BetterCMS } from "@bettercms-ai/sdk";
export const client = BetterCMS.site({
workspace: "my-workspace",
apiKey: process.env.BETTERCMS_API_KEY,
}); const page = await client.getContent("home");
for await (const item of client.listContentAll()) {
console.log(item.entry.title);
} Your next website starts here
See BetterCMS running on your pages, not on a sample site.