Limits and notices

Every account has limits: how many sandboxes run at once, the longest a sandbox may run, the largest size, data out a month and how much it keeps stored. promigence pricing shows your account's prices and limits; promigence me shows what is in use.

A new account runs 20 sandboxes at once, each for up to an hour (15 minutes unless --timeout asks for more), on sizes up to large (8 vCPU), with 20 GB of data out a month. Over a limit, the request is refused before anything starts: concurrency_limit, tier_over_plan, storage_limit_reached or egress_cap_reached. To raise a limit, email support@promigence.ai.

promigence pricing     # your prices and limits
promigence me          # your account, and what is in use

A new account starts with a short welcome in the browser: a few questions about you and what you are building.

If your account has setup questions to answer first, a command that starts new work (a run, a snapshot build, a verify) stops with setup_required (HTTP 403, exit 7) and a link to the questions; nothing is started or charged. Answer them, which takes under a minute, and run the command again. Everything else keeps working meanwhile: commands and files in sandboxes that are already running, pause and resume, reads, keys and billing.

A run's spend cap (--cap, or spend_cap in the API) is a hard limit. A run whose quote is over its cap is refused before it starts (cap_exceeded); promigence run quote shows the quote first.

A sandbox that reaches its run's cap while it runs is paused with its files and state kept: paused time is not billed, the sandbox shows pause_reason: spend_cap, and calls to it answer cap_paused. Raise the cap to go on, or end it:

promigence sandbox resume <sandbox_id> --cap <usd>   # go on, under a higher cap
promigence sandbox kill <sandbox_id>                 # or end it

A trial whose credits run out is paused the same way (credits_paused) and goes on once credits are added. A sandbox that cannot be paused is stopped at the cap, billed up to the cap and never past it.

A paused sandbox is not billed by the second and does not count against your concurrency limit. It is kept for 30 days, and resuming it starts the 30 days again.

• While it is paused, its pause_expires_at says when it will be deleted, with its files (promigence sandbox info <id> --json, the API and the SDK).
• In its last 7 days, the console shows the date on the sandbox, and an email goes to the organization's owner 7 days and 1 day before.
• A paused sandbox that reaches its 30 days is deleted and ends expired. Resume it before then to keep it.

Each organization has a monthly data-out allowance. When the organization reaches it:

• its sandboxes lose internet access but keep running: their commands and files still work through the CLI, the SDK and the API;
• their terminals and SSH sessions end, and new ones are refused until internet access comes back;
• new runs that need internet access are refused with egress_cap_reached (HTTP 403, exit 10); runs with --network none still start;
• an email goes to the organization's owner, at most one a day.

Everything comes back on the 1st of the month, 00:00 UTC. For more data out a month, email support@promigence.ai. A project that reaches its monthly spend cap has its sandboxes' internet access cut the same way; an owner raising the project's cap restores it for new sandboxes.

Promigence support can stop a sandbox or a run, for example when it breaks our terms or when you ask. It ends stopped_by_support (exit 12) with the reason in its message: promigence sandbox info <id> and the console's page for the sandbox show it, and promigence run status counts it.

The seconds it ran are billed, as a kill is, unless support found the cause was on our side: then the work since its last snapshot (or since it started), up to 24 hours, is credited back. Questions: email support@promigence.ai with the sandbox id.

With Promigence Runners on (CI, in the console), each CI job has its own page in the console: its repository, workflow, branch, commit and who started it; how long it waited for a runner, how long the runner took to be ready and how long it ran; the runner's size and what it cost; and, for a GitHub job, its steps and its log.

If a GitHub organization you connected has not accepted the Promigence App's updated permissions, the Runners page says so and links to the page on GitHub where an owner of that organization accepts them. Its repositories stay listed, and their jobs wait until then.