Introduction
bytetourist is a proxy & scraping network that you own end to end. Instead of renting bandwidth from a proxy reseller, you run your own fleet of nodes — cloud VMs across a multi-cloud, datacenter fleet — that make the final outbound HTTP call, with a central router that sends each request to the right node using one of ten selection strategies.
It is the layer that scraping APIs and “web unblockers” rent. bytetourist lets you operate it yourself: own the IPs, own the routing, own the margin.
Who it’s for
Section titled “Who it’s for”- Scraping & data teams who want datacenter egress with real routing control and country/region targeting, not a single rotating-proxy endpoint.
- Platforms that resell proxy or scraping capacity and want to stop paying a ~30% bandwidth tax to upstream proxy vendors.
- Anyone who needs geo-targeted, fingerprint-consistent outbound requests at scale, with per-tenant quotas and metering built in.
Key concepts
Section titled “Key concepts”Everything you need to use bytetourist comes down to a few ideas:
| Concept | What it means |
|---|---|
| node | A machine in your fleet that makes the final outgoing call from its own datacenter IP. |
| fleet | All your nodes across every cloud and region — grown, healed, and shrunk automatically. |
| targeting | Constrain which node serves a request — by country and region. |
| strategy | How a node is picked from the eligible set — ten strategies, chosen per request. |
| session | Pin a series of requests to the same IP for multi-step flows — see Sessions. |
You reach the whole thing as a standard HTTP proxy: point your client at it, send your API key, and encode targeting right in the request.
How it compares
Section titled “How it compares”bytetourist sits one layer below scraping APIs like Firecrawl. Those tools turn a URL into clean data but buy their proxy bandwidth. bytetourist is the egress network itself — and a Scrape API (markdown + structured extraction on top of your own fleet) is on the roadmap.