What Zero is
Zero is NNumbers' application platform. You point it at a repository; it builds the image, deploys the application, gives it a public HTTPS address, and keeps the version history — without you assembling a pipeline, administering servers, or learning the infrastructure underneath.
Build it. Zero runs it. You build. Zero puts it in production and operates it.
The problem it solves
Between "the code works on my machine" and "the application is live, with a domain, a certificate, logs, and history" lies a distance usually crossed in one of two ways, both bad for someone who just wanted to ship:
- Building the platform yourself — cluster, pipeline, traffic ingress, certificates, log collection, rollback policy. That is an entire team, and it is a team not working on your product.
- Renting a closed platform — fast on day one and opaque on the day you need to understand why the deployment failed.
Zero occupies exactly that layer. The complexity was absorbed by the platform, not pushed onto you.
What Zero is not
Every item on this list was an alternative considered and rejected.
| Zero is not | Why |
|---|---|
| An infrastructure console | You declare product concepts, never infrastructure objects |
| A server reseller | The unit is a running application, not a rented machine |
| A functions-only service | Long-running services and scheduled tasks are first-class citizens |
| A graphical interface for a cloud | No customer receives administrative infrastructure credentials |
In the NNumbers portfolio: Imaginne imagines and creates; Zero deploys, runs, and operates; Infinite Data integrates, processes, and governs data; NNumbers Cloud provides the infrastructure.
Who it is for
The target user knows how to point at a repository and knows the application needs to be online. They do not need to learn how the platform does that internally.
- People shipping an application — repository, deploy, address.
- People operating a product — version history, rollback, variables by scope, logs, and metering.
- People operating with agents — Imaginne, or any authorized agent, uses exactly the same API, with the same permissions as the person who triggered it.
What you get without configuring anything
| Capability | How it works |
|---|---|
| Build from the code | The platform builds the image from the repository's Dockerfile |
| Public HTTPS address | Every project gets an address; the certificate is issued and renewed automatically |
| Deployment without interruption | The previous version keeps serving until the new one answers |
| Immutable history | Every deployment creates a new version; none is overwritten |
| Rollback | Restoring a previous version is a pointer switch, not a rebuild |
| Logs and metering | Application output, build output, and traffic, with no agent to install |
How Zero talks to you
Two communication rules hold across the whole product surface:
No long operation pretends to be instant. Deploying goes through build, image push, and activation. The immediate response is not the result: it is the progress. You see Preparing → Building → Deploying → Verifying → Online.
Missing data never becomes zero. An error rate with no requests measured shows as "not measured", not as "0%". The two mean opposite things, and confusing them sends you looking for a problem in the wrong place.
Next steps
- Quickstart — deploy your first application.
- Getting to know the console — how the interface is organized.
- Zero concepts — the full mental model.
- What exists today — the honest list of capabilities.
Was this page helpful?
Report a problem on this pageDo not send passwords, keys, tokens, or customer data.