You build it. Zero runs it.
Zero turns a repository into a running application — with build, deployment, a public address, HTTPS, variables, logs, and version history. No pipeline to assemble, no infrastructure to administer.
This is the official documentation for people who deploy and operate applications on Zero. It covers everything from your first deployment to the reference for states, addresses, and limits.
Choose where to start
Point at a repository and get your first application running.
Start →Get to know the consoleHow the console is organized: organization, projects, and what lives inside each one.
Explore →Mental modelProject, environment, service, deployment. Five words explain the product.
Understand →Your own domainPublish under your company's domain, with a certificate issued automatically.
Set up →An application's path
Every project follows the same path, and each step has a page here.
Name, address, source of the code. The production environment is created with it.
Open →DeployWhat happens between confirming and the application answering at its address.
Open →ConfigureVariables, secrets, and resources — and where each value takes effect.
Open →Keep trackTraffic, consumption, application logs, and build logs.
Open →Reference
What each state means, and what to do in each one.
Open →GlossaryThe product's words, with the exact meaning they carry here.
Open →What exists todayThe honest list of what the platform does today and what it does not do yet.
Open →Common problemsA deployment that fails, an address that does not answer, a log that does not appear.
Open →Zero does not hand you a cluster to administer. It hands you the running application — and absorbs the infrastructure underneath. You declare product concepts (project, service, address, variable), never infrastructure objects.
Was this page helpful?
Report a problem on this pageDo not send passwords, keys, tokens, or customer data.