Real 4G and 5G SIMs on hardware we operate. British exits on EE, O2 and Three, plus eight more countries on the same endpoint. Every request leaves from a different subscriber IP. You pay for gigabytes, nothing else.
Built for web scraping, price comparison and market intelligence companies. We sell to registered businesses only — accounts are reviewed before access is granted.
Who it's for
SIMSwarm is infrastructure for companies whose product depends on collecting public web data at scale. It is not a consumer anonymity service, and it is not available to the general public. Every account is reviewed against a stated commercial use case before it is switched on.
Company details, the kind of sites in scope, and roughly how much traffic a month. A sentence about what the crawl actually does is usually enough.
Normally within one business day. We may come back with a question about a specific target — that is us doing our job, not stalling.
Credentials are issued against your account with an evaluation gigabyte, so you can benchmark us on your own hardest target before committing.
Why mobile wins
Mobile carriers put tens of thousands of real customers behind a single CGNAT address. When your request leaves an EE mast in Manchester, it is genuinely indistinguishable from the person scrolling next to it — because it is the same IP.
A target site that blocks one of our addresses also blocks every real subscriber sharing it. Almost nobody does. That is why mobile survives where datacentre ranges die in minutes.
No pool-wide rotation windows. Each connection is dispatched to a different SIM, so a thousand concurrent requests leave from a thousand different masts.
Contracts in our name, modems in our racks, in British data centres. No consent-scraped residential SDK, no mystery peer network, no phone-in-someone's-pocket surprises.
| Datacentre | Residential pools | SIMSwarm mobile | |
|---|---|---|---|
| Where the IP comes from | Hosting ASN | Peer SDKs on consumer devices | Our own contracted SIMs |
| Trust at hard targets | Low | Medium | Highest |
| Rotation granularity | Per session | Per request or timed | Per request, per mast |
| Location control | ASN only | Country / city | Country, city, carrier & server |
| Provenance you can audit | Partial | Opaque | Full SIM & site register |
| Typical UK price per GB | £0.50 – £1 | £3 – £8 | £1.20 – £2.50 |
Competitor pricing observed August 2026 across published rate cards. Datacentre remains cheaper per gigabyte — it just stops working on the targets you are reading this page about.
How it works
Point your existing scraper at a single host and port. No SDK, no browser agent, no rewrite.
Standard HTTP, HTTPS and SOCKS5 with basic auth. Works unchanged with Scrapy, Playwright, Puppeteer, curl, HTTPX and every off-the-shelf scraper you already run.
Our dispatcher scores every online SIM on health, recent target history and current load, then hands your request the freshest exit that matches your targeting rules.
Metering happens at the gateway, per request, to the kilobyte. Failed and blocked requests below 400 bytes are never charged.
Default behaviour. Nothing to configure, no rotation endpoint to call.
Holding one exit IP for a whole journey is in development. Today every request rotates.
Pin to Manchester, to EE, to the US, or to one specific server — encoded in the username, no API call.
Your own port on the gateway, pinned to your account — nobody else’s credentials work on it.
All three on a single port — the gateway detects the protocol from the first byte. One credential for each.
Authenticate by source address on your dedicated port — no credentials in your config at all.
An exit that does not answer inside three seconds is abandoned and the request re-dialled on a fresh one.
Your account is bound to a named pool. Your own targeting narrows within it — it can never reach outside.
Integration
Your credential encodes your targeting. Change the username, change the exit — no API calls, no state to manage.
# rotate on every request (default)
curl -x gb.simswarm.io:9000 \
-U "swarm11072:secret" \
https://www.example.co.uk/search?q=widgets
# pin to Birmingham, on EE — still a fresh IP every request
curl -x gb.simswarm.io:9000 \
-U "swarm11072-city-birmingham-carrier-ee:secret" \
https://www.example.co.uk/storesimport httpx
PROXY = "http://swarm11072:secret@gb.simswarm.io:9000"
with httpx.Client(proxy=PROXY, timeout=30) as c:
for url in urls: # each call = a new UK mobile IP
r = c.get(url)
print(r.status_code, r.headers["x-swarm-exit"])import { HttpsProxyAgent } from "https-proxy-agent";
const agent = new HttpsProxyAgent(
"http://swarm11072:secret@gb.simswarm.io:9000"
);
const res = await fetch("https://www.example.co.uk/", { agent });
console.log(res.headers.get("x-swarm-exit")); // 82.132.214.19 (EE/Manchester)# settings.py
DOWNLOADER_MIDDLEWARES = {
"scrapy.downloadermiddlewares.httpproxy.HttpProxyMiddleware": 110,
}
HTTP_PROXY = "http://swarm11072:secret@gb.simswarm.io:9000"
CONCURRENT_REQUESTS = 256 # no concurrency cap on our side
RETRY_TIMES = 2 # gateway already retries dead SIMs for freeconst browser = await chromium.launch({
proxy: {
server: "http://gb.simswarm.io:9000",
username: "swarm11072-city-manchester",
password: "secret"
}
});
// every navigation and XHR leaves from a different Manchester mobile IPCoverage
Britain is the core — EE, O2 and Three, from London and Manchester out to Crewe, Carlisle and Rugby. But the swarm is not UK-only, and has not been for a while.
There are no regional hostnames to migrate to. Every country below is reached from the same gateway on the same credential by adding one token to your username, so widening a crawl costs you a string change rather than an integration.
-country-gb
Networks
Cities
-country-us
Networks
Cities
bostonmassachusetts Chicago Houston houstontexas Los Angeles losangelescalifornia Miami miamiflorida New York newyorkcity North Carolina Phoenix phoenixarizona-country-ie
Networks
Cities
-country-nl
Networks
Cities
-country-de
Networks
Cities
-country-fr
Networks
Cities
-country-es
Networks
Cities
-country-pl
Networks
Cities
pozna-country-au
Networks
Cities
How to write the targeting. A value is the name lower-cased with spaces and punctuation removed — -carrier-tmobile, -city-losangelescalifornia — and a unique prefix is enough, so -city-losangeles works just as well. Where a value is not what you would guess it is printed above in grey. Combine them freely: -country-us-carrier-verizon-city-chicago. A prefix matching more than one city is rejected with a 400 naming the candidates it was torn between, rather than quietly picking one.
Pricing
Pay as you go, no monthly minimum, and your balance never expires. Move the slider to see where you land.
Roughly 786,000 product pages a month at 200 KB each, or 15.7 million JSON API calls at 10 KB.
You keep £675 a month versus the enterprise rate card. See all bands →
Every IP in the swarm traces back to a SIM contract in SIMSwarm's name and a modem in a site we lease. There is no peer network, no bundled SDK and no consumer device earning pennies to carry your traffic. If your compliance team asks where an IP came from, we can tell them — down to the rack.
No credential stuffing, no card testing, no fraud, no CSAM, no traffic aimed at UK critical national infrastructure — and no consumer accounts at all. Selling only to vetted businesses is not gatekeeping for its own sake: it is how a mobile pool stays clean enough to still work on hard targets next year. We would rather lose the revenue than end up in the sort of case study that gets a whole industry regulated.
Residential pools are usually assembled from consumer devices running a partner SDK — the IPs are real, but the provenance is murky and the exit could vanish mid-session when someone closes an app. Our exits are SIM cards we pay a monthly bill for, in modems we rack ourselves. They do not disappear, and we can account for every one of them.
Yes, always. Each new connection is dispatched to a different SIM by the gateway, so parallel requests leave from different carriers and cities simultaneously. Rotation is currently the only mode — sticky sessions, which hold one exit for a whole journey, are in development and not offered yet. If your work depends on them, tell us when you apply and we will let you know when they land.
Bytes on the wire in both directions, measured at the gateway, including TLS overhead. Gateway-initiated retries onto a fresh exit are free. The usage API breaks your consumption down by day so you can reconcile it against your own figures rather than taking our invoice on trust.
Mobile adds latency — anyone claiming otherwise is selling datacentre IPs with a mobile label. Expect 180–400 ms to first byte and 1.9 s median for a full page fetch. In exchange you get success rates on hard targets that datacentre ranges have not matched in years.
Yes. Dedicated ports with a private SIM, your own rotation schedule and an API reset endpoint are available from £45/SIM/month with unmetered traffic. Sensible when you are hammering one target continuously; the swarm is better for broad crawls.
They are already here. Alongside the UK we run exits in the United States, Ireland, the Netherlands, Germany, France, Spain, Poland and Australia — nine countries in total, all on the one gateway. You reach them by adding -country-us or -country-de to your username; there is no second endpoint to integrate against and no separate contract.
No. SIMSwarm is sold to registered companies with a named technical contact and a stated commercial use case — price comparison, market intelligence, SEO data and similar. There is no self-serve public signup and no consumer plan. If you are an independent contractor doing this work for a client, apply with the client's use case and your own company details.
Because a mobile pool is a shared reputation. One customer running bulk account creation or ticket bots gets IP ranges flagged that everybody else depends on. Vetting the intake is the cheapest way to keep success rates high on the hard targets our actual customers care about, and it keeps us well clear of the traffic that attracts regulators.
Collecting publicly available data generally is, but the details matter — copyright, database rights, UK GDPR where personal data is involved, and the target's own terms. We are infrastructure, not your legal advisor: bring a lawful use case, and our acceptable use policy tells you where our line sits.
Tell us your company, the sites in scope and rough monthly volume. Approved accounts get an evaluation gigabyte — if our success rate on your hardest target does not beat what you run today, you have lost twenty minutes.
Registered businesses only. Reviewed within one business day.