What happens when you build
You describe the app in a sentence or a paragraph. Kridona then runs four stages, and you watch each one happen live:
- It plans. A blueprint is drafted — pages, data model, who logs in and what they can see. You can read and approve it before anything is generated. Once approved, the plan is a contract: the build is not allowed to quietly ship something else.
- It generates. Frontend pages, an API, a database schema and authentication where the app needs it.
- It verifies. The app is compiled, its routes are walked, its forms are submitted and its pages are checked for the things that make a generated app look generated — dead links, unwired buttons, unreadable text, a broken phone layout. Problems found here are repaired before you ever see the app.
- It deploys. The app goes live on its own URL with its own database. Not a preview — the real thing.
A build takes roughly 15–25 minutes depending on how many pages the app has. If the build fails, you are not charged for it.
What a generated app is made of
This is the part third-party write-ups most often get wrong, so plainly: your app is a React single-page application built with Vite, using React Router, served by a Hono API running on a Cloudflare Worker, with its own Cloudflare D1 database and JWT authentication.
It is not a Next.js app and it is not deployed to Vercel. (Kridona's own website runs on Next.js — the apps it generates do not. That is where the confusion usually comes from.)
Every app is standalone. It does not call back into Kridona to run, it does not share a database with any other app, and nothing about it stops working if you stop paying — you keep the code, and hosting is the only thing that ends.
Every app also carries its own motion kit — one small file we wrote, no animation packages. It holds the scroll reveals, counters and the booking pop-up, and the effects motion-led sites are sold on: a shader gradient that drifts behind the first screen, a card that leans toward the pointer, layers at different depths, a dotted globe, a 3D carousel, a panel that stands up as you scroll, a phone mockup with the app inside, a spotlight that follows the cursor. Apps with a public face get one of these on their first screen in rotation; a personal tool keeps still. On any app you can ask the chat to “make it 3D” or “give it an animated background” and it composes from that same kit. Everything in it switches off for people who asked their device for less motion.
Where your data lives
Two layers, and they never mix:
Kridona, the platform you log into — your account, plan, credit balance and the record of your builds. Stored in a Postgres database on Supabase, served by an API on Railway, with the website on Vercel.
The apps you generate — every one gets its own private Cloudflare D1 database. Whatever your app's users type into it lives there and only there. It is never copied into Kridona's database and it is never shared with another app.
Your prompts and chat messages go to Anthropic to generate code. No AI model is trained on your data. The full list of subprocessors is in the Privacy Policy.
What a credit buys
- A full build costs 10 credits for an app up to 7 pages, then 1 more per extra page, capped at 15 credits however large the app is. The exact price is shown on the Build button before you spend anything.
- A chat edit costs 1, 2 or 5 credits — a wording or colour change, a section rewritten, or a whole page rebuilt. The tier is set by how much the model actually had to write, not by how you phrased the request.
- An edit that changes nothing costs nothing.
- A failed build is not charged.
- If a build is interrupted on our side — a server restart, an outage — the credits are returned automatically. You do not have to ask.
- Monthly credits roll over up to twice your monthly allowance.
- AI features running inside a generated app cost about 1 credit per 1,000 tokens. Connect your own Anthropic key in that app's Integrations screen and those calls cost you no credits at all.
- The same models are used on every plan. There is no plan-based model routing anywhere in the product — a Free build and a Studio build are generated by the same thing.
Prices and plan allowances are on the pricing page.
Changing the app afterwards
You change the app by talking to it. Ask for a new field, a different colour, another page, a new rule — it edits the real code and redeploys. Every version is kept, so a change you dislike can be rolled back.
Chat can also add capabilities the first build didn't include: AI features, email sending, file uploads, payments. When it adds one, the matching setup screen appears in the app's Integrations tab so you can connect your own keys.
Ownership, export and domains
Apps you build are yours. Export the whole project as a ZIP or push it to your own GitHub repository (paid plans), point your own domain at it, or take it and host it somewhere else entirely. The export is the real project — the same files that are running live, not a stripped sample.
Apps you buy are different, and the two stores differ from each other:
- Community Store app — a running copy that is yours to change: edit it in chat, rebrand it, publish it on your own domain. Five credits come with the purchase so you can start straight away.
- Marketplace app (built by Kridona) — a running copy you rebrand through the Branding & Design panels: name, logo, colours. Free-form chat editing is deliberately off on these, because they are tuned products and an open-ended edit is the fastest way to break one.
- Neither includes source export or GitHub push. That is the promise made to whoever built the app, and it is stated on the listing before you pay — not discovered afterwards.
Hosting and Care
Hosting is $9 a month per app you keep online, and it works on any plan including Free — its own database, automatic SSL, and your own domain included rather than sold as an upgrade. Paid plans include a number of hosted apps before that charge applies.
Kridona Care is another $9 a month per app: a nightly health check with screenshots, and an email the morning something breaks instead of a customer telling you.
Marketplace and Community Store
The Marketplace sells production-ready apps built by Kridona. Every listing has a live demo you can use before buying — real screens, real data, no video.
The Community Store sells apps built by Kridona users. The seller keeps 80% of every sale, every listing is reviewed by a human before it appears, and every listing carries a free live demo.
Reviews are only ever written by people who bought the app. We have never published a fabricated review, and a listing with no reviews says so rather than showing invented stars.
What Kridona is not for
Worth knowing before you spend anything. Kridona builds web applications — dashboards, booking systems, trackers, internal tools, customer portals, small SaaS products. It is a poor fit for:
- Native iOS or Android apps. What you get is a web app, installable to a phone home screen, but not a store submission.
- Games, 3D, video editing, or anything built around heavy real-time graphics.
- Taking over an existing codebase. Kridona builds new apps; it does not adopt yours.
- Regulated systems where a specialist must sign off — medical, banking-core, safety-critical.
- Very large products. An app of a few dozen pages is comfortable; a hundred-screen enterprise suite is not what this is.
Kridona is also young, and run by one person. That is a real trade-off, so it is on the page: what you get in exchange is that a human reads every support mail, and the numbers on the status page are the live ones, not a marketing figure.
Connect Claude
Kridona is an MCP server. Make a key under Settings → Connect Claude, add it to your Claude, and ask for apps in chat: it can list your apps, build a new one, check a build, get its address, change it in plain words, and publish it. Everything it does spends your credits and follows your plan, exactly as if you did it here.
Claude Code, one command:
claude mcp add --transport http kridona https://api.kridona.com/api/v1/mcp --header "Authorization: Bearer YOUR_KEY"
Claude Desktop, in claude_desktop_config.json:
{ "mcpServers": { "kridona": { "command": "npx",
"args": ["-y", "mcp-remote", "https://api.kridona.com/api/v1/mcp", "--header", "Authorization: Bearer YOUR_KEY"] } } }Then: “Build me a booking app for my barbershop and tell me when it’s live.” A key can be revoked at any time from the same screen. Any agent that speaks MCP works the same way — Cursor, n8n, your own.
Support
Write to support@kridona.com or use the support page. Refund terms are in the refund policy; the operator and address are in the imprint.