Auto top-up
Usage & billing can add credit from a saved card when your balance falls below a line you pick, up to a monthly most you set. Each automatic top-up earns 5% more as credit, and while it is on your account runs 200 sandboxes at once instead of 100. A declined charge turns it off and never stops a running sandbox. Also runtime billing auto-top-up, the SDKs and /v1/billing/auto-top-up. See auto top-up.
Jobs in the console
A Jobs page lists every scheduled job: its schedule in words, its size, its last run and how it ended, its next run and this month's cost, with what needs you first. A job's page shows each run's state, start, length, exit code, cost and output, and pauses, resumes or cancels the job. See scheduled jobs.
Run a job now, or change its schedule
Run now starts one run at once, beside the job's schedule; a paused job runs once and stays paused. Change schedule moves the next run to the new schedule's next time, and a run going finishes as it started. On the job's page, runtime jobs trigger and runtime jobs reschedule, the SDKs, MCP and /v1/jobs/{id}:trigger and :reschedule. See jobs.
Secrets in the console
Settings → Secrets lists every secret your sandboxes and jobs use: the hosts each may reach, where its value goes, its rules, whether jobs have a copy, and who added and last changed it. Add a secret, replace its value or delete it there, as with runtime secrets. Values are never shown, there or anywhere. See secrets sandboxes never see.
Referrals pay on every payment, and for a year
When a company signs up with your link, every credit it adds in its first 30 days is matched for both of you, up to $1,000 for each company, not only its first top-up. Then, for 12 months, you earn 10% of what it spends from credit it paid for, up to $50,000 a year. Your link opens an invite page with the offer and a way to sign up. See referrals.
Creates stay fast with a thousand sandboxes
A create now costs the same beside a thousand of your account's sandboxes as beside none: what it checks (sandboxes at once, quotas, a server's room) is kept as a running total instead of counted again at each create. On a test database with one account on one server, a create's database work beside 1,000 sandboxes went from 11 to 85 ms to 6.3 to 9.7 ms, and 100 creates over 8 connections from 6 to 11.5 s to 0.5 to 0.6 s. Every limit holds exactly as before.