Projects and limits

A project is the compartment you keep resources in. Servers, SSH keys, firewalls, IP addresses and API tokens always belong to a project.

Your account starts with one project ready to use, and you can add as many as you need.

When to create a separate project

• Per customer: so different customers' servers never get mixed up.
• Per environment: separating production from testing lowers the risk of deleting the wrong server.
• Per automation: if you want a script to see only its own resources, give it a token from its own project.

Creating and deleting projects

Create a project with New project on the panel's home page. You can rename it later; the name is for you and does not affect any resource.

Deleting a project has two rules:

Projects and API tokens

Every API token belongs to the project it was created in and sees only that project's resources. A token reaching for another project's server gets not_found — not even the existence of the resource leaks.

If you run automation across several projects, create a separate token for each. Details: API tokens.

Balance is not split per project

Balance lives at the account level: all your projects draw on the same balance and all usage lands in the same transaction list. When the balance runs out the effect covers the whole account, not one project.

Each line in the list names the server it belongs to, so you can still see the per-project breakdown there.

Resource limits

Limits are per account — the total across all your projects counts.

Your current limits and how much of them you use are on the Limits page in the panel.

Once you reach a limit, requests to create new resources are rejected with resource_limit_exceeded.

Limits exist to contain abuse, not to slow you down. Reasonable increases for real workloads are granted quickly.