Skip to main content
Every Rigbox account has limits on workspaces, resources, and AI credits based on your plan tier. This page covers what’s available and how to check your usage.

Plan tiers

Plan limits cover workspace count, per-workspace CPU/RAM/disk, apps, snapshots, SSH keys, and managed AI credits. Use your account’s reported limits as the source of truth; limits can vary by plan and account configuration.

Check your limits

Show your current plan limits and usage:
The output includes both the maximum allowed and current usage for each resource type. See Get User Limits for the full response schema.

Workspace resources

When creating a workspace, you specify RAM, vCPU, and disk allocation. These are validated against your plan limits:
Requests that exceed a resource limit are rejected with an error identifying the constraint. Do not assume every quota failure uses the same HTTP status.

Resizing

You can resize a workspace after creation. The workspace must be stopped first:
See Update Workspace Resources for details.

AI credits

AI credits fund requests through the managed AI proxy. Each credit maps to approximately $0.01 of upstream provider cost, though the exact rate depends on the model and token count.

Check your balance

View usage breakdown

Shows daily usage broken down by workspace, provider, and model.

When credits run out

  • AI requests through the proxy return 402
  • Non-AI services in your workspace continue running
  • Switch to BYOK mode to use your own provider account, subject to its limits

Rate limits

API requests can be rate-limited. Treat the response and any Retry-After header as authoritative instead of assuming a fixed rate across endpoints. When rate-limited, the API returns 429 Too Many Requests. Implement exponential backoff in your client:

Capacity

Before creating a workspace, check if the platform has capacity:
Inspect the returned availability before provisioning. Capacity is a point-in-time observation, not a reservation. Rigbox also tracks per-node runtime capacity internally, including bridge IP leases for running VMs. Each compute node has 253 active VM bridge IPs available (172.16.0.2 through 172.16.0.254), and stopped or deleted workspaces release their active IP lease.

Learn more

Architecture

How the platform is structured

Managed AI Proxy

How credits and the AI proxy work