Pricing
Plans based on how much content and capacity you need.
Rendered by your frontend. Edited in Garchi.Get started
Headless CMS for AI-built and developer-built products
Change content without changing your app
Garchi CMS keeps your website and application content separate from your frontend. Your team updates content in a dashboard, your app reads it through a REST API, and compatible AI agents work with it through MCP — so routine content changes stop being code changes.
Free Sandbox plan · no card required
A
Your rough brief
New pricing page copy — update the headline, add a short intro and a link to the docs.
The problem
AI can build the site. Someone still has to manage the content.
AI coding tools and developers are good at building interfaces. But once the product is live, changing a headline, publishing an article, updating a product description or adding a new page should not mean editing application source code — or asking an AI agent to rebuild the frontend again.
Garchi gives that content a structured home outside the frontend. New components, layouts and application behaviour are still your code; the content inside them is not.
-
Your frontend stays yours
Build it with your preferred framework, your own developers or an AI coding tool. Garchi does not replace your frontend, your hosting or your application architecture.
-
Garchi holds the content
Pages built from reusable sections, articles and products as data items, categories, metadata, uploaded assets and per-language content all live outside your application code.
-
People and AI can manage it
Your team uses the dashboard. Your application reads the REST API. Compatible AI tools connect through Garchi's MCP server.
One content layer
One content model. Three ways to work.
Your team does not have to keep separate copies of the same content. Editors work in Garchi, your frontend reads the API, and compatible AI agents work through MCP — all against the same structured content.
For people
Dashboard
Editors, marketers and founders manage pages, sections, articles, products, categories, images and translations from the Garchi dashboard. No access to your codebase required.
For applications
REST API
Your frontend fetches the content it needs over HTTP, in whatever framework you already use. Node.js and PHP SDKs are available if you want them.
For AI agents
MCP
Connect a compatible AI tool to Garchi's hosted MCP server and it can read and update the same structured content, using authenticated access to your account.
Product tour
See Garchi CMS in action
BUILT-IN MCP SERVER
Give AI agents structured access to your content
MCP is an open protocol that lets AI tools connect to external systems. Garchi's hosted MCP server lets a connected, compatible AI tool work with the content in your Garchi account — creating pages, updating data items, reordering sections and uploading assets against your actual content model, instead of guessing at it from your frontend source code.
CONNECT YOUR AI TOOL
MANAGE CONTENT BY CHATTING
20+ TOOLS
WORKS WITH COMPATIBLE MCP CLIENTS
YOUR AI AGENT
The agent reads your content model and calls the same Garchi operations your team uses in the dashboard, with authenticated access to the connected account.
Starter kits
Scaffold a connected project with one command
Starter kits for Next.js, Nuxt, SvelteKit and Laravel. Or skip the kit and call the REST API from any stack.
npx @lumenharbor/garchi-starter-kit -k next
What Garchi is designed to solve
One structured content layer behind your product
Instead of spreading business content across admin panels, markdown files and application database tables, Garchi keeps it in one place your team, your code and your AI tools can all reach.
-
Content models that grow with your product
- Model pages with reusable sections. Extend data items with custom metadata. Adding an author bio to a blog post or pricing tiers to a product page does not mean changing your application's database schema.
-
Your team and your codebase, side by side
- Editors work in the dashboard, developers work in code. Keep separate spaces per project and invite collaborators with per-space permissions, so content work does not run through your deployment pipeline.
-
AI agents work on your real content model
- The built-in MCP server gives compatible AI tools authenticated access to the same spaces, pages and data items your team works with — reading and writing real records rather than generating one-off text.
-
Multilingual content built in
- Pages and sections support language-specific content without an add-on. Choose the languages you need per space and manage those translations in one place.
-
Hosted, so you don't run the CMS
- Garchi is a hosted service, and uploaded assets are stored on Amazon S3. You don't have to build, deploy or maintain content infrastructure of your own.
-
A REST API any stack can call
- Plain REST endpoints your frontend can call over HTTP, with Node.js and PHP SDKs if you want them. Current rate limits are published in the API documentation.
Who it's for
Who Garchi is for
Different teams reach Garchi from the same place: the frontend is built, and the content behind it still needs managing.
Use case one
AI-built websites and applications
Use an AI coding tool to build the frontend, and keep routine business content out of the generated application code — so updating a headline or publishing an article doesn't mean another round of prompting.
Use case two
Startup and SME products
Give non-developers a place to manage landing pages, articles, product information and campaign copy, while developers keep control of the application architecture.
Use case three
Agencies and freelancers
Build the frontend for a client and hand them a dedicated place to manage ongoing content. Paid plans include multiple spaces, so separate projects stay separate.
Content modelling
Content models that fit your product
Your blog post has authors. Your product page has pricing tiers. Your case study has industry tags. Garchi's data items start with a base schema and extend with the metadata your content needs — without changing your application's database schema.
Works with your stack
Keep your frontend architecture
Garchi manages content. It does not dictate how you build the rest of your application — your framework, your database, your hosting and your auth stay yours.
- Any frontend that can make an HTTP request
-
Garchi exposes a REST API, so Next.js, Nuxt, SvelteKit, Laravel and anything else that speaks HTTP can consume it. There is no framework dependency and no SDK requirement — the Node.js and PHP SDKs are there if they help.
Read the docs - A short path to your first request
-
Sign up, create a space, add your content and generate an API token. Starter kits for Next.js, Nuxt, SvelteKit and Laravel scaffold a connected project from a single command, and the API reference documents every endpoint.
Get started - Room to grow
-
Start with one space and a handful of items on the free plan. Move up to more spaces, more pages, thousands of data items and more languages as your content grows, without moving to a different platform.