Pricing
| Meter | Price | Unit |
|---|---|---|
| CPU | $0.0288 | per vCPU-hour of CPU time used |
| Memory | $0.0108 | per GiB-hour of memory in use |
| Disk | $0.101 | per GiB-month stored |
| Egress | $0 | measured, and free |
Memory the host caches for the machine is free. Identical disk bytes are stored once across all your machines.
An idle machine costs about 14¢ a day. A stopped machine pays only for its disk. A removed machine pays nothing.
| Machine | What the meter reads | Per day | Per 30 days |
|---|---|---|---|
| Idle | 1% of a vCPU busy, 0.5 GiB of memory in use, 1 GiB of disk | 14¢ | $4.20 |
| Busy all day | 2 vCPUs busy, 8 GiB of memory in use, 20 GiB of disk | $3.52 | $105.70 |
| Stopped | no CPU, no memory, 20 GiB of disk kept | 6.8¢ | $2.03 |
Plans
Without a plan you pay as you go: add funds and pay for use at the list prices above. A plan is a monthly charge that comes back as a usage allowance at a multiple of its price, shown below. The allowance pays for CPU and memory at the rates above, so a plan is a prepaid bundle and never a discount on the meters. Included disk draws its own pool.
| Plan | Price | Allowance multiple | CPU and memory allowance | Included disk | Machines at once |
|---|---|---|---|---|---|
| Dev | $20.00 a month | 2x | $40.00 of usage | 20 GiB | 20 |
| Pro | $200.00 a month | 2x | $400.00 of usage | 200 GiB | 50 |
| Max | $500.00 a month | 2x | $1000.00 of usage | 500 GiB | 100 |
Credits never expire: what you add stays until you spend it. The unused part of a monthly allowance does not roll over. Overage is off by default; when you turn it on, spending above the allowance draws your credit balance up to a monthly cap of $100.00 unless you set another. There is no free credit on signup.
When funds run out
Running machines stop at once, with no grace period, and new starts are refused until you add funds. Disks and snapshots are kept for 24 hours. Storage used in that window is a debt that your next top-up pays first; machines start again once it is clear. After the window, data is deleted.
| Thing | What happens |
|---|---|
| Running machine | Stopped through the normal graceful path. If the guest does not flush, it is forced off and you are told unflushed writes are lost. |
| Open exec stream | Ends with the machine stopping. |
| Disk | Kept for 24 hours, then deleted. Use in that window is debt. |
| Snapshot | Same rule as disks. |
| Public ports | Closed with the machine. The hostname returns on restart. |
| New start, schedule or CI run | Refused with the amount owed. |
| Top-up | Pays the debt first, then funds. Nothing already deleted comes back. |
You are told at 80, 95, 100 percent of your funds used, and when the grace starts, nears its end and ends. The events are `billing.funds_low`, `billing.funds_exhausted`, `billing.grace_expiring`, `billing.grace_expired`, `billing.debt_cleared`.
Spending ceilings
A key with a ceiling stops spending at that number.
# This key stops spending at $100.
ix keys create customer-42 --limit 100
ix billing status
ix billing usageDo snapshots cost extra?
A snapshot bills as disk, for the bytes it does not share with your other machines.
Do I need a plan?
No. Add funds to a balance that can recharge itself, and start.