Skip to main content
Every machine comes with the same specs, every account starts with the same quotas, and an idle machine winds itself down to almost nothing. Every limit on this page can be raised. Please let us know if you need more and/or smaller/bigger machines. We generally approve requests the same day. Send an email to contact@boxd.sh.

​
What every machine gets

Disks are copy-on-write, so storage only grows as you actually write data. A fresh fork takes near-zero extra disk until it starts diverging from its parent.

​
Account limits

A new org without a payment method starts capped at 2 machines. Connect a card and it goes to the full 50. Everything counts toward the machine cap, including forks, goldens, and hibernated machines. Destroyed machines don’t. Filling the cap with hibernated workspaces is normal use, since they cost you almost nothing while parked.
Hitting a cap? Email contact@boxd.sh and tell us what you’re running. We generally approve requests the same day.

​
What each state costs

You don’t manage any of this by hand. A machine winds down on its own when traffic stops and wakes when it returns: Auto-suspend is off by default, and auto-hibernate kicks in after 4 hours without network traffic. Your app never notices the transitions. That is why a parked preview, an idle golden, or a long-lived agent workspace can sit around for weeks without burning resources. See Suspend, resume, and hibernate for the mechanics and the tuning knobs.

​
Pricing

See boxd.sh/pricing for the current rate card, and contact us for team pricing.

​
Self-hosted

When you self-host boxd, you set the quotas yourself. boxd-ctl user set-quota overrides the platform defaults per user.