Pricing and limits

Plans

Prices are in US dollars per month. Allowances reset with each billing period: your subscription's period on a paid plan, the calendar month (UTC) on Free.

Free has no guaranteed CPU or RAM hours: it runs on capacity as available. Its usage is measured and shown, but not capped.

Retained state is sized for one workspace per customer, with suspended workspaces kept for as long as you want them. The workspace counts assume 2 GiB each, which is generous for most work: on the default template with 2 GiB of memory, a new workspace keeps under 0.1 GiB, one with a cloned Node.js repository and its dependencies about 0.2 GiB, and one with a Python environment, 40 MB of data and a report about 0.4 GiB. A checkpoint also holds the memory the workspace has used, so one that has filled its memory can keep close to its memory size on top of its disk.

The workspace counts are a storage estimate, not a limit: there is no cap on how many workspaces you create or keep, and suspended workspaces do not count toward running workspaces at once.

Enterprise: contact shardflux@heliosone.fi.

There is no automatic overage. Reaching an allowance adds charges only after you turn on overage with a spend cap. Upgrade, change or cancel a plan under Usage & billing in the console, or from a terminal with the CLI (0.5.0+): shard billing upgrade <plan> prints the Stripe Checkout URL where a person pays, and shard billing portal prints the link for plan changes and cancellation (Billing).

What each allowance measures

Shared volume storage is measured and shown separately; no allowance includes it and it never blocks anything.

shard usage, cloud.usage (TypeScript) and Usage in the console show what you have used, with the time the numbers were measured through.

What happens at a limit

Every owner and billing member gets an email at 80 % and 100 % of an allowance. With overage on, they also get one at 50 %, 80 % and 100 % of the spend cap. Compute limits are enforced with short budget leases, so usage can run slightly past an allowance or the spend cap before running workspaces are suspended; the organization's spend view reports that bound.

Billing states. If a payment fails, you have 7 days of grace. Nothing changes during it, except that overage is paused until the invoice is paid. After that, new opens, resumes and forks are refused with 402 entitlement_required (details.reason: payment_past_due or unpaid); running workspaces and your data are untouched. A cancellation takes effect at the end of the period, after which Free limits apply to new starts.

Data is never deleted by billing or inactivity. Workspaces are deleted only when you delete them, with one exception: a session workspace is deleted when its session ends.

Overage (opt-in)

Overage keeps your workspaces opening and running past the CPU-hours and RAM GiB-hours allowances, up to a spend cap you set. It is off by default. Free has no overage.

Turning it on. An owner or billing member turns overage on under Usage & billing in the console and sets a spend cap in dollars per billing period. The cap is at least $1 and at most the plan price: $9 on Developer, $79 on Startup, $299 on Scale. A period's bill is therefore at most twice the plan price. The cap never exceeds the current plan's price, so moving to a cheaper plan lowers it.

Rates. They are the same on every paid plan.

Storage and outbound transfer have no overage. Retained state and shared volumes are never charged, and outbound traffic is still blocked at 100 % of the transfer allowance.

Billing. Charges come from the same usage measurements as the allowances, counted per UTC hour. They go on your next monthly invoice and are charged to the card that pays the plan. There are no prepaid credits. Upgrading during a period does not refund overage already charged.

At the cap. New opens, resumes and forks are refused with 402 allowance_exhausted (details.reason: spend_cap_reached; see Errors). Running workspaces are suspended, keeping their files, memory and processes. Nothing is deleted. Work can start again when the next billing period begins, when you raise the cap (up to the plan price), or when you upgrade. Usage can run slightly past the cap before workspaces are suspended, but you are never charged more than the cap.

Past-due payments. While a plan payment is past due, overage is paused and the allowances apply as if it were off. Past an allowance, starts are refused with 402 allowance_exhausted (details.reason: overage_paused) and running workspaces are suspended. Overage resumes when the invoice is paid.

Emails. Every owner and billing member gets an email at 50 %, 80 % and 100 % of the cap, and when someone turns overage on or off or changes the cap.

Workspace sizes

A workspace's CPU, memory and disk are the smallest of three maximums: the plan's (above), the template's, and the caps you pass to open (caps: { cpu_millis, memory_mib, disk_gib }; 1,000 cpu_millis is one vCPU). The allocation is fixed while the workspace runs.

• python-node-browser allows up to 4 vCPU, 8 GiB of memory and 20 GiB of disk, and starts workspaces with 2 GiB of memory unless you set caps.memory_mib.
• Disk is the space for the workspace's own changes; the template's files do not count against it.

See Workspace size.

Region

Workspaces and the API run in AWS us-west-2 (Oregon, United States). The API is https://api.shardflux.dev and the console https://app.shardflux.dev.

Starts and waits

API rate limits

Over a limit, the API answers 429 rate_limited with a Retry-After header. The SDKs retry 429 for safe and idempotent requests (maxRetries / max_retries, default 2), then raise the error with retryAfterSeconds (TypeScript) or retry_after (Python).

File and command limits

Search, patches and revisions

See Search and edit files.

File-first workspaces

See File-first workspaces.