What exists today

Zero shows what it does not do as clearly as it shows what it does. A screen that promises and delivers emptiness teaches you to distrust all the others.

This page is the same truth, written outside the console. The console answers by capability and by organization — what you see there is always this installation's answer.

Available

Capability	Where
Creating a project from a GitHub, GitLab, or Bitbucket repository	Projects
Private repository, with an access token in the project source	The project source
Building from a Dockerfile	How the image is built
Deployment with verification before the traffic switch	Deploy
Failure reason when the application does not become ready	Deployment states
History of deployments and attempts	Following
Restoring a previous version	Restore
Public address with HTTPS	Project address
Choosing and checking the address	Project address
Changing the public address, with no gap without an address	Changing the address
Custom domain: delegated subzone or DNS kept by you	Custom domain
Deleting a project, with its history preserved	Deleting the project
Variables and secrets in three scopes	Configuration
Resources and limits per service	Resources and limits
Instances and autoscaling	Scale and availability
High availability: instances across different machines	Scale and availability
Promoting the tested version between environments, without rebuilding	Promoting
CLI, TypeScript and Go SDKs, MCP server	Tools
Build log	Logs
Application log	Logs
Traffic: requests, latency, errors, routes	Traffic and consumption
Consumption: CPU, memory, instances	Traffic and consumption
Organization activity	Activity
Users and access: grant, change, revoke and create people, with no invitations	Users and access
Networking between projects: blocked by default, permission per service	Networking between projects
Internal project, with no internet address	Internal project
Internal name per service (<name>.zero.internal)	Internal name
Gateway internal entries, with prefix paths	Gateway internal entries

Depends on activation in this installation

These capabilities exist in the product and may be switched off for your organization. When they are, the console says so — and the action belongs to the team that administers the platform, not to you.

Capability	Note
Consumption collection	Depends on collection being active; the console distinguishes "not configured" from "no data"

Does not exist yet

Nothing in the product produces this today. No date is promised, and the screen says so rather than showing an empty section.

Capability	What the console answers
Alerts	This installation does not evaluate alert rules
Connecting a code provider	There is no organization-level connection to GitHub, GitLab, or Bitbucket; each project keeps its own source, and pushing code does not deploy on its own
Security report	Depends on checks this installation does not run yet
Consumption presented	Consumption is measured and is not yet presented in the console
Managed databases and storage	Not exposed in this installation
Timeline of configuration changes	Activity covers operations; variable and access changes do not show up there yet (access changes are in the audit trail)

How the console communicates each case

State	Meaning	Any action from you?
Ready	There is data	No
No data	It measures and there was nothing to measure	Widen the period or generate traffic
Not configured	A step of yours is missing	Yes — the screen says which
Degraded	There was data and collection fell behind	No; the sample's age is the information
Unavailable	It exists in the product, not in this installation	No
Not available yet	Nothing produces that data	No

Next steps

• Getting to know the console
• Release notes
• Common problems