Free during the beta, up to 3 sessions.
Every feature on every plan. What changes is how many sessions can run at once on a machine.
We are not taking payments yet. The paid tiers below are shown so you know what is coming; nothing can be bought and nothing is charged.
Free
The whole thing. Sign in for more of it.
- 1 session with no account
- 3 sessions with a free account
- Every feature, no time limit
- Community
No card, no trial clock. The free key is issued the moment you sign in.
Member
Coming soonFor one person and a few jobs.
Payments open after the beta.
- 50 concurrent sessions
- 1 license key
- Cancel any time
- Hands-on support
VIP
Coming soonReal concurrency for a small team.
Payments open after the beta.
- 200 concurrent sessions
- Multiple license keys
- Usage across machines
- Hands-on support
Sponsor
Coming soonProduction fleets.
Payments open after the beta.
- 2,000 concurrent sessions
- Early access to engine builds
- Invoicing
- Priority support
Gamer
Coming soonNo cap. Run whatever you want.
Payments open after the beta.
- Unlimited concurrent sessions
- Patch requests
- Security review, procurement
- Priority support, named engineer
- Latest Google Chrome and Firefox builds, with compatibility updates
- Windows
- JavaScript / TypeScript, Python and Java
- Playwright, Puppeteer and CDP
- Human-like input, on by default
- Persistent profiles and reproducible identities
- Proxy support with WebRTC leak-proofing
- MCP server for AI agents
During the beta nothing is for sale and nothing is charged. The paid tiers above are what they will cost when payments open, in USD, billed monthly, cancel any time. Sign in now and the free key you get is yours for good.
Frequently Asked Questions
What do I actually get for free?
The whole product. Same patched engines, same API, same measurement suite, no card, no trial clock. With nothing set up at all you get 1 session at a time; sign in with an email address and you get a free key for 3. The paid tiers raise the limit further and add support. If 3 at a time is enough for what you are doing, that is fine and you never need to pay us.
How is the limit enforced?
Locally. The client counts its own running instances on the machine and refuses to start one past the limit. It does not phone home to do it, which is what lets the free tier work offline and keeps the fail-open promise honest. It is a licence term with a check attached, not DRM, someone determined to defeat it can, and the pricing assumes that.
Is the limit per machine or per account?
Per machine. Ten machines each get their own limit, including on the free tier. That is deliberate: the workload people actually pay for is running many browsers on one box, and an account-wide cap would need a heartbeat to the licence server on every launch, which would break offline use and contradict the fail-open behaviour documented above.
When do payments open?
When the beta is over. Until then the free tier is the product, and a free key issued now stays a free key afterwards. If 3 sessions at a time is not enough for what you are doing during the beta, write to us and say so, that is the kind of feedback the beta is for.
What happens if my card fails?
Nothing, at first. A subscription in past_due keeps working, and there is a three-day grace period after the paid period ends. A failed retry should not take down your production automation before your bank has finished thinking about it. Access ends only once Stripe has exhausted its retries.
Can I get a refund?
Yes, within 14 days of your first payment, for any reason, no questions, as long as you have used less than 24 hours of it. Test on the free tier first, that is what it is for. After that, cancel any time and you keep access until the end of the period you have paid for. The full terms are on the refunds page.
Do you see my traffic?
No. The browser runs on your machine and connects to your targets through your proxies. What this service receives is a license key check, the key, a machine id, optionally a hostname, plus the IP it arrives from, which is logged briefly for rate limiting. Not URLs, not page content, not credentials.
What happens if your license server goes down?
Your automation keeps running. The client caches its last successful validation and fails open on our outage, an outage on our side is our fault, and breaking your production for it would be indefensible. The check is not a kill switch.
Can I self-host the license server?
On Gamer, or under a separate agreement, yes. The validation endpoint is a single documented POST, and the client takes a base URL, so pointing it at your own deployment is configuration rather than a fork.
What am I allowed to use this for?
Testing and automating systems you own or have permission to access. That boundary is not decoration, see acceptable use. We will cancel a license rather than defend a use we do not want to be part of.