Orgs, usage and billing

Your org owns your sandboxes, templates, keys and vault; see its quotas, current use, per-second usage and estimated cost.

Everything in pols belongs to an org: sandboxes, templates, API keys, SSH keys and the vault. An API key acts on its own org only, and names of sandboxes and templates are unique within an org.

Accounts and orgs

You sign up at https://my.pols.so/signup with your email address; there is no password. Each address can have one account, and every new account gets an org of its own with the default quotas.

New accounts are approved by hand. Until yours is approved you can log in, but not create API keys; you get an email once it is approved.

Your account page shows your org’s API keys, its vault, its sandboxes with their current CPU, memory and disk use, and its usage against its quotas.

Your org from the CLI

pols org      # the org, its quotas and what it uses right now
pols usage    # per-second usage and estimated cost, this calendar month
pols usage --from 2026-09-01T00:00:00Z --to 2026-10-01T00:00:00Z
pols stats    # CPU, memory and disk use of the running sandboxes

The same data is in the API: GET /v1/org, GET /v1/usage and GET /v1/org/stats.

Usage and billing

pols meters running time per second. Every time a sandbox starts or stops, the change is recorded together with the status change, so the record of running intervals is exact. pols usage adds them up per size and per sandbox and prices them at the list prices:

• Only running time counts. Stopped sandboxes, templates and the disks behind them are not billed.
• Usage defaults to the current calendar month in UTC; --from and --to take RFC 3339 times.
• The cost shown is an estimate at list prices. During early access we invoice usage by hand.

Notices

At 80 percent of the monthly sandbox-hours, the org’s users get an email. At 100 percent, the org’s running sandboxes are stopped until the next month or until the quota is raised; see Limits and quotas.