Fastest and cheapest
decentralizeddistributed HQ residential proxy network.
What to run a node? Go to our website or Turbo Client Node
- Self-sourced IPs and node connection quality analysis for highest success rate
- All the standart proxy features:
- Redis Auth & PUB/SUB (Credits, Stream for abnormal traffic detection model)
- Skip-hop option (requires port forwarding and SDK use): dynamically connect to the end nodes for extremely low latency and TTFB (up to <20ms)
flowchart TD
User(User)
subgraph Self-hosted [Self-hosted backend]
ProxyServer[Proxy Server]
Redis[(Redis Database & Streams)]
AI[AI Traffic Analysis]
end
%% subgraph Zero-Trust Zone
ClientNode[Client Node]
NodeRunner(Node Runner)
%% end
PaymentGateway[Payment Gateway]
Blockchain[(Crypto Blockchain)]
TargetWebsite[Target Website]
Website[Next.js Website]
Supabase[(Supabase PostgreSQL)]
User --> |Sends HTTP/S or SOCKS5 Requests| ProxyServer
User --> |Buys Credits| PaymentGateway
ProxyServer --> |Node data update| Supabase
ProxyServer <--> |TLS-encrypted QUIC Messaging| ClientNode
ProxyServer --> |Uses for Auth & Credits| Redis
AI --> |Evaluates server connections| Redis
ClientNode --> |Processes Requests To| TargetWebsite
NodeRunner --> |Operates| ClientNode
PaymentGateway --> |Processes Payments| Blockchain
PaymentGateway --> |Updates Credits In| Redis
Blockchain --> |Sends Rewards| NodeRunner
Website --> |Provides Data| NodeRunner
Supabase <--> |Realtime stream| Website
Your node score
-
$L$ : Latency, capped on a range from 10ms to 500ms -
$R$ : Reliability -
$U$ : Uptime, measured over a 30-days rolling period
Where, by default,
The magic is that you can tailor the weights to your needs, for example if you want to prioritize reliability over latency, you can request like so:
curl -x "socks5h://reliability=70%,uptime=12%,country=US:API-KEY@turbonodes.net" https://httpbin.org/ip
You're free to operate your own server for commercial use according to the Apache 2.0 license.
Run server docker image with docker-compose up and connect client nodes.
For more information, see Setting Up Development Environment
See Global Architecture for a high-level overview of the system.
sequenceDiagram
participant SOCKS5_Client as User
participant Proxy_Server as Server
participant Proxy_Client as Node
participant Internet as Internet
SOCKS5_Client->>Proxy_Server: 1. SOCKS5/HTTP CONNECT request
Proxy_Server->>Proxy_Client: 2. Forward dest. IP + TLS-encrypted payload via QUIC
Proxy_Client->>Internet: 3. Process request (TCP level)
Internet-->>Proxy_Client: 4. Return encrypted response
Proxy_Client-->>Proxy_Server: 5. Send data via QUIC
Proxy_Server-->>SOCKS5_Client: 6. Send back to SOCKS5 Client
Networks of this type always raise security and ethical concerns. Most providers (including major actors such as Bright Data, Oxylabs, ...) spy the content of your communication with the website, and can even inject malicious content into the traffic.
We are the only providers that systematically block any pure HTTP request and strictly enforce user-terminated TLS encryption
That way, only the proxy user and the target website can decrypt the traffic. Our aforementioned zero-trust policy ensures that client nodes cryptographically cannot see the packets' payload.
This architecture mitigates MITM threats and reliably certifies that the data returned to the proxy user is the data sent by the target website.
Want to buy proxy access from our network for web-scraping, browser agents?
Join our Discord server for more information: Create a ticket or DM @lished. You can also reach us via email