Alternatives
LUNO is Backend Platform for the AI Era.
microCMS alternative
Teams outgrow microCMS when they need agent operations, multi-tenant org surfaces, or more than REST content APIs.
Criteria
What to look for in an alternative
Can humans and agents operate the same record (MCP / API / Console)?
Are forms, identity, and ops platform capabilities — not bolt-ons?
Is pricing per site/org rather than editor seats?
Edge delivery and security ops burden
Options
Main options
microCMS is a Japan-first headless CMS with fast REST setup. LUNO is a Backend Platform: CMS-like content sits beside forms, identity, MCP agents, and edge ops under one control plane.
LUNO
Japanese-capable teams that want MCP + forms + per-site/org platform pricing, not CMS-only APIs.
If GraphQL-free REST content alone is enough and you will not run agents against the backend, microCMS can stay.
See Product →microCMS
Domestic projects that only need a simple Japanese headless content API.
WordPress
Editorial teams whose entire workflow is classic WP admin plus an accepted plugin stack.
LUNO vs WordPress →Contentful
Enterprises standardized on Contentful’s content model and multi-language SDKs.
LUNO vs Contentful →Strapi
Engineering orgs that want full OSS customization and accept self-host cost.
LUNO vs Strapi →Sanity
Content orgs that want Sanity Studio collaboration as the center of gravity.
LUNO vs Sanity →
Migrate
Migration notes
Model content on LUNO, move entries via API, reconnect Next/Nuxt clients, then enable MCP for ongoing edits.
FAQ
FAQ
Is LUNO just another Japanese headless CMS?
No. Category is AI-era Backend Platform. Content is a capability; agents and forms share the same record.
Does LUNO have a free plan like microCMS Hobby?
Yes — Free is $0/site forever for evaluation (MCP, embed, forms, public API). See /pricing.md.
Japanese UI?
Yes. Console and docs support Japanese alongside English.
Also see the matrix
Use the filterable comparison hub and machine-readable pricing file.