Getting to know the console
The Zero console lives at console.zero.nnumbers.com.br. It has two levels of navigation: the organization and the project.
The organization
The organization is the global filter: it decides the meaning of every action. If you belong to more than one, the console asks which before opening anything.
At the organization level you find:
| Section | What it shows |
|---|---|
| Overview | The organization at a glance: projects, recent deployments, what needs attention |
| Projects | The project list, with address and the state of the latest deployment |
| Deployments | Every deployment in the organization, newest first |
| Domains | The organization's custom domain zones |
| Activity | The history of operations: deployments, rollbacks, cancellations |
| Settings | Variables and secrets at organization scope |
| Users | Who exists in the identity provider and each person's access to Zero — see Users and access |
The project
The project is the application. Entering a project replaces the entire side navigation: everything that hangs off it lives inside.
| Section | What you do |
|---|---|
| Overview | Current state, address, latest deployment, shortcut to deploy |
| Deployments | The deployment in progress and the history, with detail and rollback |
| Domains | The project's public address, changing the address, and how far it is confirmed |
| Services | What is running, with type, replicas, and schedule |
| Variables | Configuration the application reads, with inheritance in plain sight |
| Secrets | Sensitive values — they go in once and do not come out |
| Source | The repository the project deploys from, the branch or tag, and the access token |
| Build and deploy | How the image is built |
| Runtime | The port, command, and health check applied |
| Scale and availability | Instances, autoscaling, and the size of each instance: CPU and memory reserved, maximums, and observed usage |
| Observability | Traffic and consumption measured |
| Logs | Application output, build output, and the platform's narrative |
| Settings | Name and project deletion |
A project with a single service shows that service directly, with no intermediate layer. The Services section gets content of its own when the project has more than one — a web service and a background process, for example. See Services.
The vocabulary on screen
The console uses few words, and each one means exactly one thing.
| Word | Meaning |
|---|---|
| Organization | The tenant: the boundary of access, metering, and audit |
| Project | The application: it is what has an address, versions, and history |
| Environment | The deployment target. Every project is born with Production |
| Service | A unit that runs inside the project |
| Deployment | A deployment, with its state and its history |
The word "application" does not appear as a separate object in the interface: the project is the application. The full glossary is in Glossary.
When a screen says something does not exist
The console distinguishes six situations that are often collapsed into a single "no data":
| What the screen says | What it means | What to do |
|---|---|---|
| Ready | There is data | Nothing |
| No data | The path works and there was nothing to measure | Wait, widen the period, or generate traffic |
| Not configured | A step of yours is missing | The screen says which and where |
| Degraded | There was data and collection fell behind | The numbers are still valid; their age is the information |
| Unavailable | The capability exists in the product, not in this installation | Nothing on your part |
| Not available yet | Nothing produces that data today | Nothing — and the screen promises no date |
This distinction exists because each one leads to a different action. The list of what sits in each state today is in What exists today.
Next steps
Was this page helpful?
Report a problem on this pageDo not send passwords, keys, tokens, or customer data.