A block editor your team writes in, and seven read-only JSON endpoints your site renders from. No plugin ecosystem, no theme layer, no database of yours involved.
{
"version": 1,
"blocks": [
{ "id": "blk_h1a2", "type": "heading",
"data": { "level": 2, "text": "Why we moved our blog to the edge" } },
{ "id": "blk_p9x1", "type": "paragraph",
"data": { "html": "Our writers were filing tickets to change a headline. That was the whole problem, and it was not a technical one." } },
{ "id": "blk_l4c7", "type": "list",
"data": { "style": "bullet", "items": ["No plugins to update", "No theme layer fighting our CSS", "No database of ours involved"] } }
]
}Fourteen block types and a typed data object on each. That is the entire vocabulary, and it is versioned.
Anchors come free, and they stay stable when the text is edited.
Sanitised on write by re-serialisation, so you can render it with a clear conscience.
Four variants, dimensions to stop layout shift, and a blur placeholder — same response.
A language tag and the raw source. Shiki, Prism, or nothing — your theme, your call.
Fourteen types in all, and no arbitrary HTML block waiting to break your layout.
A type your renderer has not met yet stays quiet instead of crashing the page.
Drop in the component, or map block types to your own. There is no scaffolding step and nothing to eject from later.
import { BlogContent } from 'blogkit/react' export default async function Page({ params }) { const post = await blogkit.blogs.get(params.slug) return ( <article> <h1>{post.title}</h1> <BlogContent blocks={post.blocks} /> </article> ) }
Read-only, bearer auth, ETags on every response. No GraphQL, no SDK you are forced to keep current — the package is optional and the JSON is documented. Publishing invalidates the cache so the next request is already warm.
The blog is the part of your side project that never gets built, because MDX means a rebuild for a typo. This is a real editor, a JSON endpoint, and an afternoon.
npm i blogkit and one componentEach client is a separate project — its own posts, media, categories, authors and quota. Nothing leaks between them, and you sign in once.
Not built yet: Webhooks · Scheduled publishing. Listed here rather than in the pricing table, because you should find out now and not after you have moved three clients across.
One price per plan, not per person — each tier includes its seats rather than billing for them.
One blog of your own.
A personal blog, or a side project.
A few sites, or your first clients.
An agency running a roster.
Cache hits count as a fifth of a request. Over quota we keep serving to 110% and email you — your blog never goes dark mid-launch.
No. Export gives you every post as block JSON plus a media manifest, from a button, any time. The block schema is documented, so the export is renderable without us.
Sign up, write one post, and see the JSON. If the integration takes more than five minutes, tell us and we’ll fix the docs.