Concepts

Projects & accounts

How resource limits and pools work for your account and projects.

Your account is the top-level container — it owns billing, members, and the resource pool. Projects live inside your account; each project is an isolated environment where your apps run. Most users start with one or two projects (e.g. staging, prod) and grow from there.

Quotas

Each project draws RAM from your account pool — the sum of your tier baseline plus any extra RAM packs you’ve added. Storage is fixed per tier and allocated automatically, so it doesn’t draw from the pool.

If your pool is 8 GB and you’ve assigned 5 GB to prod and 2 GB to staging, your remaining pool is 1 GB. Bumping staging to 4 GB would need either shrinking prod first or buying an extra RAM pack.

Reallocation flow

When your agent wants to deploy something larger than the current project ceiling, the recommended pattern is:

Agent nyx_account_ram

Returns the pool baseline and remaining headroom.
Agent nyx_project_state <project>

Returns the project's current allocation and floor.
Agent nyx_project_ram <new value>

Resizes if the pool covers it — RAM rounds up to the next 256 MB step.

If the pool can’t cover the request, the agent surfaces a subscription-upgrade link instead of failing silently.

Your agent does this without prompting — nyx_brain’s cookbook includes the decision tree. You’d only see the upgrade prompt if the pool genuinely can’t accommodate the request.

Console

The per-project gauge and account-pool gauge live in the console at Projects → <name> → Resources. The same numbers are visible from the CLI via the nyx account / nyx project commands.

Next: The cookbook →