Browser automation for a team,
not a laptop.

The self-serve tier is one concurrent session per account, on purpose — it is the shape an individual developer needs. A team running fleets of accounts needs concurrency, and that is where deployment stops being someone's laptop: concurrent sessions run on servers behind proxies, which needs datacentre or residential IPs and GPU-less rendering that stays coherent. We size that with you rather than quoting a number that would be wrong for your account count and geography.

Yes. The browser is a binary you launch; the licence check is one call. For a private deployment the binary and the humanized-input layer run on your machines, under your network, with the balance billed against your own ConnectOnion account. Nothing about a session's contents reaches us — we verify the licence, not the work. The full data flow is on the security page.

A fingerprint that changes between sessions is as damning as one that is obviously synthetic. Persona continuity — one coherent identity per account, persisted across restarts, with a fingerprint derived from a real host rather than randomised — is the part that matters at fleet scale, and the part self-serve does not address. This is scoped per deployment with you.

It is a tool for authorised automation: testing, accounts you own, and work you have permission to do — the same footing as a VPN or a privacy browser. We do not build platform-specific bypass modules and we do not help evade a site's security for accounts you do not control. If your use is authorised, the tool removes the automation tells that would otherwise flag legitimate work; if it is not, this is the wrong product. We are happy to talk through where a specific use falls.

Self-serve is $0.10 per browser-hour from a ConnectOnion balance — usage, not a seat. Enterprise keeps the same balance model so there is one bill to reason about, and adds the things a team needs: concurrency, private deployment, persona continuity, and a support path. A conversation sizes those; the meter stays the honest part underneath.

No, and we say so on every page — no product does. It clears the common engine-level tells (navigator.webdriver, the Sec-CH-UA brand, the WebGL renderer) and drives input with human motor timing, which is where most automation is caught. Two checks still catch it and are documented. A vendor who claims to pass everything is the one to distrust; we would rather scope what your targets actually check.