The same client-friendly vocabulary — posts, pages, media, roles — with the build experience flipped from PHP and page builders to your own stack plus an AI agent.
WordPress remains right when the site leans on its plugin economy (WooCommerce especially) or a non-developer is doing the building. If you build with AI in a modern framework and hand the result to a client, Prelo is the version of that workflow that doesn’t end with you as the update department.
Export WXR from WordPress, hand it to your agent, and it recreates types, posts, pages and media through the content API. Redirects are core, so old URLs keep working. Most content sites move in an afternoon.
The studio deliberately keeps WordPress’s vocabulary and layout logic. In handovers so far, clients don’t ask what it is — they just start editing.
No — Prelo is headless, your frontend is code. That’s the point: the agent builds it in your stack.
More comparisons: WordPress alternative (overview) · Best headless CMS
Free and open source. One command, and the client gets a login instead of a Loom.