Draftbase
Product

Typed schemas. An MDX editor. An API agents can drive.

Every feature is on every plan, free one included. Plans differ on usage, not on what works.

Authoring

A real editor,
not a text box

Writers compose in blocks and see the exact components render as they type. No preview tab that lies to them. Nobody touches raw MDX unless they want to.

See the editor
<h1>
Ship weekly changelog
<callout>
New MCP tool: agents can now open a PR.
<p>
Full width media, structured fields, zero glue code.
schema.json
{
  "id": "headline",
  "type": "text",
  "required": true
}
Structure

Collections with real schema

Pick a field type, name it, mark it required. The schema updates live and every entry follows it. That is the whole content modeling workshop.

  • 8 field types: text, rich text, number, boolean, date, media, reference, JSON
  • References link collections without duplicating data
  • The same schema drives the editor UI and the delivery API
See content modeling
Collaboration

Org roles, entry status, and a full revision history

Every entry moves through draft, published, updated, and archived. Every edit becomes a revision you can roll back to. Nobody has to reconstruct last Tuesday from memory.

See platform admin
Homepage hero copyDraft
Pricing page updateUpdated
August changelogPublished
Automation

MCP-connected AI edits

Give an agent write access the same way a teammate has it, through the schema. It gets tools, not a directory of files to freestyle in.

  • 26 MCP tools cover templates, entries, and media
  • Every automated write is schema-validated first
  • Fires the same webhooks a manual edit would
Read the MCP docs
Delivery

A clean API and webhooks that fire on publish

Pull content into any frontend with the REST API or GraphQL. Push updates out to the services that need to know the moment something ships.

See webhook settings
  1. Entry published
  2. Webhook queued
  3. Delivered (200 OK)

See it without Draftbase, side by side

Flip the switch to compare a typical CMS hand-off with how Draftbase teams actually work.

Without DraftbaseWith Draftbase
  • Writers work from a schema your team already reviewed — no ticket to add an entry
  • Rich text is plain MDX, rendered by the exact components you wrote
  • Publishing fires a webhook — your pipeline picks it up automatically
  • Every change is a revision, attributed and rolled back to on demand
Built on open standards
ReactNext.js App RouterMDXREST APIGraphQLNode SDK

Explore each part in depth

One page per capability, with the tradeoffs, the comparisons, and how Draftbase implements it.

Questions about Draftbase features

What does Draftbase include out of the box?

Typed content schemas with 8 field types, a block-based MDX editor, a REST and GraphQL delivery API, a typed Node SDK generated from your schema, org roles, revision history with rollback, signed webhooks, and CDN-backed media. Every plan includes all of it — features are not gated by tier.

Does Draftbase work with the Next.js App Router?

Yes. @draftbase/renderer ships a JSX-runtime integration for React, Next.js, React Native, Astro, and Remix. Rich text fields are stored as MDX strings, so a server component can fetch an entry and render its body with your own components.

Can AI agents write content through these features?

Yes. 26 MCP tools cover templates, entries, and media, and every automated write is validated against your schema before it lands. Agent edits fire the same webhooks a manual edit does and land in the same revision history, so any change can be rolled back.

Is there a free plan?

Yes. Hobby is free and needs no credit card. Startup is $49/mo, Growth is $299/mo, and Scale is $499/mo. Plans differ on usage limits, not on which features you get.

Start writing in under two minutes

Hobby is free, no card. Startup is $49/mo when you outgrow it. No demo call, because the numbers are already on the pricing page.

Sincerely: pick whichever CMS gets out of your way. We built this one because none of them did.