Docs · Get started

Pricing

Sandboxes are billed by the month, not by the second. You choose your setup: how many sandboxes of each size, with shared or dedicated vCPUs. Each runs 24/7 at no extra charge. There are no plans, no minimum and no per-second usage for sandboxes.

SizevCPU · memory · diskShared vCPUs, a monthDedicated vCPUs, a month
lite1 · 2 GB · 51 GBfree: one per account with a card, interruptible—
small2 · 4 GB · 51 GB$3$10
default4 · 8 GB · 51 GB$5$20
large8 · 16 GB · 111 GB$10$40

Shared vCPUs are time on the host's cores, shared with other sandboxes; most agents idle most of the time, so they rarely wait. Dedicated vCPUs are physical cores no other sandbox runs on. Memory is reserved for every sandbox either way.

Your setup

Invite-only for now. Paid sandboxes open account by account. Join the waitlist with the setup you'd run and what it's for: froog billing request default=3 --note "CI for a monorepo", the dashboard's Billing page, or POST /v1/billing/capacity/request {"slots": [...], "note": "..."}. We read every request and email you when you're in. Until then, adding to a setup or starting a paid sandbox answers 403 capacity_waitlist, and GET /v1/billing shows capacity.waitlist (when you asked, and what). The free lite is open to everyone with a card.

froog billing capacity default=3 large:dedicated=1 sets the whole setup (sizes left out are 0; none removes it), and froog billing capacity shows it. In the dashboard it's the table on the Billing page; in the API, PUT /v1/billing/capacity {"slots": [{"size": "default", "count": 3}, {"size": "large", "cpu": "dedicated", "count": 1}]}. GET /v1/billing returns it as capacity.

  • Adding applies at once: the rest of this calendar month (UTC) is charged right away, prorated. A declined card leaves the setup as it was.
  • Removing applies from the next month, since this one is paid; capacity.pending shows it. Setting the old setup again takes the removal back.
  • Each month the card is charged for the whole setup at its start. Credit already in the wallet is used first. If the charge doesn't go through, the setup is unpaid at once (capacity.unpaid, with capacity.owed_usd): you get an email, its sandboxes can't start (402 capacity_unpaid) and running ones stop (disks saved). The free lite keeps running. It's tried again every hour, and at once when you add a card (a card just added becomes the default) or choose another default. If your bank asks you to confirm each payment (3D Secure every time), froog can't charge the card on its own: pay on a Stripe page with Pay now on the dashboard's Billing page or POST /v1/billing/capacity/pay (it goes to the wallet, and the setup is paid). Adding to a setup with such a card answers 402 authentication_required with a link to pay that way.
  • Running more of a kind than the setup holds fails with 402 capacity_full, which says what to add. When a month starts with fewer slots than are running, the newest extra sandboxes stop.
  • froog new without --size picks default if one is free in the setup, else another size with a free slot, else the free lite.
  • The fleet's room caps how much one account can add: every setup must fit on the hosts one by one, dedicated vCPUs included (409 no_capacity says how much is left); email hello@froog.tech for more.
  • Changes to a setup are made one at a time per account: a second request at the same moment (a double click) waits for the first and is charged only for what it adds then.

The free lite

With a card on file, an account runs one lite sandbox (1 vCPU, 2 GB) free, alongside its setup. It's interruptible: when froog is full and a sandbox of someone's setup needs the room, the lite that has run longest is stopped, its disk saved, and its owner emailed. Start it again later with froog start NAME. A second lite fails with 429. We can also stop it at any time, for any reason, and change or end the offer; removing the card stops it.

Card

froog billing card (or Add a new card on the dashboard's Billing → Add funds page, or POST /v1/billing/card) opens Stripe Checkout in your browser: froog never sees your card number, and your bank may ask you to confirm the card (3D Secure). Adding a card charges nothing. You can save more than one. The default is the one the monthly charge and auto top-up use: a card you just added becomes it, as does one you pay with; choose another with Make default on the Add funds page or PUT /v1/billing/cards/{id}/default. While your setup is billed, your only card can't be removed (409 card_needed): add another first. Stripe emails a receipt for every card payment, and the Billing page lists your payments and charges (GET /v1/billing/history).

Wallet (Pushbox)

The wallet is a prepaid balance in US dollars for what's billed by use: Pushbox CI job time ($0.0006 per vCPU per minute, per second), 120 fps desktops ($0.05 an hour while watched, per minute) and saved snapshots past those included. froog wallet pay 20 adds $20, charged to your saved card (whole dollars, $5 to $10,000; at most $10,000 a day per account). Starting a CI runner needs an hour of its job time in the wallet (402 insufficient_balance), and when the wallet runs out, running CI runners stop.

Auto top-up. In the dashboard you turn it on in its own form (a payment there is one-time). From the CLI and API, your first wallet payment turns it on at the same amount: whenever the wallet drops below half of it ($3 at least), your card is charged that amount again. froog wallet auto 50 changes it, froog wallet auto off turns it off, and froog wallet pay 20 --no-auto pays without touching it. A declined charge turns auto top-up off and emails you.

Bonus. A payment of $200 or more gets 2% extra, growing to 25% at $10,000 (froog wallet quote 500 shows it).

Spending cap

froog billing cap 50 sets the most the wallet may spend in a calendar month (UTC), froog billing cap off removes it (API: PUT /v1/billing/spend-cap {"usd": 50}). Every account starts with a cap of $10,000 a month. You get an email at 80%. At the cap, CI runners stop and new ones wait (402 spend_cap_reached) until next month or a higher cap. Your setup isn't affected.

Storage

  • Stopped sandboxes keep their disk for 14 days, free. Automatic snapshots are free. Every account includes 10 saved snapshots; each one past those is $1.50 a month, charged daily from the wallet. With an empty wallet, saving one more under a new name fails with 402 credit_required.
  • Network traffic (no egress charges), public URLs, the desktop and /dev/kvm are included.
  • froog billing shows your setup, the wallet and this month's usage; froog usage breaks down this month's Pushbox and snapshot usage (--month 2026-10 for a past one).

Limits

An account runs its setup and the free lite. Starts: up to 20 a minute, 100 an hour and 500 a day (5, 25 and 75 before the first payment), and at least as many a minute as the setup holds, so a whole burst starts in one go. CI runners: 3 at once before the first payment, 10 after. froog limits shows your limits and how much of each you've used.