Storm Proxies proxies in Mosaic: one line, an exit per profile

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

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

Connect Storm Proxies to Mosaic

1. In Storm Proxies'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 Storm Proxies and saves it as a provider you can reuse.
3. Attach the Storm Proxies line to each profile. Mosaic checks the exit it reaches before the browser opens.
4. Press Start. Mosaic checks the proxy before every launch and will not open the browser until Storm Proxies has answered and tunnelled, so a dead proxy never leaks your own address.

Storm Proxies's line has no session token Mosaic reads, so profiles share its rotation unless you paste one of Storm Proxies's own sticky endpoints. If a Storm Proxies endpoint stops answering, the launch stops and names what failed, so you fix the line rather than browse on your own IP.

How it works: Provider minting

What Storm Proxies carries in its line

Storm Proxies's gateway line, as Mosaic reads it, has no country, city or session token that Mosaic recognises. So Mosaic uses the line as you paste it: whichever Storm Proxies endpoint and country the line already names is the exit. To put a profile in a particular place, paste the Storm Proxies endpoint for that place; to keep one exit for a profile, paste one of Storm Proxies's sticky endpoints.

What Mosaic does with the Storm Proxies exit

Once a Storm Proxies 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 Storm Proxies proxy, so a page cannot read your real address that way. The authentication runs through a local relay, so a Storm Proxies 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 Storm Proxies bill is between you and Storm Proxies. Mosaic reads Storm Proxies's format from the published documentation and has not run it against a live Storm Proxies account, so the row shows an untested badge; the format may be out of date if Storm Proxies has changed it. Whether to run several accounts on Storm Proxies 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.