Skip to content
Pricing

Independent verification.
Clear usage costs.

Cruise runs bounded coding work against your approved checks. Today, you pay KeepState for active session time and checkpoint storage; your model provider bills you separately on your own key.

What you're billed for.

KeepState charges for active session time and checkpoint storage. Bring your own provider key and pay model costs directly to your provider, with no KeepState markup. The current usage rates below come from the published price book (v1.3, 2026-09-14); managed inference is planned and not available.

Active session time

$0.011 / min LIVE

Meter details

Charged while a session is running, metered per second and billed per minute. A parked session is charged no active time.

live rate, from the published price book (v1.3, 2026-09-14); more classes are planned · record

Checkpoint storage

$0.09 / GB-month LIVE

Meter details

Charged on the amount actually stored after deduplication. Parked sessions still store checkpoints, so storage is still charged.

19.1x deduplication measured across 82 checkpoints of one soak. One workload; your ratio will differ. · record

Model usage

Your own provider key: 0% KeepState fee PRICE BOOK

Managed inference (4%): planned

BYOK access: self-serve. Managed inference: planned, not available. Check the scope →

Meter details

Use your own provider key (BYOK) and pay your provider directly, with no KeepState markup (0%). Managed inference is planned and not available; its 4% price-book rate is not included in this estimate. Your key never enters a guest, an image or a snapshot.

your key never enters a guest, an image or a snapshot · record

What it costs.

Type a number or move the slider. Everything this produces is an estimate, and it says so, because we have not measured your workload.

min 1 · max 200 · step 1
agents
min 1 · max 24 · step 1
hours per day

Active time only, not calendar lifetime.

min 0 · max 1000 · step 0.1
GB

Enter average billed checkpoint storage. Actual usage depends on the data you keep and the retention rules. A deduplication result from one benchmark is not your expected storage ratio.

Inference

your key (BYOK) · the one path

Continuation: current scope

Scoped cross-provider continuation: enabled in production; self-serve.

Tested on Claude Code 2.1.251 with real tool use, and the deployed production gateway. Harness runs in a chroot of a copy of the recipe image (the firecracker transport is proven elsewhere); streaming is buffered, not incremental (first byte after the upstream completes); replayed thinking blocks are dropped in translation; continuation quality model-dependent

Read the current scope →
How provider routing works

Calls go to your provider on your key: no token meter on this bill, and the key never enters a guest, an image, or a snapshot. Stored-response replay of interrupted calls is proven; routing across providers is roadmap.

Managed inference, where KeepState brokers the tokens, is planned and not available: there is nothing to select, nothing to buy, and no token fee in this estimate. Dated per row on the availability matrix.

optional · min 0 · max 1000000
$ per month

Enter what you expect your provider to charge and the estimator adds it to the combined total. Leave it blank and the KeepState fee still computes on its own.

Worked solo example: 1 agent, 2 hours a day, at the same storage input, is about $40.50 a month in KeepState fees. Your provider bills your model use separately. Same formula at the live rates; the output stays ESTIMATED because your workload is not our example.

estimated KeepState fees, per month

ESTIMATED

Based on your inputs and the displayed rate version. Not a quote or a savings result.

$80.10

120 agent-hours per month

session time $79.20
checkpoint storage $0.90
Estimated KeepState fees $80.10

Collected by KeepState, from prepaid credits. Polar takes the payment as merchant of record and issues the purchase receipt; KeepState issues the usage statement.

Model-provider charges your provider's bill · enter your spend to add it

Collected by your provider, on your own key.

Total estimated cash cost add your model spend to complete this

What you pay in total, to both parties. It is a sum of two bills, not one bill.

currency
USD
rate book
v1.3, published 2026-09-14
rounding
statement level, to the cent. Session time is metered per second and billed per minute, rounded at statement level to the cent.
tax
Taxes are collected and remitted by Polar as merchant of record. KeepState statements show pre-tax charges and say so. The figures above are pre-tax.
All estimator assumptions
  • Estimated KeepState fees = active session time + checkpoint storage. Model-provider charges are what you entered, billed by your provider, and are not a KeepState fee. Total estimated cash cost = the two added together.
  • 30 days modeled, an ESTIMATED scenario and not the billing-month denominator; standard class $0.011/min; storage $0.09/GB-month after dedup; live rates from the published price book
  • storage is the average billed storage YOU enter; the 19.1x dedup ratio is one soak's result and is not assumed of your workload
  • token prices are yours and we assume none; BYOK carries no KeepState markup, and managed inference is planned, so no token fee is modeled
  • no egress charge and no support charge appear in the ratified price book, so the estimator models neither. Managed inference is not purchasable, so no fee or pass-through row is computed.
  • the estimate is a model; the statement KeepState issues after the month is the record
  • this assumption set as a content-hashed artifact

The published production record confirms usage settlement and an interlock event; neither account had a running session. Checkpoint-and-park on a running production session remains unverified by that record.

One agent, 2 hours a day: about $40.50 a month in KeepState fees. Model costs are yours and go to your provider.

How these rates are published and verified

live · published price book v1.3The meter rates on this page render from the published prices file, the same file the control plane bills from; a hand-typed number here fails the release gate. Two documents govern every dollar: Polar issues the purchase receipt, KeepState issues the usage statement. Taxes are collected and remitted by Polar as merchant of record. KeepState statements show pre-tax charges and say so. What is available right now, dated per row, is on the availability matrix.

how these two meters count · price book v1.3

Session time is metered per second and billed per minute, rounded at statement level to the cent.

The storage unit is the decimal gigabyte: 1 GB is 10^9 bytes, not a GiB of 2^30 bytes. A GB-month is the hourly average over the billing month.

every estimate's method and assumption set, content-hashed

