Skip to content

Digital agenciesEnterprise

Twenty clients, one platform.No shared state, and a clean offboarding.

An agency's exposure is custody rather than detection: whose laptop holds the client's session, who can open it, and what leaves when a contractor's access ends. A profile holds the session so the credential does not have to, roles are checked on the API rather than in an interface, and the browsers run on hardware you operate.

Contact salesGet started

Work like this is usually enterprise, which starts at $5,000 and is priced against the operation rather than per profile. Plans are real, and one of them is the right start for a single operator.

Roles
owner · admin · member
Deployment
self-hosted fleet
Bulk operations
duplicate · bulk-delete
Entry
from $5,000

01The work

The work

Three questions a client asks that are not about fingerprints

Every one of them is answered by where things run and who can reach them, which is why this page is about custody rather than about detection.
  • Custody

    Where does the client's session actually live

    In a persistent profile on a machine you operate, rather than in a personal browser on a laptop that goes home at six. The profile is the object under management, and a member can launch it without ever being handed the credential inside it.
  • Offboarding

    What ends when a contractor's access ends

    Their membership of the organisation. The profiles they were working in stay where they are, with their storage intact, and nothing has to be re-created because somebody left.
  • Review

    What leaves your infrastructure at all

    Browsers, sessions and profile storage run on your machines. Accounts, plans, licence verification and the metadata describing organisations and profiles live in our cloud. That boundary is worth reading before a client asks rather than during the answer.

02What carries it

What carries it

Four capabilities do the work here

One of them is the reason a competitor cannot write this page: they run the browsers, so the fleet is never yours to place.
OrganisationYour agencyowner · admin · member, enforced on the APIclient-a42 profilesclient-b18 profilesclient-c7 profilesabove the line: browsers, sessions and storage on machines you operatebelow the line: oursCloud control planeAccounts, plans, licence verificationorganisation and profile metadata
Fig. 01One organisation, three clients, and the line that matters. Browsers, sessions and storage sit on machines you operate; accounts, plans, licence verification and profile metadata sit with us.

Capabilities doing the work

Organisations and roles
Owner, admin and member, enforced on the APIAccess is granted at the organisation and checked server-side rather than hidden behind an interface, and operations against the fleet are recorded.
Self-hosted fleetOnly here
The whole platform on machines you operateControl plane, workers, browser builds and profile storage all deploy onto infrastructure you provision. Platforms that run the browsers themselves cannot offer this, which is the difference worth taking to a client conversation.
Bulk operations
A new client is a short script, not an afternoonOne call deletes a client's whole set when a retainer ends. Duplicating a configured profile and creating one are a call each, so standing a client up is a loop over the API rather than an afternoon in a form.
Per-profile isolation and routing
One client's storage never meets another'sCookies, localStorage, IndexedDB, cache and the exit address are held per profile, so keeping clients apart does not depend on anybody remembering which window belongs to whom.

The boundary in the drawing above is the part a security review will ask about, and it is written out in full on the security page rather than summarised here.

03Plan or enterprise

Plan or enterprise

This is the enterprise page

Not because agencies are large, but because seats, roles and a fleet somebody operates are what an agency needs and what enterprise is for.
PlansPick one and pay by card
Two or three clients and one operatorA plan runs profiles and proxies perfectly well. What it does not carry is the fleet, the seats and the role separation that arrive with the fourth client.
EnterpriseTypical hereFrom $5,000
Seats, roles, and a fleet you operatePriced against the operation rather than per profile: how many profiles you hold, how many machines the fleet spans, how many seats, and whether we deploy alongside you or hand over the documentation.

Bring the client count, the seat count and the platforms you work against, and the first call ends with a number rather than a brochure.

Plans and enterprise run the same platform. The difference is who operates the fleet and how many people need a seat on it.

Contact salesPricing

04Where it stops

Where it stops

Two things this page will not claim

Both are the kind of thing an agency discovers in month two, so they are here in month zero.
  • Three roles

    Access is organisation-wide, not per client

    Owner, admin and member are the roles. There is no per-client scope inside one organisation, so restricting a contractor to a subset of a client list is not something a role does.
  • Not self-hosted

    The cloud side stays ours

    Self-hosting covers the fleet: control plane, workers, browsers and profile storage. Accounts, plans, licence verification and organisation and profile metadata stay with us, and no page here will tell you that nothing leaves your network.

Take the boundary to the security review first

The fastest way to know whether this fits an agency is to read what crosses to our cloud and what never does, then decide whether the fleet belongs on your hardware. Both are documented.

Roles
owner, admin and member, enforced on the API
Execution
browsers, sessions and profile storage on machines you operate
Held by us
accounts, plans, licence verification, and organisation and profile metadata

Pricing is published because a number saves a call. What it does not tell you is whether the boundary suits your clients, which is the part worth reading first.