Skip to content

Independent verification for AI agent work.

AI does the work. Your tests decide.

KeepState checks agent work against acceptance tests you approve before the run. Every attempt and cost stays on the record; each verdict carries a signed receipt.

$10.00 of session and storage credit at signup. Bring your own model key. Model usage is billed separately.Verification and signed receipts today.
Receipt-triggered payment is planned.

KeepState Illustrative
receipt

Work, accounted for.

One record. A basis both sides can inspect.

Work
Bounded coding task
Acceptance
Buyer-approved tests
Verifier
Independent host runner
Record
Attempts · cost · verdict
Illustrative verdict Accepted
ILLUSTRATION ONLY
No real job, signature or payment.
Buyer-approved tests.
Independent verification.

The work has an account. Now give it a receipt.

Cruise · live

Verification and signed receipts.
Buyer-approved tests. Host-run checks. Every attempt accounted for.

Clearing · planned

The receipt releases the payment.
Receipt-triggered payment is planned. Not live today.

01 / From a job to a shared record

Agree on done.
Then let the work begin.

KeepState’s Cruise workflow turns the buyer’s acceptance tests into an independent record of what passed. The agent does the work. The tests decide the outcome.

01

Lock

Start from the repository’s existing checks. Approve the acceptance manifest before the run.

02

Run

The agent works in a durable session. Save points keep its files and context ready to resume.

03

Verify

Pinned tests run on the host, beyond the agent’s reach. Forged pass logs are refused.

04

Escalate

Restore the checkpoint before trying the next model. After the last model, review the job: resume with a wider ladder or cancel.

05

Receipt

Reconcile every attempt and cost. Each verdict carries the locked tests’ digest and a signed receipt.

Cruise supports bounded coding tasks with deterministic tests. Payment clearing is planned.

Inside the workflow
Scope and verification details
01 / Verify

Let tests decide what passes.

Cruise checks work with an independent runner the agent cannot reach. It starts with a cheaper model and restores the checkpoint before escalating a failed attempt.

Cruise. Set the task. It drives, tests, and retries.

Current scope: bounded coding tasks (scoped tasks with a fixed test suite) on the KeepState runtime, across Anthropic-native and OpenAI-compatible model families.

See Cruise · View the test record

AttemptIndependent
check
Restore and retry
Restore and retry when needed.

Illustration the record defines the scope original record

Recovery covers supported agents and saved checkpoint state. External effects stay outside that boundary. Current availability →

Verify. Your checks decide what passes.

Recover. Return to recorded state.

Account. Every attempt, on the record.

02 / Continuity beneath the receipt

Your agents
never start over.

A failed attempt should not erase the work that came before it. Retries fork from the parked checkpoint. Saved session state supports the next attempt.

One saved stateA considered next step
A saved state forks into a retryAn initial attempt reaches a saved checkpoint. The first branch is held; another resumes the saved context and reaches verification. This is an illustration of the workflow.RunSaved stateAttempt heldResume → verify

Workflow illustration. A saved state supports the next verified attempt.

03 / The record is open

Trust includes
the uncomfortable row.

If we verify other people’s work, you should be able to inspect ours. Measured results and known failures belong in the same record.

100

Green gates in the ledger
Current green verdicts. Earlier runs and their limits remain in the record.

MEASURED · v0.1.26
Record synced 2026-09-19

25 / 25

Kill-and-resume cycles
Historical bench result. Fresh cycles with memory and files intact.

MEASURED · 2026-08-25
Read the bench record ↗

Measurement scope

fresh kill/resume cycles, bench; the claim is the Wilson interval [86.7%, 100%], not the point

Sample: 25 fresh kill/resume cycles

Durability findings

The row we kept.

No open durability finding is listed in this release record; that is not independent assurance for the current deployment.

Every claim expires with its gate evidence. No claim outlives its gate.

Read the proof record
Availability, fit and boundaries

Evidence is part of the product

Check us.

Check the scope before you start.

See which capabilities are proven, which are enabled in production, and what KeepState does not claim.

Cruise requires bounded coding tasks with deterministic tests. Customer data requires classification and named authorization; the manifest enforces what you supply and does not detect sensitivity.

What works today · Security and data handling

04 / An independent position

Between “we did it”
and “it’s accepted.”

The vendor’s account of its own work is only one side of the story. KeepState gives the buyer and vendor a record grounded in tests agreed before the work begins.

What independence means
  1. 01

    The buyer sets acceptance.

    Tests are locked on approval. The verifier refuses changes to the pinned test code.

  2. 02

    The verifier sits outside.

    Host-run checks are out of the agent’s reach. A fabricated pass log is not a pass.

  3. 03

    The receipt keeps the account.

    Attempts and costs stay in the ledger. A signed verdict receipt makes later changes detectable.

Accounting record and pricing
03 / Account

What did every attempt cost?

KeepState records attempts and costs in its ledger. In the accepted-work test, settlement cleared only after every attempt reconciled, including failed attempts.

Publication authorization only: this scope does not create an external pull request.

The recorded fixture uses a placeholder tariff. It is not a customer price.

View the accounting record · See live pricing

Attempt record

01AttemptWhat ran
02VerificationWhat passed
03Accounted costWhat it consumed

Illustration accounting structure; the record carries results and limits original record

Start with one bounded task

Put “done”
on the record.

Start with a hosted session.
Use Cruise for bounded coding tasks with tests that define done.

Sign up

Cruise is available to every hosted account.
Explore the developer path

Choose how to start

A considered first step

Choose how to start.

01 / Explore

Cruise, from your terminal.

Describe the goal, approve the checks, run. Cruise supports bounded coding tasks with deterministic tests.

Explore Cruise →
How the offer works

The durable agent session cloud

KeepState runs your AI agents under your own acceptance rules, on save points it can rewind and retry, with a ledger of reconciled costs.

Run coding agents with saved checkpoints, independent checks and an account of every attempt.

Run AI agents with rules for done.

KeepState runs your agents, checks their work against your acceptance rules, and keeps save points for recovery. Its ledger accounts for attempts and costs.

Available to every hosted account. Cruise supports bounded coding tasks with deterministic tests.

See the walkthrough · Free-credit terms · Scope and evidence

02 / Continue

A hosted session.

Try a kill-and-resume yourself.

Follow the quickstart →

Prefer to watch first? See the walkthrough.

Credit and model usage

Sign up with no card for $10.00 in credit, once per identity. Credit covers session time and checkpoint storage; model tokens use your own provider key.

Keep the point.
Continue the work.