- Visual editing included on every plan, including free.
- Built-in image delivery and optimization via its asset CDN.
- Sandbox environments for schema changes.
Compare
Leiho vs DatoCMS
SaaS headless CMS with a GraphQL Content Delivery API, modular content blocks and built-in image CDN. Leiho takes another route: your content stays in WordPress, and editors click the real page of your own front end to change it.
LeihoDatoCMS
Hosting Your own WordPress, on any PHP host. Your front end stays wherever it is. SaaS only.
Open source Yes, GPL-2.0-or-later (plugin and bridge). Proprietary.
Pricing Free. No seats, no usage limits. Free plan: yes (300 records, 10GB/month bandwidth). Entry paid plan: Professional, €149/month billed annually or €199/month monthly (10 collaborators).
Visual editing Yes: editors click text and images on the real front end, inside wp-admin, and it updates as they type. Yes: click-to-edit overlays on the draft site plus a side-by-side 'Visual' tab in DatoCMS, on all current plans.
Content model Leiho Collections (schema builder or leiho.schema.json), or your existing ACF fields. UI (models built in Settings; also scriptable via the Content Management API).
AI Writing with your brand context on every text field, through WordPress’s own AI connectors (WordPress 7.0+). AI content translation and AI image tagging.
MCP server Yes, through the official WordPress MCP Adapter: agents read content and write drafts only. Yes, hosted.
Localization Built in, field by field: one entry holds every language, fields are translatable or shared, and AI or agents (MCP) translate what is missing. Yes, built-in field-level localization.
SEO and AI search Built in: each collection maps its fields to schema.org, description and FAQ. Leiho serves JSON-LD, llms.txt and every page as Markdown, in every language. Built-in SEO and social field and a computed meta tags API with fallbacks and framework helpers. JSON-LD is left to the front end. llms.txt and .md files are a documented build recipe.
Checked on 5 November 2026 from each vendor’s site. Prices and plans change: follow the sources below.
Where DatoCMS shines
Where Leiho differs
- Your content stays in a WordPress you host, not in a vendor’s cloud.
- Free and GPL for every site: no seats, plans or usage limits to watch.
- Editors keep WordPress: their login, roles, media library and plugins.
- Publishing follows your deployment, from a build hook to GitHub Actions or a self-hosted Coolify.
Choose DatoCMS if…
Teams that want a polished managed CMS with visual editing and strong media handling, priced in EUR.
Choose Leiho if…
Your team or your clients already know WordPress, you want them to edit the real page of a Next.js, Astro, Nuxt or SvelteKit site, and you’d rather not pay per seat or move content to a vendor’s cloud.
Can I move from DatoCMS to Leiho?
There is no automatic importer from DatoCMS. Leiho entries are WordPress posts, so content can be brought in with WordPress import tools or a script using Leiho’s PHP API. Your front-end components usually stay the same: only the data source and the annotations change.
Do I need WordPress?
Yes. Leiho is a WordPress plugin: WordPress stores the content and runs the back office. Any PHP host works, and your front end stays separate.
Edit the real site.
Free and open source. Try it on a real WordPress, in your browser.