- Content stored as files in Git with commits as history.
- No database or server required.
- Works with most static site generators.
Compare
Leiho vs Decap CMS
Open-source, Git-based CMS (formerly Netlify CMS) that edits files in your repository for static sites. Leiho takes another route: your content stays in WordPress, and editors click the real page of your own front end to change it.
LeihoDecap CMS
Hosting Your own WordPress, on any PHP host. Your front end stays wherever it is. Self-hosted (a single-page admin app in your site; you bring auth/backend); paid Decap Turbo add-on offers hosted auth.
Open source Yes, GPL-2.0-or-later (plugin and bridge). MIT.
Pricing Free. No seats, no usage limits. Free: yes (MIT). Paid: Decap Turbo extension (price not confirmed).
Visual editing Yes: editors click text and images on the real front end, inside wp-admin, and it updates as they type. No on-site editing: the editor shows a live preview pane next to the form fields.
Content model Leiho Collections (schema builder or leiho.schema.json), or your existing ACF fields. Code (config.yml collections).
AI Writing with your brand context on every text field, through WordPress’s own AI connectors (WordPress 7.0+). None notable.
MCP server Yes, through the official WordPress MCP Adapter: agents read content and write drafts only. No official MCP server found.
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, side-by-side multi-language authoring via i18n config.
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. Git-based, writes Markdown files. No built-in SEO widget; JSON-LD, llms.txt and Markdown serving are handled by the static site generator.
Checked on 5 November 2026 from each vendor’s site. Prices and plans change: follow the sources below.
Where Decap CMS shines
Where Leiho differs
- Editors edit the real front end, inside wp-admin: they click a heading on the page and type.
- 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 Decap CMS if…
Small static sites whose developers want a free, Git-based editing UI with no 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 Decap CMS to Leiho?
There is no automatic importer from Decap CMS. 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.