Solutions
5 kinds of work.A different part of the platform under each.
These are not one page with the noun changed. Each names the operational problem, the four capabilities that carry it, whether the work runs on a plan or needs enterprise, and where it stops. Pick by the problem rather than by the label.
- Pages
- 5
- Split
- 4 on a plan · 1 enterprise
- Folded in
- e-commerce
- Written once
- /multi-profile
01Route
Route
Which page answers which problem
Affiliate marketing
Nine advertiser accounts across four platforms, run from one desk, where each account has to be the only thing that has ever happened on its machine.
- Fit
- Plan
- Capabilities
- per-profile isolation
- persistent profiles
Web scraping
Collection that has to survive a page rendered client-side, a catalogue served by region, and a DNS query that must not come from your own network.
- Fit
- Plan
- Capabilities
- cluster mode
- socks5h
Ad and price verification
Checking what somebody in Munich on an Android handset is actually shown, without your office network, your language header or last week's session in the way.
- Fit
- Plan
- Capabilities
- exit-derived region
- Android device model
Digital agencies
Twenty clients, a dozen contractors and a rotation, where the question that matters is who can open which client's session and what walks out the day they leave.
- Fit
- Enterprise
- Capabilities
- organisation roles
- self-hosting
Privacy research
Measurement work on fingerprinting and detection, where the fixture has to be describable, repeatable, and not itself an artefact of the patch that produced it.
- Fit
- Plan
- Capabilities
- in-build signals
- named lifetimes
02Underneath
Underneath
The same platform under all five
Capability
What a profile actually holds
Storage, device signature, route and lifetime, taken apart one at a time. Read this when a solution page named a capability and you want the mechanism behind it.
Trust
What a security review will ask for
Where execution happens, what crosses to our cloud, what we hold and what we will not claim. This is the page to hand to somebody else's security team.
Operations
Running the fleet yourself
The one-command control plane, validated configuration swaps, drain-then-roll updates and the role model. The infrastructure argument in full.
03Not here
Not here
Three pages you will not find
- Folded in
E-commerce
Marketplace and storefront work splits cleanly in two: operating long-lived accounts is one page and seeing what a given market is served is another. What was left over was per-profile isolation, which is the capability page. A page whose only distinguishing feature is its noun is no use to anyone. - Not sold
A proxy pool
Per-profile routing takes HTTP, HTTPS, SOCKS5 and SOCKS5H endpoints that you supply. There is no bundled inventory, no resale and no per-gigabyte line, so there is no page here about buying addresses from us. - Not promised
Ban avoidance
No page here says accounts will survive. Isolation and a consistent device are controls over the environment a platform observes; what that platform then decides also rests on payment, content and behaviour, none of which this software touches.
Still not sure which page you are on
The five differ in which capability carries the weight rather than in what the product is. If two of them look right, read the capability page first and come back with a shorter question.
- Pick by
- the operational problem, not the label
- Shared
- isolation, fingerprints, routing and automation are documented once, on the capability page
- Entry
- a plan carries most of this work; enterprise starts at $5,000
Every page in this section names its own limits in the same typeface as its capabilities. That is deliberate, and it is the fastest way to work out whether this is the wrong tool for your week.