Cost
An installation has two kinds of cost: a small one that runs all the time, and runners, which
run while workspaces do and for a while after (runner_idle_minutes). Once its runner is given back,
a stopped workspace costs what it keeps in the bucket.
Prices depend on the region and change; every price here says where and when it was read, and
the AWS Pricing Calculator has yours.
Three months, priced
Section titled “Three months, priced”The module’s default machines, on demand, in the regions Spin OS has images in. The machines are at the prices the AWS pricing page listed on 2026-11-14 (the record was written on 2026-11-16, and the daily sync rewrites it); disks, addresses, keys and zones at AWS’s price lists of 2026-11-19:
| Scenario | What runs | us-east-1 $ a month | us-west-2 $ a month |
|---|---|---|---|
| Nothing running | The control plane (t8i.medium) and the proxy (t8i.micro) all month, their 60 GB of gp3, their two public IPv4 addresses, three KMS keys and two Route 53 zones. No runner is up, and the buckets and logs are left out. | $62 | $62 |
| One runner, working hours | The above, and one c8id.8xlarge up 176 hours: eight a day, twenty-two days, on demand. | $374 | $374 |
| One runner around the clock | The above with the runner up all month, on demand: the most the default installation can spend on runners. | $1,357 | $1,357 |
These are list-price estimates. Runners are spot by default, so a runner usually costs less than the on-demand hour these use (Spot). Not in the table: what the buckets hold, the logs, and what leaves the region, at EC2’s price per GB; they depend on what your workspaces do.
With nobody working
Section titled “With nobody working”| What | Default | List price, us-east-1 and us-west-2 (2026-11-19) |
|---|---|---|
| Control plane | One machine, instance_type, which also runs the database | In the table above |
| Proxy | One machine, proxy_instance_type | In the table above |
| Their disks | gp3: the control plane’s root_volume_gb and the proxy’s 20 GB | $0.08 per GB a month |
| Public IPv4 addresses | Two: the control plane’s, and the proxy’s elastic IP | $0.005 an hour each |
| KMS keys | Three: the installation’s encryption, identity and volume keys | $1 a month per key version |
| Route 53 | Two hosted zones | $0.50 a month each |
| S3 | What the volumes, the database’s archive, logs, documents and certificates hold | S3 Standard, $0.023 per GB a month |
| CloudWatch | The flow log and the machines’ boot logs, 30 days | Cents a month at a few hosts |
There is no NAT gateway, no load balancer and no interface endpoint: every machine has its own public address, and the bucket is reached through a gateway endpoint, which is free.
At list price that is the table’s first row, before the buckets and the logs. The one measurement so far is higher: on a day the module’s own install test left an installation standing in us-east-1, the region’s bill was $2.34 (2026-11-01), about $70 over a month. That day’s bill may include the test itself, and it was not broken down: one data point, not a figure for your installation. Your own is on the Costs page, as the standby.
While workspaces run
Section titled “While workspaces run”Runners are the largest cost, and they cost only while they are up. By default a runner is a
spot machine with local NVMe, of 32 to 48 vCPUs: a c8id, m8id or r8id 8xlarge or 12xlarge
(runner_instance_types,
runner_vcpus). Each also has a public IPv4 address
and a gp3 root disk.
The control plane sizes the runners’ group:
- It starts the first runner when a workspace waits for one, and adds another only when a
workspace has waited longer than a runner takes to start, up to
max_runners. - When no workspace has run, started or waited for
runner_idle_minutes, it empties the group, and at once duringquiet_hours. - While workspaces run on other runners, it gives back a runner that has held nothing only it has for as long, one at a time.
Runners and hosts has the details. A workspace nobody uses is suspended, and so is one that runs past the installation’s limit, so a forgotten workspace does not keep a runner up all night (Workspaces).
How many workspaces fit on one runner is not measured yet. A workspace’s share of a runner is what it held, not what it used: the control plane divides the runners’ cost by the cores and memory each workspace held while it ran (The bill). Runner capacity nobody held is shown apart, as idle.
AWS prices spot by zone and hour. Over the 30 days to 2026-11-19, the default runner types were at these prices an hour, against the on-demand list:
| Type | On demand | Spot, us-east-1: median (low to high) | Spot, us-west-2: median (low to high) |
|---|---|---|---|
| c8id.8xlarge | $1.77 | $0.53 ($0.34 to $1.06) | $0.61 ($0.47 to $0.89) |
| c8id.12xlarge | $2.66 | $0.78 ($0.52 to $1.11) | $0.79 ($0.67 to $1.20) |
| m8id.8xlarge | $2.09 | $0.72 ($0.47 to $1.32) | $0.75 ($0.62 to $1.05) |
| r8id.8xlarge | $2.66 | $1.00 ($0.67 to $2.13) | $1.02 ($0.77 to $1.43) |
The group asks for all six types the defaults match (the four above, and m8id and r8id 12xlarge), with the price-capacity-optimized strategy, in every
zone the installation has a subnet in (up to
availability_zones), and with Capacity
Rebalancing on; a runner it takes away is held for
drain_seconds while it empties. On 2026-11-19,
AWS’s spot placement score for those six types together was 9 of 10 for one runner in both
regions, and in 5 of the 9 zones asked one zone at a time. For more runners it held in us-west-2
(9 at 10 and at 20 runners) and fell in us-east-1 (5 at 10, 2 at 20). AWS gives a low score to
any request that names fewer than three types, so ask for the set. Scores change from day to day,
and they say how likely AWS is to start spot capacity, not how long it keeps it.
aws ec2 describe-spot-price-history --region us-east-1 --product-descriptions Linux/UNIX \ --instance-types c8id.8xlarge c8id.12xlarge --start-time 2026-10-20T00:00:00Zaws ec2 get-spot-placement-scores --region us-east-1 --region-names us-east-1 --target-capacity 1 \ --instance-types c8id.8xlarge c8id.12xlarge m8id.8xlarge m8id.12xlarge r8id.8xlarge r8id.12xlargeWhen AWS has no spot capacity, the group keeps asking for it. A host class can be set to fall back instead: the control plane starts the group’s new runners on demand for 30 minutes, then asks for spot again; runners already started on demand stay until they are given back. It is off for the default class and on only where a class turns it on (Admin → Runners), and each switch is in the audit log.
A runner AWS reclaims suspends its workspaces to the bucket within the notice AWS gives, and they resume on another runner (When a runner goes away). Whether a full runner’s memory fits in that notice is not measured yet.
A stopped workspace
Section titled “A stopped workspace”Once its runner is gone, a stopped or suspended workspace costs only what it keeps in the volumes bucket, at S3 Standard’s price: $0.023 per GB a month for the first 50 TB, in us-east-1 and us-west-2 (2026-11-18). A suspended one also keeps its memory checkpoint there, at most its whole RAM. Clones share their image’s layers, so a hundred workspaces from one image store the image once. Its owner sees what keeping it stopped costs a month, on its page.
The bucket keeps every object under Object Lock for
object_lock_days and removes it the day
after. So a deleted workspace is paid for twice over: in the trash, a week by default, with its
disk; then, once it is erased, its bytes, checkpoints included, for about 31 days more by
default.
Reading the bill
Section titled “Reading the bill”The control plane reads the installation’s own bill: the month’s costs from Cost Explorer, its
forecast, and its budget if it has one, every six hours.
A day’s cost settles a day or two after it ends. spin admin costs shows it, starting with the
standby: the installation’s daily cost with nobody working, from the last billed day.
spin admin costsspin admin costs by workspaceThe dashboard’s Costs page (Admin) shows the same, and each workspace’s owner sees its cost and its rate. Jobs, the bill and the store explains how the month is shared out.
The bill is read by the installation’s tags, and AWS shows a tag in the bill only once it is a
cost allocation tag. That is the account’s to switch on, once, and AWS refuses to before it has
seen the tag on a resource: after the installation has run for a day, apply bootstrap with
cost_allocation_tags = true, in one bootstrap per account. Until then the Costs page is empty.
monthly_budget_usd makes an AWS Budget over everything the installation tags, and mails
budget_emails at 80% and 100% of what it cost and at 100% of the forecast. Nothing is stopped
when it is passed.
Settings that change the cost
Section titled “Settings that change the cost”| Setting | Effect |
|---|---|
runner_idle_minutes | How long runners stay up once nothing runs, and how long a spare one is kept |
quiet_hours, time_zone | A window, such as nights, when runners go as soon as nothing runs |
max_runners | The most runners at once |
runner_spot = false | On-demand runners: more expensive, never reclaimed |
runner_instance_types, runner_vcpus | Smaller or larger runners |
instance_type, proxy_instance_type | The size of the control plane and the proxy |
flow_logs, log_retention_days | What is kept in CloudWatch. Variables of the control plane’s module, which the root module leaves at their defaults. |
monthly_budget_usd | A budget and its alerts; it stops nothing |
Installations run Spinbox v20261027.01; the reference is generated from spin v20261114.01 (51f7e0dea). This page as Markdown, for a model or a terminal.

