Skip to content

Affiliate marketingPlan

Nine ad accounts, nine environments.Nothing shared between them by accident.

An ad account is not a password, it is an environment: the storage the platform wrote, the device it measured and the address it saw. Run several from one browser and all three merge. Here each account holds its own, on your machine, and opens next month exactly as you left it.

Get startedContact sales

Work like this usually starts and stays on a plan. Enterprise starts at $5,000 and is about the fleet, the seats and the people behind it rather than a larger profile count.

Isolated per profile
cookies · localStorage · IndexedDB · cache
Route per profile
http · https · socks5 · socks5h
Lifetime
persistent
Bulk operations
duplicate · bulk-delete

01The work

The work

Three things that go wrong before anyone detects anything

None of these is exotic. They are the ordinary failure modes of running many accounts from one machine, and they are what the capabilities further down are for.
  • One jar

    A shared browser gives every account the same storage

    Cookies, localStorage and IndexedDB belong to the browser profile, not to the tab. Nine accounts in nine tabs are nine accounts in one jar, and the ninth login can read what the first one wrote.
  • Drift

    A device that changes between sessions is not an identity

    Values assembled by overriding JavaScript getters have to be re-applied for every document and every frame, and the engine underneath still answers with its own. An account whose fonts, screen and canvas move from week to week is inconsistent with itself, which is a different problem from being unremarkable.
  • Batches

    This work arrives in a loop and leaves in one call

    A launch needs forty profiles configured the same way on one afternoon, and a finished campaign needs them gone. Deletion takes the whole set in one call. Creation and duplication are one call each, so provisioning is a loop rather than a single request.

02What carries it

What carries it

Four capabilities do the work here

The full surface is on the capability page. These four are the ones this work leans on, and the fourth is the one people forget until somebody leaves.
Account oneAccount twoProfilebuyer-aProfilebuyer-bcookies · localStorage · IndexedDBcookies · localStorage · IndexedDBcanvas · WebGL · audio · fontscanvas · WebGL · audio · fontssocks5h → Frankfurtsocks5h → Chicagono shared storage · no shared device · no shared exitOne worker hostshared kernel, clock and network interface
Fig. 01Two accounts side by side. Storage, device values and exit address are held per profile, and the gap down the middle is the whole point. The dashed row underneath is what they still share.

Capabilities doing the work

Per-profile isolation
Storage that cannot reach sidewaysCookies, localStorage, IndexedDB and cache are held per profile. Nothing one account writes is legible to another, and deleting a profile takes its storage with it.
In-build fingerprints
The same device on launch five hundredCanvas, WebGL, WebGPU, audio, fonts, client hints and device metrics live inside the browser build rather than in JavaScript injected at page load, so an account presents one machine consistently instead of a machine that is patched again on every navigation.
One proxy per profile
One account, one addressHTTP, HTTPS, SOCKS5 and SOCKS5H per profile. With socks5h the DNS query resolves at the exit, so the name lookup does not leave from your own resolver while the request arrives from somewhere else entirely.
Persistent profiles
An account you can hand to somebody elseA persistent profile keeps its storage across launches, so the environment is an object under management rather than a state of one person's laptop. Media buyers rotate; the account's environment does not have to.

Timezone, locale, languages and geolocation are derived from the exit address rather than typed in. Every established platform in this category does that, so it is table stakes rather than a reason to pick one, and it is here.

03Plan or enterprise

Plan or enterprise

Most of this work runs on a plan

Profiles, proxies and bulk operations are the whole job, and none of it needs a conversation to begin.
PlansTypical herePick one and pay by card
One operator, or a team of fiveSign up, configure profiles, bring proxies, drive them from a script if you want to. This is where account work belongs until the fleet itself becomes a job.
EnterpriseFrom $5,000
When the fleet becomes the jobOnce the browsers run on machines you provision, several people need seats with different rights, and somebody has to answer for the fleet at three in the morning, what you are buying is infrastructure rather than a larger profile count.

Plans are paid from the first day and there is no trial, so if the fit is unclear, a call with the engineers is shorter than an evaluation.

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

Get startedPricing

04Where it stops

Where it stops

Two things this page will not claim

Set in the same typeface as the capabilities, because an evaluation finds them either way and finding them here is cheaper for both of us.
  • Not a boundary

    Profiles are separated in storage, not by a machine

    Profiles on one worker share its kernel, its clock and its network interface. The separation is of storage and identity, so work that needs machine separation needs separate workers.
  • Not an outcome

    No software decides what a platform does with an account

    Isolation and a consistent device are controls over the environment. Payment methods, creative, spend patterns and an account's own history are not things this platform touches, and nothing here is sold as a way around another company's rules.

Start with one account and one exit

The useful first test is small: one profile, one proxy, one platform you already run. Launch it, leave it a week, launch it again, and check whether anything about the environment moved.

Isolated per profile
cookies, localStorage, IndexedDB and cache
Route
one proxy per profile over http, https, socks5 or socks5h, with socks5h resolving DNS at the exit
Entry
a plan carries this work; enterprise is about the fleet around it

Everything on this page is documented rather than described. Where the documentation and this page disagree, the documentation is right and the page is a bug.