Update your website's content without changing the code.
A whole site, just your blog, or a single content section: kura is the editable content layer for whatever part of your site needs to change. Your developer, or your AI tool, wires up the fields once; whoever keeps the site current then edits the words, photos and prices forever, without touching the code.
$6 per site per month, or $60 per year. Unlimited editors. First month free.
How websites are typically updated
You built a site, or paid someone to build one. Six months later a menu has changed, some prices are out of date, new staff need photos on a team page. Most people end up doing one of three things.
Pay a developer
Every change becomes a quote, a deploy, an invoice. Fine for big work. Painful for small edits, and most developers are busier than they sound when you ask. Ideally, updating content shouldn't need a developer at all.
Use a CMS
Content management services (CMS) like Sanity, Contentful, Storyblok and Strapi let you edit content yourself. The trade-off is the bill: most charge per editor, and things like a draft copy or single sign-on are billed as separate add-ons.
Have an AI make changes
In most sites, content and layout live in the same files. Asking a general-purpose AI to update content means editing the codebase. Getting 80% of what you want is easy. Getting it the way you actually want takes a lot more prompt-and-correct, prompt-and-correct.
kura sits in the second category. Content lives separately from layout, so updating content never touches the code that builds the site. A price update is just a price update.
Use kura for as much or as little as you need - your whole menu, your product list, or just the blog.
How kura works
The first two steps are your developer's one-time setup. After that, editing is all that is left.
- 1
Your developer's one-time setup
Set up the fields
Your developer (or their AI coding tool) defines what can be edited - your menu items, your team, your prices - and kura builds a simple form for each.
- 2
Your developer's one-time setup
Build the website against the API
Your frontend reads the published content from kura's REST API. Works with any stack: Astro, Next.js, Nuxt, SvelteKit, plain HTML.
- 3
Then, forever: you edit
Update the content using kura
Whoever keeps the site current signs in with an emailed link, changes the words, photos and prices, and hits save. No code, no GitHub, no fear of breaking anything.
Set up content by talking to your AI tool
kura ships a Model Context Protocol server, so your AI coding tool can set up your content types by talking to kura. Say "add a bedrooms field to Listing" and the field, plus the editor form for it, appear. It only shapes the content schema; it never overwrites what your editors have written, and no model runs when your site is served.
You Add a bedrooms field to the Listing type
kura Done. "bedrooms" (number, required) added. The editor form now shows it.
Add kura to Claude Code, Cursor, or any MCP-compatible tool:
npx -y @kuracms/mcp Demo sites in your favourite framework
Browse a live one, open an editor copy and change something, or read the source on GitHub.
The Bistro Restaurant
A small Paris bistro menu in five sections. Server components fetch from kura. The page revalidates every minute, so a publish shows up on the menu within about a minute.
Inaka Properties
Vacant rural houses by prefecture. Photos, filters, an interactive map. Server-rendered on Cloudflare Workers.
Bloom Hair Salon
A hair salon on Auckland's Ponsonby Road. The home page, services list and the team page are all edited through kura - plus the privacy policy and T&Cs as plain markdown. Vue rendered on Cloudflare Workers by Nuxt 3.
Marlow Clothing
A small Brooklyn clothing label. Products, collections and a mock basket. Rendered on Cloudflare Workers by SvelteKit - the framework kura itself is built on.
The Sealed Room Co. Escape Rooms
A London escape-room operator. Built statically by Hugo: every page is a flat HTML file on Cloudflare's edge. Rebuilds when kura fires the deploy hook.
Our pricing
We've tried to keep this as simple as it gets. One price per site. No feature gates, no per-editor charges, no add-ons. The same $6 covers everything kura does.
$6/month per site
First month free, no card charged.
- Unlimited editor accounts
- Drafts and atomic publish (versions)
- Rich-text editor - bold, links, headings and lists
- Built-in image library with drag-to-reorder photo galleries
- Link entries together - categories, authors, agents
- REST API your frontend reads from
- Editors sign in with a one-time emailed link - no passwords
- Pause-not-delete if a payment is missed
Add a card to start. You are not charged during the first month. If you cancel inside that month, you pay nothing. After the first month, your card is charged $6 each month, or $60 once a year (two months free). If a payment fails, your project is paused and not deleted. You can start it again as soon as your card works.
Compare competitors
What each platform charges, for a small business with the team size and needs you pick below. Other content systems often look cheap at the start, but the price jumps a lot the moment your customer asks for something small - a draft copy, a second site, one more editor. With kura that price stays the same.
The price is the same whether kura runs one section of your site or all of it. $6 per site, unlimited editors, no per-seat charge.
The options above are paid, hosted CMSes. There are also free, open-source ones you can self-host - EmDash (Cloudflare's own), Strapi, Directus, Payload. They cost nothing, but you host and maintain them yourself. kura is for when you'd rather not: we host it, with nothing for you to set up or run.
Numbers from each vendor's published pricing as of May 2026. Where a tier or add-on is needed to fit the scenario, the cheapest qualifying option is used.
FAQ
Can I use kura for just part of my site?
Yes. kura runs whatever slice you point it at: the whole site, only the blog, or a single section like the menu or the team page. Hand-code the rest. The price is the same either way, and you can widen what kura owns later without a migration.
Where does my data live?
On Cloudflare. Your text and structured content go into a Cloudflare D1 database in their global edge network; your images and uploads go into Cloudflare R2 object storage - the same global network that fronts a large share of the web, including names like Shopify and Discord.
Can I take my content with me if I leave?
Yes, in one click. The settings page has a Download button that bundles every row in your project - content types, versions, entries (draft and published) and image references - into a single JSON file in a documented, open format. Your images sit in your Cloudflare R2 bucket where you already have direct access. No proprietary lock-in - though we don't yet ship a one-click importer into a fresh kura project.
Daily backups, plus export on demand
Every project is backed up daily to separate storage, and you can export all of your content as JSON at any time.
Does kura handle authentication?
Yes, but only for the people editing the website - not your visitors. Editors sign in here to change words, swap photos, update prices, then publish. Visitors browse your site as normal and never see kura. Once your developer has set the site up, they shouldn't need to come back unless the structure itself changes - new content type, new field. Routine content updates stay with the editor.
Is this just another headless CMS?
Pretty much - if you've seen Sanity, Contentful or Storyblok before, you'll recognise the shape. The difference is who it's for. kura is built for websites where the person editing the words isn't the person who built the site. The editor changes prices and photos; the builder doesn't have to be called back every time a menu changes.