About
Your content, as data. Every way you use it.
Nohead holds the structured data behind your website, apps and agents, and serves it through one API, with an editor on top for the people who keep it right.
Data firstDefine collections and fields; get a REST API, SDKs, a CLI and an MCP server.
One set of rulesPeople, scripts and agents change content the same way, and every change says who.
All in the boxFiles, images, search and version history, with no extra services to wire up.
More than pagesCatalogs, listings, reference data, app settings, docs and posts.
How we build it. And what that rules out.
These aren't features: they decide what we build, and what we don't, whatever comes next.
Content, not pages. Nohead will never have page-building blocks. Records hold structured data that any front end can render, so a redesign never means rewriting your content.
Everything the editor does, the API does. Content and schema work the same through the API, the SDKs, the CLI and MCP. Nothing is locked behind a screen.
Any framework, any host. Nohead serves JSON over HTTPS, so it works with whatever you build on, and nothing in it assumes one framework or one host.
Engines you can see. Search runs on Meilisearch and images on imgproxy, and we say so: your site uses their own documented options instead of a wrapper we made up.
Free to leave.
nohead exportwrites plain files: your schema as YAML, one JSON Lines file per collection and, if you ask, every original file and the full history. Take them anywhere, or load them into a new project withnohead import.Open where it runs in your code. The SDKs and the CLI are MIT-licensed on GitHub, and the API contract is a public OpenAPI document.
No AI unless you turn it on. Agents reach your content only with the keys you give them. Any AI features of our own will be off until your organization turns them on, and your content will never train a model.
Get in touch.
We read everything.
Your first collection is two minutes away.
Start from a template or a blank collection, invite your team, and read it all back from the API before the coffee gets cold.