Priced by the run,
not by the token.

No. Local is the product, not a sample of it — the same runtime, the same replay engine, the same audit log, with no cap on workflows or runs. What the paid tiers add is a place to keep the results that isn't one person's laptop, and the review and access controls a team needs around them. If you never want that, you never need to pay.

One entry in a compiled workflow: verify the pre-condition, resolve the target by similarity, act, then poll until the post-condition holds. A login workflow is typically 4–8 steps. A step that fails closed still counts; a step that never ran because an earlier one stopped the run does not. fs stats shows the exact number for every workflow you have, locally and for free, before you decide on a plan.

There are none to charge for. Replay makes zero model calls by design, and relocation after drift uses similarity rather than inference. The single optional model — region labelling on captured pages — runs at build time, is billed per capture, and is disabled until you enable it. Nothing in the automation runtime gains a model dependency when you turn it on.

Overage is $2 per 1,000 steps on Pro and $1.20 per 1,000 on Team, and you can cap it at zero — in which case runs queue until the next period instead of billing. Nothing is throttled silently and nothing is deleted; you get a notification at 80% and again at 100%, in the tool and by email.

The runtime is always self-hosted — it is a CLI on your machine or your runner. What Enterprise adds is a self-hosted control plane: the store, the registry, the repair queue and the audit chain running inside your VPC, with the browser fleet on your own instances and a KMS key you hold for the audit log.

No. A seat is a human who logs in — reviews repairs, approves workflows, reads audit trails. An MCP-connected agent replaying an approved workflow consumes steps, not a seat, and so does CI. Charging per agent would price the thing the product exists to make cheap.

One click, from billing, effective at the end of the period. Your workflows were always files in your repo, so there is nothing to export to keep running them — drop the hosted store and the same fs replay keeps working against your local one. We will export your run history and audit chain as JSON on the way out regardless.