- GraphQL-first API for reading and writing content.
- Content federation: query external REST/GraphQL sources through one endpoint.
- Fully managed, with no servers to run.
Compare
Leiho vs Hygraph
GraphQL-native SaaS headless CMS with content federation from external APIs. Leiho takes another route: your content stays in WordPress, and editors click the real page of your own front end to change it.
LeihoHygraph
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 (Hobby, 3 seats). Entry paid plan: Growth, from $199/month (10 seats).
Visual editing Yes: editors click text and images on the real front end, inside wp-admin, and it updates as they type. Partial: Live Preview plus Click to Edit (beta) adds Edit buttons on tagged front-end elements that jump to the field in Hygraph Studio.
Content model Leiho Collections (schema builder or leiho.schema.json), or your existing ACF fields. Both (Schema Builder UI and Management SDK).
AI Writing with your brand context on every text field, through WordPress’s own AI connectors (WordPress 7.0+). AI Assist on all plans with token quotas; AI Agents announced as a paid add-on.
MCP server Yes, through the official WordPress MCP Adapter: agents read content and write drafts only. Yes, early-access MCP server (endpoint per project; docs mirrored; official page not confirmed).
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 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 SEO field: the docs recommend an SEO component you model yourself. JSON-LD is recommended but rendered by the front end. No llms.txt or Markdown output in the docs.
Checked on 5 November 2026 from each vendor’s site. Prices and plans change: follow the sources below.
Where Hygraph shines
Where Leiho differs
- Editors edit the real front end, inside wp-admin: they click a heading on the page and type.
- 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.
Choose Hygraph if…
Teams standardized on GraphQL that need to combine CMS content with data from other systems.
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 Hygraph to Leiho?
There is no automatic importer from Hygraph. 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.