Use cases

A few shapes kura fits, and how you'd set each up

kura is the content layer for a site - whatever part of the site that is. A few shapes it fits, with how you'd set each up.

A whole site

The straightforward case: every page's content lives in kura. Define a content type per kind of thing (pages, posts, listings, products), build your frontend against the API, and hand your client one admin to edit it all. The six example frontends are this shape.

Just the blog, or one section

You don't have to put the whole site in kura. Hand-code your marketing pages and let kura own only the part that changes - the blog, the menu, the price list, the team page. Define a content type for that one thing, read it from that one part of your frontend, and leave the rest static. There's no migration to widen later: add more content types when you want kura to own more.

This is often the easiest place to start: smaller schema, one part of the site, the same flat price.

A manual edit layer over imported data

If you already have data coming from somewhere - a scraper, an import, another system - kura can be the human review-and-correct layer on top of it. Your pipeline writes the records into kura content types (over the API), and an editor uses kura's clean admin to fix typos the import carried through, hide bad entries, and curate what's shown. Your frontend reads the corrected, published content.

The key point about today: kura holds the data. You bring records into kura content types; kura is the system of record. This is how Akiyahopper - kura's customer zero - uses it: scraped listing data written into kura, with a human curation layer on top.

What is not available yet (roadmap, v0.2+): pointing kura at your existing external database or table so it reads and writes your rows in place. There is no such adapter today. If you want kura now, your data lives in kura.

What kura deliberately is not

kura is content-only by design. It is not your visitors' login system, not a page builder, not an e-commerce backend. Bring your own auth (Supabase, Clerk, Better Auth), your own commerce (Shopify), your own forms. kura holds the content your frontend reads, and stays small so one person can run it reliably.

Ready to build one of these? Start with the tutorial or connect an existing site.