- Real-time collaborative editing on a hosted content store, with no database or server to run.
- GROQ query language and fully code-defined, versionable schemas.
- Studio is a customizable React app that developers can extend deeply.
Compare
Leiho vs Sanity
Hosted content platform (Content Lake) with an open-source, code-configured React editing app called Sanity Studio. Leiho takes another route: your content stays in WordPress, and editors click the real page of your own front end to change it.
LeihoSanity
Hosting Your own WordPress, on any PHP host. Your front end stays wherever it is. Both, partly: content is stored in Sanity's hosted Content Lake (SaaS only); the Studio app can be self-hosted or deployed on Sanity.
Open source Yes, GPL-2.0-or-later (plugin and bridge). Studio is MIT (open source); the Content Lake backend is proprietary and paid by usage.
Pricing Free. No seats, no usage limits. Free plan: yes ($0, up to 20 seats, 10k documents). Entry paid plan: Growth, $15 per seat/month, with pay-as-you-go usage above included quotas.
Visual editing Yes: editors click text and images on the real front end, inside wp-admin, and it updates as they type. Yes: the Presentation tool shows the real front end inside Studio, and clicking an element opens the matching field (quickstarts for Next.js, Astro, Remix, SvelteKit, Nuxt).
Content model Leiho Collections (schema builder or leiho.schema.json), or your existing ACF fields. Code (schemas defined in JavaScript/TypeScript in the Studio config).
AI Writing with your brand context on every text field, through WordPress’s own AI connectors (WordPress 7.0+). AI Assist, Agent Actions, Content Agent and semantic search/embeddings, with monthly AI credits per plan.
MCP server Yes, through the official WordPress MCP Adapter: agents read content and write drafts only. Yes, hosted remote server.
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, via official plugins (field-level or document-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. No built-in JSON-LD, llms.txt or Markdown output; SEO fields are modeled by you (the main SEO plugin is community-made). Sanity publishes an official starter with .md routes and llms.txt, as front-end code.
Checked on 5 November 2026 from each vendor’s site. Prices and plans change: follow the sources below.
Where Sanity 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 Sanity if…
Developer-led teams that want a code-defined schema and a deeply customizable editor on top of a managed content backend.
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 Sanity to Leiho?
There is no automatic importer from Sanity. 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.