PacketStream proxies in Mosaic: one line, an exit per profile

We make Mosaic, the local-first anti-detect browser; PacketStream is a proxy seller you bring your own account to. This page is the setup, not a review of PacketStream's network.

You bring a PacketStream account; Mosaic brings the browser. Mosaic reads PacketStream's gateway line from the seller's own documentation, so the line you copy from PacketStream is kept as a template, and the targeting and session tokens are read from it rather than guessed.

Connect PacketStream to Mosaic

1. In PacketStream's dashboard, copy the gateway line for the pool you want, with your username and password in it.
2. In Mosaic, open a profile's proxy field, or the Proxies screen, and paste the line. Mosaic detects it as PacketStream and saves it as a provider you can reuse.
3. Create profiles from the provider. Each one mints its own PacketStream session, so each profile browses from a different exit.
4. Press Start. Mosaic checks the proxy before every launch and will not open the browser until PacketStream has answered and tunnelled, so a dead proxy never leaks your own address.

PacketStream carries a session id Mosaic recognises, so each profile mints its own session and holds its own exit. A PacketStream session that answers but reaches nothing is swapped for a fresh one rather than retried, because a residential session that is dead stays dead for every attempt on the same token.

How it works: Provider minting

What you can set per profile with PacketStream

PacketStream's line carries the exit country and a sticky session id, so those are what Mosaic lets you choose per profile. Pick country in PacketStream's own words, and the exit matches. A pick PacketStream has no word for is refused by name, because a token a gateway silently ignores would put the profile somewhere else without telling you. The words Mosaic does not recognise still survive, because the line is copied rather than rebuilt, so an option PacketStream added that Mosaic has never seen still reaches the exit.

What Mosaic does with the PacketStream exit

Once a PacketStream proxy is checked, Mosaic reads the public address and city it comes out at and matches the profile to it: the timezone, the languages and the geolocation are set from the exit, not from the proxy's label. Mosaic also stops WebRTC from going around the PacketStream proxy, so a page cannot read your real address that way. The authentication runs through a local relay, so a PacketStream login works over HTTP, HTTPS and SOCKS5, including SOCKS5 with a username and password, which Chrome cannot log in to on its own.

The honest limits

Mosaic does not sell proxies or proxy traffic; the PacketStream bill is between you and PacketStream. Mosaic reads PacketStream's format from the published documentation and has not run it against a live PacketStream account, so the row shows an untested badge; the format may be out of date if PacketStream has changed it. Whether to run several accounts on PacketStream exits is the platform's rule, not ours: Mosaic keeps accounts you are entitled to run apart, and does not change what a site allows.

If you are still choosing a seller, the proxies worth using with an anti-detect browser sets out what to look for, and rotating against sticky sessions explains which kind each job wants. Mosaic Pro is $49 a month for any number of profiles, with the first 14 days free, and Free holds 3 profiles.