Describe what you need — and get a real app
Not sure where to start? Try one of these:
No credit card · or start from a ready-made template
A real database
Every table is built from your description, with fields, and records that are actually stored — not temporary state in a browser tab.
Accounts for your users
Sign-up, e-mail verification and login — for your site, not ours. With a free address of its own from the first minute.
Permissions the server enforces
"Only the person who created it can see it" is not a suggestion in the code — it is a rule the server checks on every request.
A live address, straight away
Every project gets a public address and a project code, shown at the top of every screen.
History you can walk back into
Every build is a version. Restoring brings back the code and the data structure together — and does not delete what came after it.
Priced by what was actually used
Billed from measured tokens, after the version is saved. A build that failed is not billed at all.
While it builds
Not a loading screen. Stages with names.
The plan is written once, and then every page is written at the same time — not one after another. Each stage appears on screen while it runs. These are the five, in order:
- 01Planning the app
- 02Building the shared frame
- 03Writing the pages in parallel
- 04Checking the code really runs
- 05Saving a version
The fourth is a limit, not a decoration: code that fails the check is not saved and not billed — nor is the automatic repair round that tried to rescue it.
Who it's for
For someone running a business, not a server
You do not need to know how to code. Describe what the system should do and for whom, then carry on in ordinary language: "add a gallery page", "move the form to the home page". The code is written and you can read it — but you never have to touch it.
What the others leave unwritten
Three things that are easy to promise and hard to keep, which is why almost nobody puts them in writing.
A build that fails the health check is not saved — and not billed. Neither are its repair rounds.
No record is reachable with a public key. The server is the only door, and that is checked automatically on every change.
A ceiling per build, per day and per month. When you reach it, it stops — it does not carry on and send you a bill.
Handing it on
Give someone a key without giving them the whole ring
An invitation goes to one e-mail address, carries a role — member or admin — and lasts up to thirty days. The link is shown once, at the moment it is created: only its hash is stored, so even we cannot send it again.
While an invitation is still unused you can cancel it. All of this is written to an activity log kept for every app.
And for anyone who arrives without an invitation: you can put the app into approval mode, and every new sign-up waits for you. Whoever is already in stays in — turning the switch on does not lock out people who are already through the door.
Choose how to start
30 credits to begin with, and 10 more every month. No credit card.
- Unlimited projects
- Up to 3 published apps at once
- Accounts for your site's users
- An API key and an MCP server
More credits, and no ceiling on published sites.
- 250 credits every month
- Unlimited published apps
- Everything else is open on the free plan too — that is the only difference
Common questions
What exactly do I get?+
A site or an app running at a real address, with a database of its own, accounts for your users, and permissions enforced on the server. Not a prototype and not a picture — you can send someone the link the same day.
Do I need to know how to code?+
No. Describe what the app should do and for whom, then carry on in ordinary language: "add a gallery page", "move the form to the home page". The code is written and you can read it, but you never have to touch it.
How is a credit measured?+
From the tokens actually used, after a version has passed the health check and been saved. Before every build you see an estimate and the ceilings you set are checked — and if the request goes over one, it stops before a single token is spent.
What happens if a build fails?+
No version is saved and no credit is charged — including the automatic repair rounds. Those tokens are on us, because you asked for a working app, not an attempt.
Who can see the data stored in my app?+
Whoever that table's rule allows, and the server checks it on every request. When the rule is "only the person who created it", the filter goes inside the query itself — a mistake returns zero rows, not another customer's rows. The record tables are closed to the public key completely, so there is no way to read them from a browser.
The people who sign up to my site — are they your users?+
No. They sign up to your site alone, and their session belongs to your app. A token taken from one site is treated at another as not signed in.
Can I use my own domain?+
Not yet. Every project gets a free address of its own from the first minute, and connecting a domain you own is being built — we will say so here the moment it is live. We will not sell it before then.
Can I go back if a change broke something?+
Yes. Every build is a version, and restoring points at an earlier one without deleting what came after it — you can go forward again too.
What happens to the data if I delete a project?+
The address stops answering immediately. The data is kept so it can be restored and is no longer reachable from the system. An export to a file is available at any moment from the data screen.
The templates — are they pictures or sites?+
Sites. Every template in the catalogue runs at an address of its own, sign-up and login included, and only appears there after a browser has loaded it and moved between its pages successfully.
Once it's live
You close the laptop, and it keeps working
The address keeps answering. The traffic screen shows how many people came, where from and which pages they read — and every number there is worked out in the database itself rather than counted in the browser, because a number that looks right and is wrong is worse than an error.
The spend ceilings you set stop at the point you chose instead of carrying on and sending you a bill. And every build is a version, so if something breaks there is somewhere to go back to — without deleting what was done after it.
