Account phases

Your account is always in exactly one phase. The phase decides what the account can do, what happens next and by when. The dashboard shows the phase in one line and links here; the same answer reaches gh0stcli and your assistant, so every surface tells you the same thing.

Provisioning

The account has just been created and your environment is still being set up. Everything is read-only for a few minutes. Nothing is owed; the starting credit is already there.

Trial

The account runs on its starting credit. Nothing is owed, and you can create projects, connect a repository and deploy. Two things are different from a full account:

• Only stable applications are offered from the catalog. Beta and experimental work opens up once the account is full.
• When the credit runs out, the account moves to attention and, if nothing happens, its workloads stop and the account is eventually deleted (see suspended).

Topping up credit or setting up a payment method ends the trial and makes the account a full account.

Active

A full account that is in good standing. Everything is available; the catalog shows what you opted in to under early access. The only date on an active account is the due date of an open invoice.

Attention required

Something is about to end, and the dashboard names the date and the one thing that resolves it.

• On a trial: the starting credit is used up. You have seven days to top up before the workloads stop.
• On a full account: an invoice is overdue. You have fourteen days to pay before the account is disabled.

You receive a mail with the date in the subject at the start of the period.

Disabled

A full account whose invoice stayed unpaid for fourteen days. The workloads are stopped and your data is kept. A disabled account is never deleted. Everything is refused except what you need to pay: invoices, topping up, the payment method and your billing details. Paying every open invoice restores the account to active, with the workloads started again.

Suspended

A trial account whose credit ran out and was not topped up in time. The workloads are stopped and the data is kept for fourteen days. Topping up within that time restores the account and makes it a full account. After fourteen days the account is queued for deletion.

Deletion

The account and its data are removed. This only ever happens to an account that never became a full account. A full account that stops paying is disabled, not deleted.

Unknown

If the dashboard shows an unknown phase, the platform stored a state this version of the portal does not know. Nothing is assumed to be healthy in that case; the reason is shown and the account keeps its data. Contact support if it stays that way.

Full account

A full account is one that has paid: either a credited top-up or a completed payment setup, manual or automatic collection alike. Once an account is full it stays full: a later empty balance or a revoked mandate does not turn it back into a trial. Being full is what keeps the account off the deletion path and opens the catalog to your early-access choice.

Before the first top-up, the billing details have to be complete (name, invoice email and a billing address) so that the invoice is valid. The dashboard lists the missing fields and links to where they are entered.

Journey

Besides the phase, the dashboard shows where the account is on its way from nothing to a running workload, with one list of steps:

1. Organization: billing details complete.
2. Project and namespace: the first project with a namespace.
3. GitOps repository: a repository binding that has synced.
4. Secret store: the secret store confirmed.
5. Network and exposure: a route or an exposure policy.
6. Storage and backup: a volume, a backup binding or a managed service.
7. Full account: a top-up or a payment method.

The stage (setting up, exploring, building, running, growing) is derived from those steps; nothing is chosen or stored. A step that needs a change to your environment is blocked while the account is disabled or suspended, with the reason next to it.

Tiers

Every account has a plan tier: starter, standard or enterprise. The tier sets your environment's limits (how many projects, namespaces and repository bindings it may have) and the default policy bundle behind them: compute quota, storage, network and exposure bounds. A new account is always a starter. The dashboard shows the limits and how much of them is in use.

Stepping up is a change request: the platform applies the new tier's bundle and limits. When an account uses three quarters of a limit, or runs managed services on the starter tier, the dashboard and your assistant point that out.

Whether you run the application yourself or we operate it for you is the account's mode, not its tier. See operating models.

Feature access

The catalog of operated applications is graded stable, beta and experimental. Your early-access setting on the customer page chooses the highest grade you want to see. The phase caps it: a trial account sees stable applications only, an account under attention as well, and a disabled or suspended account has no catalog until it is restored. An active full account sees what it opted in to.

Profile

Your assistant learns how experienced you are, what your role is and whether you prefer guided or concise help from the way you work with it, and records that on your account so it does not have to ask again. It shapes how the assistant explains things; the portal does not change with it, and nothing else does. You can tell the assistant to change or forget it at any time.

Notices

You receive a mail, in your language, when something starts or ends: the start of an attention period with its date, workloads stopping, an overdue invoice, the account being disabled or restored. Every mail names the date in its subject and links to the page that resolves it. The dashboard shows the same date; the two cannot disagree because both read the same state.