The open-source CMS for websites built by AI and run by humans
Modern stacks made websites fast to build and impossible to hand over — this one ends with a WordPress-style studio your client already knows.
“I handed over a Next.js site in under an hour. The studio needed zero explanation — my client just started editing.”
“Couldn't figure out how to hand over AI-built sites until this. One container, one login — done.”
“First handover where the client didn't call me the next week. They've published 40 posts themselves.”
How it works
From prompt to a client running their own site, in three steps.
One command: a running site, a studio and a database. Yours, on your infrastructure — no accounts to open.
Describe it in a sentence. Your agent writes the content types, pages and copy through the content API — not into files only you can reach.
They log into a studio that already knows the site — posts, pages, media, drafts. No handover doc, no training call.
One install. Every way to write.
Humans use the studio, agents use the API — same content, same roles, same audit log.
One predictable endpoint for every content type. Agents and scripts write here; the site revalidates on publish.
Posts, pages, media, drafts, roles — WordPress vocabulary, on purpose. Your client has seen this before.
Your agent keeps an author-role key after handover. Every write lands in the same audit log as the humans'.
Ask the AI for a plugin, not a rebuild. The client just finds a new panel in the sidebar.
Everything your client needs to run the site
Skip months of glue work. One install gives the site a full back office.
Posts, pages, media, drafts. Vocabulary your client already knows — no training call.
They add their own team — admins, editors, authors. You stop being the account manager.
Every publish revalidates the live site in about four seconds. No build minutes, no webhooks to wire.
Humans and agents write through the same API — and the same log. Always know who did what.
Site, studio, API, auth, media and database in one image. Runs on a $6 VPS or their existing cloud.
The agent writes plugins against a stable API — booking forms, galleries — and installs them into the same studio.
Your stack, unchanged
Prelo is a dependency, not a platform to migrate onto.
Your agent already knows how to build
A first-party Claude Code skill, a hosted MCP server, and a plain REST API. All official, all maintained.
A drop-in skill for Claude Code. It teaches the agent to scaffold, write content and manage roles.
One config block gives Claude, Cursor or any MCP client full access to a site's content.
Typed, versioned and predictable. Create, schedule and publish anything with a fetch call.
Frequently asked questions
Is Prelo really free?+
Yes — MIT licensed, self-hosted, no per-seat or per-editor pricing. Optional managed hosting exists for clients who'd rather you didn't run the server.
Can my client break the site?+
No. The studio edits content, not code. Roles scope what each person can touch, and every change is in the audit log and reversible.
Which frameworks does it work with?+
Next.js, Astro, Remix, SvelteKit and Nuxt, with SQLite or Postgres underneath. Prelo installs into the repo you already have.
Where does it run?+
Anywhere a container runs: a $6 VPS, the client's existing cloud, or your managed hosting. Backups are a volume snapshot; migration is a docker pull.
How do agents write content after handover?+
Through a scoped API key with an author role. Their writes appear in the studio as drafts, attributed to the key, next to the humans' changes.
Can I white-label it for my agency?+
Yes — it's MIT. Fork it, put your logo on the studio, and hand clients a back office with your name on it.
Ready to hand over your next site?
Free and open source for every site you build. Start with one command and send the client a login link instead of a Loom.