Cruise bills as hosted sessions.

cruise · access: self-serve

Cruise is not a separate tier. A job runs hosted sessions under your account, so platform usage and model charges follow the rates above and the signup credit applies. The token limit is active, and so is the spend limit you set before a job runs. There is no general savings guarantee.

For larger workloads under agreed terms, a trial is scoped and priced in writing before any job runs. Typical trial shape: bounded tasks, deterministic tests, agreed rates.

Separately agreed trial fee: 20% of conservatively estimated net savings.

The performance fee is separate from what the trial costs to run, and both are stated.

Attempts that are not accepted cost what they consumed. Their spend is metered, reported and counted in the all-in cost, not written off.

Read the agreed trial terms

Start a trial conversation · What Cruise does, and what its evidence does not establish

Three different records

Verification verdict receipt
Carried by a verdict event that reports checks against the pinned tests; signed with the fleet judge key. It is not a bill or a payment-release instruction.
KeepState usage statement
Accounts for session time and checkpoint storage under the price book.
Polar purchase receipt
Records a credit purchase and its tax treatment; Polar is the merchant of record.

Receipt-triggered payment to an agent vendor is planned. Verification evidence.

Access today

live · self-serve

Self-serve signup is live: no card and no call. Capabilities differ from one another, and each carries its own access and deployment date on the availability record.

The published payment record covers sandbox checkout; production paid checkout is not established by that record. This is separate from self-serve signup. Read the payment scope.

Sign up, bring your provider key, and run a bounded task with Cruise. You can also test recovery with the kill-and-resume. Sign up from the header, or from the end of this page.

Free

Start with $10.00 in credit.

No card, no call. Bring your own provider key.

Included terms

About 15 hours of standard session time, or the storage equivalent

Session-minutes and storage only; model tokens ride your own key (BYOK)

Kill it, wake it, watch it resume mid-sentence: the kill-and-resume

One per person

Pay as you go

Prepaid credits

Hosted usage at the published rates. See the checkout qualification.

Included terms

Recorded checkout mechanism: Polar handles payment and tax as merchant of record; card data never touches KeepState.

A refund nets your ledger to exactly zero; every row is append-only

Funds-exhaustion checkpoint-and-park is tested; its running-session production check is pending.

Immutable usage statements, re-verified against the raw meters

Recorded funds-exhaustion tests checkpointed and parked a session, then resumed it after credit was added. Verification of that path on a running production session is pending. Billing evidence and limits

see it survive · free

See the recorded kill in three transcripts, or ask about a supervised interruption, a conversation where you type the kill on our bench yourself and watch the session come back.

See the walkthrough

When the credits run out.

The 31 August fleet test checkpointed and parked a real session after a debit exhausted its funds, then resumed it after credit was added. Check the session's recorded state before resuming, and see the current limits for failure cases.

The current production record confirms usage settlement and the interlock firing; its check of a running session being parked remains pending. A parked session bills storage only.

Money questions, straight answers.

How do budgets work across forks? +

Per-session token budgets are enforced by the gateway, and exceeding one checkpoints and parks the session. Budget pools across a fan-out are the design rather than proven behaviour.

A cap on a parent applying to the whole lineage has no gate yet, so it is product behaviour and not proof.

Do credits expire? +

Paid credits do not expire. The free signup credit expires 90 days after it is granted.

Credits are prepaid and sit on your ledger as append-only rows: every purchase, every meter tick and every refund is a row you can read back.

How do refunds work? +

Unused paid credits are refundable within 14 days of purchase. A refund nets your ledger to exactly zero.

The purchase and its reversal are both rows, and the round trip was rehearsed end to end before launch. Refunds are issued through Polar, which handles payment and tax (merchant of record).

record

What do I pay for a parked session? +

Storage only. A parked agent is a document: its checkpoints occupy deduplicated space and nothing else.

Waking it costs session-minutes again from the moment it resumes.

Do I pay twice for an interrupted model call? +

No. An interrupted call is stored and served from the store on retry, and the gateway enforces that rather than trusting the client.

Proven for Claude Code. For aider it is reported rather than promised: the gateway held the response 4 of 4 times, and the client walked back through 3 of 4.

record

What if nobody can tell whether a call completed? +

A supported replay uses a completed response already stored by the gateway. It is not a new provider request.

New requests and ambiguous attempts follow the documented accounting rules. Ambiguous gateway results are never billed until reconciled. Unreconciled after 24 hours resolves in the customer's favor and is flagged on the statement.

Can I run KeepState on my own servers? +

No. The KeepState engine runs only on KeepState infrastructure.

The current offer runs sessions and Cruise on KeepState infrastructure. You install the ks client locally; ks cruise run uploads the repository archive and approved manifest for a hosted job. Running verification or settlement attached to work in your own environment is not part of the current offer.

Plans, and what's planned.

planned tiers · POLICY · no prices until each exists

The current price book covers prepaid hosted usage. Subscriptions are planned. Each planned tier would price one axis on top of the same usage rates, and none carries a number here, because none of them can be bought yet.

Developer

checkpoint retention windows, personal budgets and caps

Team

seats, roles, shared budgets, the org audit log

Enterprise

compliance holds, regions, SSO and audit export

Subscriptions are planned. See the planned subscriptions on Proof.

Enterprise is not a plan card yet, because SSO, regions, retention, audit and contracting are not real yet. Enterprise readiness: the procurement ledger, stated as it is →

Put a bounded task to the test.

Start with $10.00 in signup credit for session time and checkpoint storage, no card. Model usage is paid to your provider. Want a recovery walkthrough? Book 30 minutes, and you type the kill -9 on our bench and watch the session come back.

keepstate.ai · independent verification for AI agent work