Billing
How a monthly plan ($10 to $1,000, or sized to your boxes past that) becomes credit, what boxes cost by the hour, and what happens when the credit runs out.
On this page15
How it works
A plan, any rung from $10 to $1,000 a month, lands at least that much credit every cycle; every box meters against it by the second, quoted by the hour:
| Box state | Rate |
|---|---|
| Awake | Its monthly price spread over a 730 hour month: a Small is $100 a month, so $0.137 an hour. |
| Asleep | $0.0001 per GB hour of the disk the box actually has, or of its size's full disk while a new box's disk is still growing into it; a Small asleep for a month is about $22. A box that kept a bigger disk pays that rate on the extra disk, asleep or awake. |
| Infinite storage | The box bills as its size with that size's disk, awake or asleep, plus $0.05 a GB-month for what its files take up in storage beyond that disk, as Prized measures it (after compression): a Small (300 GB) holding 1.3 TB pays $50 a month more. How much each size and each workspace can hold is on Boxes. |
Infinite storage bills each recorded size for as long as it was in force: a smaller size lowers the charge from then on, not for the time before.
- Pausing keeps the money. Pause from the dashboard or with auto-pause;
prized sshwakes the box. - A box that failed to launch costs nothing. It meters at zero until you delete it; usage from before a later failure still counts.
- Credit rolls over up to two months of your plan; the excess lapses when a cycle's credit lands, as its own line in your activity. Top-up and free credit are spared that trim for two months after they land.
- Each rung runs one size around the clock: $10 a Nano, $100 a Small, $1,000 an Extra Large. The credit spends on any mix.
- Long cycles land more credit. Rates assume 730 hours; a calendar cycle of up to 744 lands proportionally more, at no extra charge.
- A fleet bigger than the biggest rung gets a plan sized exactly to it: an Extra Large plus a Small is a $1,100/mo plan.
Free credit
New workspaces get $30 of free credit, once per person, as the owner walks through onboarding or first signs in with prized login through the browser (an account a coding agent made gets it, or not, when its code is checked: Agent sign-in); it spends like paid credit, and the tour starts a box on it with no card. It does not refill: at zero, boxes pause (Running out) and the dashboard opens on the plan picker. Choosing a plan keeps what is left, and the first cycle's credit lands at once. If the workspace has one box and it is asleep, however it got there, the first plan starts it, and so does a top-up once the credit is spent. A workspace whose owner already took the free credit, on the same email address or the same Google or GitHub account, gets none, including after erasing the first workspace. It is once per computer too: an account signed up from a browser or a computer that recently took it for another account, or from a network where many accounts took it the same day, doesn't get it. The same goes for prized login: if a computer signed in in the last 30 days to another person's account that took the credit, a newer account it signs in to that got the credit has what is left of it removed. Such an account still works: start a plan or a top-up, or write to if you think it is a mistake.
An owner who signs up from a Sandboxes link gets the same credit with no tour and no box: the dashboard opens on Sandboxes. So does a new owner who opens the API keys page before picking a box, and the dashboard opens on API keys.
While the workspace runs on the free credit alone:
| Rule | Detail |
|---|---|
| Nano, Micro, Extra Small, or Small only | Medium and larger need a plan (on the credit alone, the API answers 409 tier_unavailable, with the same link to Billing). Any plan unlocks every size, so the tour and the create form quote them from $10/mo. On the tour, pick the size (and a region), then one of its plans, each with what it buys that size: the cheapest buy less than a big size's disk costs asleep and the list says so, so the one picked for you is the cheapest that runs the size at least an hour a day (Medium $50, Large $100, Extra Large $250). The box launches at that size once the first cycle's credit lands, with a 2-hour idle pause when the plan is below its around-the-clock price. A create that names no size gets a Small. Awake around the clock, the credit lasts about three months on a Nano, five weeks on a Micro, nine days on a Small; used eight hours a day and asleep the rest (below), a Small runs about 15 days. |
| One box at a time | A second create (prized box new, the API, a restore, or a fork) answers 409 box_limit, whose message names the plan that lifts it, says a one-time top-up does not, and links Billing, and the dashboard's create form turns Create box off and says so, with Pick a plan under it; delete the box to free the slot. A deleted box holds the slot until it finishes shutting down, usually within a minute or two. A plan raises the cap to the plan's (Limits). |
| No process at full CPU for more than 30 minutes, unless it is development work | One process holding the whole box at full CPU that long starts an automated review of the box's processes and the workspace's recent commands. Development work, a runaway dev server included, keeps running on your credit; anything else pauses the workspace's boxes, and creating or waking one answers 409 workspace_held with the reason. A process at a full core for 5 minutes on the free credit can be reviewed sooner, whatever the rest of the box does, and that review pauses the workspace only for mining. Builds, tests, agents and single-threaded jobs keep running; a long job that fills every core belongs on a plan, and starting one lifts the pause at once. Left paused, the boxes' disks go the way of any hold. |
All three lift the moment a plan is live, which is when its first payment goes through: a declined or unfinished checkout leaves them in place and launches no box. Every link these limits give opens Billing with the cheapest plan that lifts them picked. A box started on the credit keeps its settings.
A box on the free credit sleeps when nobody is using it. After 2 hours idle it pauses itself (Auto-pause), so the credit goes on the hours you use it: asleep, a box costs only its disk. On the default it never pauses itself in its first 24 hours, while the first sync and setup land; a window you set applies from the start. A coding agent's screen stops counting as use after 4 hours with nobody typing and nothing else going on. prized ssh or prized up wakes it, with everything where you left it. Change the window per box on its dashboard page or with prized box auto-pause BOX 4h, up to 12 hours: off, or a longer window, pauses the box after 12 hours idle, never in its first 24 hours. A plan lifts the default and the 12-hour limit, a top-up lifts the 12-hour limit, and a window you set, off included, stays.
Sandboxes on the free credit run within the free tier: up to 10 at once, each up to 2 vCPU, 4 GB of memory and 60 minutes. They draw on the credit at the sandbox rates, and the full-CPU rule above holds for them too. A top-up or a plan lifts them to the full quotas.
Deal credit
A workspace on a deal from Prized, such as a startup program, gets credit every month until the deal's last day. Until you start a plan, the Billing page shows the amount and the last day, which ends at midnight Pacific time.
YC founders get the YC deal by clicking Redeem on Prized's deal in Bookface, then signing in at prized.dev with the same email, or with the email they gave in the deal's form. The credit lands on their workspace (on an account a coding agent made, once they keep or revoke the agent's key at their first sign-in), and a cofounder who redeems adds theirs to the same workspace once they've joined it. A company gets the deal once: after its last day, or in its last 24 hours, a founder who redeems doesn't add credit or start a new deal on any workspace.
- It spends like any credit, on any mix of boxes and sandboxes. The free credit's one-box and size limits don't apply. The first month's credit lands the day the deal starts, then once a month, counted back from the day after the last day: a deal that starts October 27 for three months gets credit on October 27, November 27 and December 27, and its last day is January 26.
- Boxes pause after 2 hours idle, as on the free credit: never in a box's first 24 hours, and you can change the window or switch it off per box. A workspace auto-pause floor does not apply, and a plan lifts the default.
- GPU boxes need a plan of your own.
- A plan started during the deal keeps every unspent deal dollar: the rollover cap bounds the plan's own credit, never the deal's.
- After the last day, deal credit you haven't spent is removed, and we don't email you about it. Any other credit stays, including credit you paid for. A plan carries on and bills as usual.
- Your boxes keep running for a month after the last day, never paused on the day the deal ends. What they use past your credit that month bills at the month's end to your card, if you added one (pay as you go) or started a plan by then. With neither, the boxes pause with their files kept and that month isn't billed; a plan or a top-up starts them again. Without a card, the month stops early, from its second day, once it has used a full month of the deal's credit. A team already on a paid plan when the deal ends skips the month: its plan, and its overage setting, carry on as before. A plan started during the month carries it to its last day whatever its overage switch says (while its card is failing, the month can stop early, as it does without a card); switch overage off, or choose Pause at zero now under it, and the month ends there, with the balance as the stop again.
Pay as you go
A workspace on a deal can add a card from the Billing page, under Plan. It's optional, and the deal never needs it. Adding one charges nothing that day: the deal's credit is spent first, and once it runs out or the deal ends, what your boxes use bills to the card once a month at the same hourly rates. The Billing page shows what has built up and the date it bills. Boxes keep the 2-hour idle pause, which you can change per box. If a payment fails, boxes keep running for 7 days while the card is retried. Cancel from the Billing page and the plan stops at the end of the period, with what was used by then billed to the card. GPU boxes still need a plan that lands credit, and you can move to any plan on the ladder from the same page.
Sizes and rates
| Size | Specs | Disk | Awake | Asleep | Plan that runs it 24/7 |
|---|---|---|---|---|---|
| Nano | 2 vCPU / 2 GB | 40 GB | $0.014 an hour | $0.004 an hour | $10 a month |
| Micro | 2 vCPU / 4 GB | 80 GB | $0.034 an hour | $0.008 an hour | $25 a month |
| Extra Small | 2 vCPU / 8 GB | 150 GB | $0.068 an hour | $0.015 an hour | $50 a month |
| Small | 4 vCPU / 16 GB | 300 GB | $0.137 an hour | $0.030 an hour | $100 a month |
| Medium | 8 vCPU / 32 GB | 500 GB | $0.342 an hour | $0.050 an hour | $250 a month |
| Large | 16 vCPU / 64 GB | 1 TB | $0.685 an hour | $0.100 an hour | $500 a month |
| Extra Large | 32 vCPU / 128 GB | 2 TB | $1.370 an hour | $0.200 an hour | $1,000 a month |
The last column is the most a box can cost in a month, and the plan that runs it around the clock. The pricing page compares renting the same machine elsewhere. GPU boxes are billed by the hour from the prepaid balance only, never on overage.
Sandboxes
Sandboxes spend the same balance, metered per second with no minimum by the shape they hold: running, by vCPU, memory, and disk; paused, no compute, and their disk and saved memory count toward the workspace's paused storage.
| Resource | Running | Paused |
|---|---|---|
| vCPU | $0.04 per vCPU-hour | Not charged |
| Memory | $0.0125 per GB-hour | Saved memory counts as paused storage |
| Disk | $0.0001 per GB-hour | Counts as paused storage |
| Paused storage, per workspace | Not charged | First 20 GB included, then $0.05 per GB-month |
| Shape | Running | Paused |
|---|---|---|
| 1 vCPU, 2 GB, 10 GB disk | $0.066 an hour | 12 GB of paused storage |
| 2 vCPU, 4 GB, 10 GB disk | $0.131 an hour | 14 GB of paused storage |
| 4 vCPU, 8 GB, 10 GB disk (the default) | $0.261 an hour | 18 GB of paused storage |
| 8 vCPU, 16 GB, 10 GB disk | $0.521 an hour | 26 GB of paused storage |
| 32 vCPU, 128 GB, 10 GB disk (the largest) | $2.881 an hour | 138 GB of paused storage |
- Any balance above zero starts them. On the free credit alone they run within the free tier, from any template but
prized-docker-v1; once the workspace has paid in (a plan or a top-up), the full quotas apply. An empty balance answers409 insufficient_balance. No plan is needed, and the four-hour check for boxes does not apply. - Their run time is capped. A running sandbox is deleted when its run time ends, so a forgotten one cannot run up compute past that: 60 minutes of running on the free tier; once paid in, 24 hours by default and at most 7 days ahead unless you extend it again (on a custom plan, at the end you set) (Run time). A paused one bills storage until you delete it or
autoDeleteMindoes; on the free tier it is deleted 30 days after its last use (Paused retention). - At zero, they pause. With overage off, running sandboxes pause when the balance runs out and stay paused until you resume them; with it on, they keep running, as boxes do.
- Paused storage is per workspace. Every paused sandbox's disk and saved memory add up to the workspace's paused storage; a sandbox moved to a new machine without its paused memory (see
memoryDiscardedAtin the sandbox object) holds its disk alone until it runs again. The first 20 GB are included; past that it bills $0.05 per GB-month, prorated, and is listed on its own line, Paused sandbox storage past 20 GB included, under Recent activity on the Billing page. A 4 vCPU, 8 GB sandbox with the 10 GB disk holds 18 GB paused. - A sandbox that never came up costs nothing, like a box that failed to launch, and a create or resume still waiting to start bills no compute.
- Compute runs from start to pause. It starts the moment the sandbox runs and stops once it is
paused; while it ispausingwith its VM still running, it bills as running. A pause that fails because the VM itself failed lands the sandbox inerrorand stops the bill there. A delete stops the bill at once. - Every size bills at the same rates. A 32 vCPU sandbox pays per vCPU and per GB exactly as a small one does.
Choosing and changing the plan
The owner picks a plan on the Billing page, or on the tour's payment step once the free credit is spent. Payment is Stripe Checkout, cards only, and the first cycle's credit lands before you are back; with no box yet, choosing a plan starts one at the size picked with it on the tour, or else the size that plan runs around the clock, in the region picked with it (Oregon if none). A size picked on a plan below its around-the-clock price starts with a 2-hour idle pause, which you can change on its page.
| Change | Effect |
|---|---|
| Upgrade | Starts a fresh cycle today: a full month of the new plan, minus the unused share of the old one, bills now and lands as credit. Your renewal date resets. |
| Downgrade | Changes what the next cycle bills, on your existing renewal date; this cycle's credit stays yours. |
| Cancel | Stops the plan at the period's end; credit already landed works until spent. Pick a plan again before then and it keeps renewing. The cancel step asks what made you cancel; answering is optional. |
Before your first plan, with one box, each plan on the Billing page and the payment step says what it buys that box: around the clock, or how many hours a day it can be awake. If a plan won't keep the box running all month, the page says so before Checkout and, where it would make the plan enough, offers a 2-hour idle pause.
Past $1,000/mo the ladder grows one more rung, sized to your boxes. The balance and plan belong to the workspace: everyone spends the same balance and can see the Billing page; only the owner changes the plan, buys top-ups, switches overage, or opens the Stripe portal.
Topping up
The owner can buy one-time top-ups on the Billing page: $10 to $250 by card, as often as needed, in your balance right away and never changing what the plan bills. With overage on, you need none. On the free credit, a top-up leaves the box limits in place; only a plan lifts them.
A spent free credit needs no plan. The plan picker it opens on also offers a one-time top-up of $10, $25 or $50, by card. Your box starts again on its own once the top-up lands, whether the empty balance paused it or it was already asleep. The free credit's box limits stay until you choose a plan, and a top-up leaves each box's auto-pause as it is (2 hours unless you changed it) and ends the free credit's 12-hour limit: a box you set to off, or to a longer window, then runs as you set it.
When we tell you
- Dashboard banner when less than two days of credit remain at the current rate, and on the free credit from a quarter of it spent; others in overage, after boxes were suspended, while a renewal is being collected or a payment is failing, and before the account is funded.
prized statusprints a credit line when the balance is running low or empty, and says whether boxes keep running (overage, a renewal collecting, or a failed renewal's grace). On the free credit, and when the balance has stopped boxes, it prints the link to the Billing page.- Reaching for a paused box says why when the balance is what stopped it:
prized ssh,prized up, plainssh <box>, an editor's remote session and sync print which credit ran out, that nothing was deleted, and the way back with its link, instead of a connection error. On the free credit that is a $10 top-up or a plan, on prized.dev/keep. - Any other
prizedcommand in a terminal, once a day while the balance keeps a box paused, ends with one line saying so, that nothing was deleted, and the link. On a spent free credit it says $10 starts the box again, no plan needed.--json,--quietand scripts never get it. - Email to the workspace's address and every owner, at a quarter and a tenth of what the last cycle left you, and once each on crossing into overage, on boxes pausing, and on a failed payment; at most two reminders if you never started a plan. A deal ending, and the month after it, send none of these, and pay as you go sends no overage email.
- Email when a free credit limit turns a request down. When a request through the API or the CLI is turned down at a limit a plan or a top-up lifts (a second box, a size past Small, a GPU box, the sandbox free tier), the workspace's address and every owner may get one email a few hours later that names the limit and links to Billing. At most one a day and two a week per workspace, and none once the workspace has paid.
- On the free credit with one box, the banner and these emails name the box and the plan that keeps it, and they and the sidebar's Upgrade link prized.dev/keep, which starts checkout for that plan in one click. Once the credit is spent it also offers the one-time top-up.
- When the free credit's idle pause puts a box to sleep (the 2-hour default, or the 12-hour limit on a box you had set to off), its page, the browser terminal while the box wakes, and
prized ssh, plainssh <box>or any other command that wakes it in a terminal say how much credit is left and which plan keeps it awake, with a link to prized.dev/keep. A pause you made, or an idle window you chose, gets no such line. - Which plan. A plan turns off the free credit's 2-hour idle pause, so we name the plan that runs the box around the clock (a Small's is $100). If its busiest week in the last 4 weeks fits a cheaper plan with the pause, we name that too, and choosing it on /keep sets the pause. A box with an idle pause you chose keeps it on a plan and gets the cheapest plan its busiest week needs. Quotes assume at least 2 hours of use a day. Until a box has 2 full days of history at its current size, not counting its first day, that is the whole quote, so a new Small is offered $100 around the clock or $50 with the pause.
Overage
Off by default: out of credit means boxes pause, and nothing bills past what you put in. The owner can switch it on from the Billing page, and running out then stops nothing:
| Case | What happens |
|---|---|
| Usage past zero | Bills at the same hourly rates, as its own line on your next invoice, no markup. Prepaid credit always spends first; new credit (a top-up, an upgrade, the next cycle) pays overage down first. |
| You turn it off | The balance is the hard stop again; overage already run up still bills with your next invoice, or a final one if the plan ends first. |
| A failed or disputed payment | Switches overage off until a payment collects. A failed renewal still keeps boxes running for seven days (Failed payments). |
| A cancelled plan | Its negative balance bills once, on a final invoice; a tail under Stripe's 50 cent minimum is written off. |
| A refund, a reversed payment, or a correction | Never charged as overage, even if it makes the balance negative: only metered compute bills as overage. |
| A dispute of the payment that settled your overage | Puts the balance, and the overage owed on it, back where they were. |
Running out
With overage off, without a plan, or while a payment is failing past its grace, the balance is the hard stop: at zero, boxes suspend. Disks are kept, with your work, installed tools, and git state. Boxes the stop paused start again on their own once the next cycle, an upgrade, a top-up, or overage can run them for four hours; a box you woke, paused, or deleted since is left as you left it, except the one box a spent free credit's top-up or first plan starts (Free credit). Suspended boxes meter their disk at the sleep rate, and usage the balance cannot cover is written off, never turned into a debt. Until then, anything that tries to reach a box the balance stopped is told so, with the link to pick a plan or add credit (When we tell you).
Renewal day is not running out. A renewal takes about an hour to collect, so a plan that reaches zero after it renews pauses nothing until the payment goes through, for up to six hours, and that time bills from the new cycle's credit. If the payment fails, the seven-day grace under Failed payments takes over; if the six hours end with neither, your boxes pause. Usage recorded during the wait keeps its running rate and is paid from your next credit, not charged as overage. An unpaid upgrade does not extend this renewal window or delay suspension at zero.
If a box stays paused after funds return, resume it yourself. A pause whose intent is uncertain is never undone automatically.
Starting and resizing boxes
With overage off, a create, a wake, or a resize needs enough balance to run the resulting fleet for four hours, counting every box at the disk it actually has; while a renewal collects or a failed renewal is in its grace, a box from the fleet already running when collection began can be woken without that balance unless failed-launch cleanup is still reserving allowance. Waking a previously parked box with credit and pausing it again does not add it to that protected fleet. A box paused before its first start still needs normal funding.
An infinite storage box counts with the space it uses beyond its size's disk, including when it wakes or is resized. Restoring a deleted one counts the space the deleted box last used.
It is a check, not a charge: a refusal says what the fleet would burn and what the balance would need. A resize meters at the new rate at once; a box mid-change cannot be resized until it settles.
A failed launch still reserves its allowance until its cleanup finishes, even if you delete it. That reservation is not billed, but it still counts against box limits and member policy limits. A failed box cannot be resized. While it is pending and overage is off, even a wake during renewal collection or payment grace needs the full four hours of fleet allowance; add credit or wait for cleanup.
A region move keeps the hourly rate but copies the whole disk, so it needs a funded balance (Regions). Its caps, and every other, are on Limits.
When a new or resized box would cost more around the clock than your plan puts in each month, the owner is offered the covering plan (with no plan yet, a first one). Resize offers it as one extra click, quoting the charge due today, and declining just resizes; Create pre-selects it, and unchecking creates on your current plan. Nothing charges without the page saying so first, and the prepaid balance is the only thing that gates a box.
Failed payments
A failed renewal of a plan that has paid before keeps your boxes running for seven days from the first failure, whatever the balance reads; the banner, the Billing page, prized status, and the email name the minute it ends. Overage is off meanwhile, so nothing more goes past zero: the time the boxes run waits, at the rate it ran, for the payment to cover. A box that was running at renewal can be woken again after a pause; a box already asleep before renewal, new boxes, and resizes need enough credit. These wakes still need the failed-launch cleanup allowance.
Stripe retries the card on its own schedule; the owner updates it in the Stripe portal, linked from the Billing page, and the charge retries on its own. Paid, nothing changes; still unpaid after seven days, or the plan cancelled, the balance is the hard stop again and boxes pause at zero.
Any other failed payment (an upgrade's charge, or a plan's first) suspends nothing by itself: boxes keep running on what remains, and pause at zero.
Fully refunded or reversed plan payments do not qualify for renewal grace. A refund of your last qualifying plan payment ends that grace.
A refund, or a payment your card issuer pulls back (a dispute), takes the credit it bought out of the balance; a dispute also pauses the plan's billing and switches overage off while it stands. Won, the credit is restored, billing resumes, and overage returns with your next successful payment; lost, the plan is cancelled and overage stays off until you pick a plan again.
Receipts
Every cycle produces a Stripe invoice you can download. The Billing page's recent activity lists each cycle's credit and one usage line per hour; card details, invoices, and receipts are in the Stripe portal, linked there for the owner.
Custom plans
A fleet bigger than the largest rung needs no special deal: the plan sizes itself to your boxes (above). For a startup deal or a negotiated amount, email for a link (it expires after 30 days) the owner opens to subscribe at that amount in one click, or to move an existing plan; it then behaves like any other plan. A custom plan also unlocks zero data retention.