Plans, billing and usage
What each plan includes, what is free during early access, how to pay, and how to read your metered usage.
Check your usage
sailfork usage
sailfork usage --org acme --month 2026-10 month: 2026-11
changes: 12500 (10000 free, 2500 billable)
estimate: 5.00 USD at 2.00 per 1000 changes
compute: 0.500 unit-hours (900 s) at 0.012 per unit-hour
compute est: 0.01 USD The numbers above are an example of the format. --month takes YYYY-MM and defaults to the current UTC month. --org shows an organization's usage and is for its owners.
Early access is free
Every plan is free during early access. Before billing starts, every account gets 30 days of notice by email, with the date and what its plan will cost. Each person and every owner of an organization gets the email. Nothing asks for payment until then, and you do not need a card to start.
The prices below describe what starts after that notice. See /pricing for the current list.
Plans
Plans differ only in storage. Every feature is in every plan.
| Plan | Price | Storage included | Past that |
|---|---|---|---|
| Free | $0 | 5 GiB | No extra storage. Pushes are refused at the limit. |
| Pro | $12 a month | 50 GiB | $0.10 for each extra GiB a month |
| Max | $40 a month | 250 GiB | $0.10 for each extra GiB a month |
| Team | $20 a seat a month | 25 GiB per seat, pooled across the organization | $0.10 for each extra GiB a month |
Free, Pro and Max are for a person. Free and Team are for an organization. Here 1 GiB is 1,073,741,824 bytes. A partial GiB is prorated and rounded up to the cent.
What counts as storage
The packed git data and Git LFS objects of every repository you own, measured from object storage after compression. For an organization, it also counts releases, pooled across every seat. Reading and cloning code is free.
What happens at the limit
Nothing is ever deleted for you. On Pro, Max and Team, going over costs $0.10 a GiB. A Free account has no extra storage: once billing starts, a push that would take it past 5 GiB is refused until you delete something or change plans. The refusal reads:
This account stores 5.2 GiB and the Free plan includes 5 GiB. Pushes and commits that add data are refused until you free space by deleting repositories or move to a paid plan under Settings, Billing. Reading, cloning and deleting still work. The sizes in that message are an example.
Seats on Team
Every owner and member of an organization takes a seat. Seats are counted when the billing cycle ends. An invitation takes a seat only once someone accepts it, and an expired one takes none. Each seat adds 25 GiB to the pool. See Organizations.
Choose a plan
For yourself, open Settings, Plan and usage. It has Storage, Plan, and Receipts. Pick Free, Pro or Max.
For an organization, an owner opens the organization's Settings, Plan and seats. It has Plan, Seats, Storage, Bills and receipts and Past bills. Pick Free or Team.
Changes apply now. Moving down takes effect at the end of the cycle, so nothing you paid for is lost. The button says what will happen: Switch to a plan, Move to a plan at the end of the cycle, or Keep your plan.
Pay
Moving to a paid plan goes through Stripe checkout. Choose Continue to checkout, enter a billing name and country, and agree to automatic renewal. Card details go straight to Stripe and never reach Sailfork. A paid plan renews every month until you cancel.
To change the card or bank account, open Settings, Plan and usage and choose Manage billing, then add the new one and make it the default. The old one stays until you remove it. Choose Cancel renewal to stop a plan from renewing. If a payment fails, the page says The last payment failed and asks you to update the payment method under Manage billing.
You can pay with a card or a bank account. Enterprise plans can pay by invoice with net terms. Tell us your billing contact through the contact page and we set it up.
Upgrading while subscribed charges the difference for the current cycle to your saved payment method.
Receipts and past bills
Under Receipts, choose which of your verified email addresses receives receipts. Only verified addresses can. For an organization, Bills and receipts picks the addresses that get invoices. Past bills lists one bill per cycle, issued the day after the cycle ends. Open one for its line items, who was billed and how it was paid.
Metered usage
Agents that write through caissons are metered. One change is one file an agent writes, edits or deletes through a caisson. Pushes over git and reads are not counted.
| Meter | Free allowance | Past the allowance |
|---|---|---|
| Agent changes | 10,000 a month | $2.00 per 1,000 changes |
The allowance resets each month, on the UTC calendar. A partial thousand is prorated and rounded up to the cent.
The changes belong to the repository's billing account: its organization, or else its owner. sailfork usage prints the month, the changes with how many are free and billable, and the estimate. Add --json for the same fields as JSON.
Once billing starts, a Free account that has used its changes is refused further agent writes until the month ends or it moves to a paid plan. The refusal reads:
This account is on the Free plan, which allows 10000 agent changes a month, and it has used 10001. Agent writes are refused until the month ends (UTC) or you move to a paid plan under Settings, Billing. Reading, cloning and deleting still work. Who pays for CI and sandbox compute
You choose. There are three places to run:
- Sailfork hosted. Your jobs and sandboxes run on Sailfork's own machines and you pay by the second. Turn it on under Settings, CI.
- Depot. An organization connects its own Depot account and pays Depot. Sailfork charges nothing for it.
- Your own Drydock hosts. Machines you register run CI and sandboxes. Sailfork charges nothing for them.
CI uses hosted compute when it is on, then Depot, then your own hosts. Sandboxes run on your own hosts, and on Sailfork's when hosted compute is on. An account with none of the three gets no runs. See CI and Sandboxes.
All three need an account with a verified email address.
Hosted compute
| Meter | Free allowance | Price |
|---|---|---|
| Hosted compute | None | $0.012 per unit-hour |
One unit is 1 vCPU with 2 GiB of memory. A job or sandbox counts its vCPUs or its memory in 2 GiB steps, whichever is more, rounded up to an even number, because no two tenants share a core. A 2 vCPU job with 4 GiB is 2 units. A 4 vCPU job with 8 GiB is 4 units. A 1 vCPU job with 5 GiB is 3 memory steps, so 4 units.
It is billed per second, from the start of the sandbox to its stop. There is no start fee and no egress fee. A run that is moved back to the queue before it finishes is not billed for the time it lost. A 4 vCPU job with 8 GiB that runs 10 minutes is 4 units for one sixth of an hour: 4 × 1/6 × $0.012 = $0.008.
The compute that stopped since the last bill is added to the renewal invoice as one line, Hosted compute, rounded up to the cent. sailfork usage shows the month so far.
Hosted compute needs a paid plan with an active subscription, once billing starts. Until then it cannot be turned on. A Free account that tries it is refused with a message that names its plan:
Hosted compute needs a paid plan. acme is on Free; move to Team under Settings, Billing. Two caps keep a mistake cheap. Both are under Settings, CI, and an owner can change them.
| Cap | Default |
|---|---|
| Running vCPUs on hosted compute | 64, from 1 to 256 |
| Spend in a UTC month | None |
Work past either cap waits in the queue, and its status names the cap. A running sandbox is never stopped for a cap. The spend cap counts compute that has stopped, so it can be passed by the runs in flight.
Turning hosted compute off sends later jobs to Depot or your own hosts. Running sandboxes carry on. Code from outside contributors never runs on Sailfork's shared hosts, whether or not hosted compute is on. Sailfork can suspend an account on hosted compute, which stops its running sandboxes there at once.