Guides

Guides

Three explanations of what happens under the bonnet. For practical questions — “where is the button”, “why is this not showing” — the help centre is quicker.

A diagram in three steps: one sentence describing what the system has to do, a build that is checked in which code that does not run is not saved, and a live app with a public address, tables and users.1One sentenceYou describe what it must do, and for whom2A build that is checkedCode that does not run is not saved — or billed3A live appA public address, tables and users of your own
Every build goes through these three steps. A build that failed its health check is not saved and not billed — nor is the automatic repair round that tried to rescue it.
How the security worksWhy there is no database key in the browser, and what exactly is checked on every request.How the price is setFrom measured tokens to a credit — including what happens when a build fails.Driving it from outside: API and MCPOne key, the same ownership checks, and eight tools for your agent.