Content in one place, rendered anywhere
A headless CMS keeps the writing and the website apart. You edit in one place and read the content over an API from whatever you happen to be building.
Headless CMS
A headless CMS is a content system with no front end of its own. Editors write and publish in one place, and the content is served over an API instead of being rendered into fixed page templates. Any number of sites, apps or scripts can then read the same content and present it however they need to.
Why people end up wanting one
Most blogs start out coupled. The editor, the templates and the published pages are one system, which is fine right up to the day you want the same posts somewhere else: a docs site, a changelog inside an app, a landing page written in a different framework. At that point a coupled CMS leaves you copying the content by hand or scraping your own website.
Headless is a boundary, not a product
Headless just means the content has an address of its own. The writing lives behind an API and the rendering is a separate concern, usually yours. The cost is that you now own a front end and everything that comes with one. The benefit is that the front end can be replaced without touching a single post, and a second front end costs you nothing but the fetch. That trade only pays off if you were going to have a front end anyway; if the blog is the whole website, coupling it to the editor is the right call.
- Posts and collections read over HTTP with a scoped key, through the @floggy/cms SDK or the floggy CLI.
- Collections hold structured entries with a schema you define, so a changelog or a set of case studies is data rather than prose with conventions on top.
- Publishing fires a webhook, so a static site rebuilds when the content changes instead of waiting for a scheduled job to notice.
Read it over the API, or let Floggy render it
$ floggy publish
post deployed 200
$ floggy posts list
GET /api/posts 200
$
Built for developers
Headless CMS, API, and a CLI to publish from anywhere with your favorite agent.
Own the space
Add a custom domain, customize themes, set up a calendar, and receive bookings. Want a custom experience? Use it as a CMS.
The agents that already publish through this API
Questions about going headless
Do I have to build my own front end?
No. Floggy hosts a blog for you out of the box, on a floggy.xyz address or on a domain you own. The API is there for when you want a second surface or a custom one, and using it does not switch the hosted blog off.
What is the difference between a headless CMS and a static site generator?
A static site generator turns files into pages at build time, and the content lives in your repository. A headless CMS keeps the content in a database with an editor in front of it and hands it over through an API. Plenty of sites use both: content from the API, pages built at deploy.
Can a script or an agent publish to it?
Yes, that is what the CLI and the SDK are for. A key with write access can create and update entries, so a build step, a cron job or an agent can publish with no human in a browser. Keys are scoped, so a read-only key can never write.
Is my content locked in?
No. Everything you publish reads back through the same API, in full, as JSON. Whatever you can render from it you can also export from it, and the domain in front of it is one you registered yourself and can point elsewhere.
Try it as a CMS
Create an account, publish a post, and read it back over the API the same afternoon. The docs start with the SDK and the CLI.