The editor
Not a config file — a real editor
This is the actual app that opens on npx @kdrgny/justjson: a visual schema builder, and a theme panel that previews your generated site as you style it.
schema
design
Every other headless CMS wants something first — an account, a database, an API key, a plan tier. JustJSON wants nothing. Create your content, save it, read it back. It's all files in your own repo.
Pick a use case to see the schema, the editor fields and the JSON file it produces.
Your content never touches our servers — because there are none. The files are already in your repo; JustJSON only edits them.
No account, no database, no token, no dashboard. It runs on your machine and sends data nowhere. Start it, use it, close it.
Plain JSON diffs and versions cleanly. Import it in your build, deploy it wherever you like — or walk away with it tomorrow.
A headless CMS hosts your data and rents you an API to reach it. JustJSON removes the whole middle.
Your content sits on someone else's disk. Getting it back is an export job — and leaving is a migration project.
Create it, save it, read it back — all on your own disk. Your build imports the files directly. There is no round trip, because there is nowhere to go.
| Typical headless CMS | JustJSON | |
|---|---|---|
| Account & signup | Required | None |
| Database | Theirs, hosted | No database at all |
| API key / token | Required to read | None |
| Request quota | Tied to your plan | There is no request |
| Where content lives | Their cloud | Your repo, on disk |
| Works offline | No | Always — it's local |
| Getting your data out | Export job or API dump | You already have it |
| Cost as you grow | Per seat, per request | Free, MIT |
| Leaving | A migration project | Delete one dev dependency |
Schema, content, validation and typed output — without a line of config, without a server.
Say what you're managing and JustJSON drafts the collections and fields. Bring your own key (Gemini, Groq, OpenRouter or local Ollama) — it goes straight to the provider, never to us.
Paste any content JSON and JustJSON works out the structure: lists become collections, objects become singletons, HTML becomes rich text.
Define collections and fields in the UI — drag to reorder, collapse what you're not editing. No config file to hand-write.
Entries list with title, slug and date; search and edit instantly. Content — not a pile of slugs.
Headings, bold, lists, quotes — WYSIWYG. But it's saved to disk as clean, diffable Markdown.
Drop an image; it's resized to WebP right in the browser and written under content/media/.
Generates types.ts and a zero-dependency content.ts loader — or drops straight into Astro content collections with one line. Your content is fully typed in your build.
Wherever you put the JSON becomes your API — repo raw, jsDelivr, your own build. Export the whole project as a ZIP any time.
justjson validate checks content against the schema — broken relations, duplicate slugs, missing media, wrong types — and exits non-zero, so a bad entry never ships.
Flip an entry's status while you work on it. The generated loader returns only published entries by default, so drafts stay off your live site.
This is the actual app that opens on npx @kdrgny/justjson: a visual schema builder, and a theme panel that previews your generated site as you style it.
Begin from one of eight templates, from JSON you already have, or just describe what you're managing and let AI draft the schema. No config file to write.
npx @kdrgny/justjson opens the editor in your browser. Build the schema by clicking, enter content, upload images. Nothing leaves your machine.
Pick a palette, accent, font and spacing, and watch a live preview of the actual site as you go. The look is saved as plain JSON too.
Generate a working site from your content in a click, push it to GitHub, and hand it to Vercel or Netlify from the same screen. Still no account with us — the files stay yours.
Real sites whose content is nothing but the JSON in their own repo.
The page you're reading. An Astro build whose every word is a JustJSON project in its own repo — edited in the editor, read straight at build.
Visit →A personal CV site. Built from the cv template, edited in JustJSON, shipped as content/*.json read straight at build.
Visit →Made something with JustJSON? Tell us and we'll add it here.
The whole local CMS is free and MIT. The one thing you pay for is client handoff — the part you bill for anyway.
Everything you need to build on your own machine.
Hand the finished site to a client. They edit and publish — no git, no deploy, no fear.
For agencies handing off many client sites.
Give a non-technical client a URL, a login and a Publish button — while the content stays in your own repo. Join the waitlist and lock the early-bird lifetime price.
One command. No account to create, nothing to cancel later.