New IP per request
Residential rotating
HTTP and SOCKS5 exits on residential networks, rotating on every connection or request.
$4.50 per GB · demo
Demo data. Not a live network, credential, or invoice.
HTTP(S) · SOCKS5 · sticky and rotating
Residential, mobile 4G/5G, ISP, and datacenter exits. Country, city, ASN, and carrier on the credential. Byte metering stays separate from billing.
Demo data. Not a live network, credential, or invoice.
New IP per request
HTTP and SOCKS5 exits on residential networks, rotating on every connection or request.
$4.50 per GB · demo
Hold an exit
Keep the same exit for a session window so a login or checkout stays on one address.
$6.00 per GB · demo
Carrier exits
Mobile-network exits with carrier targeting for flows that expect a handset ASN.
$8.50 per GB · demo
Long-lived addresses
ISP-assigned addresses meant to stay up, for accounts and allowlists that hate churn.
$2.40 per IP / mo · demo
Optional, fast
High-throughput datacenter pools when the target does not require a residential ASN.
$0.70 per GB · demo
Web Unlocker
Send a URL. The unlocker handles proxy selection, retries, and common anti-bot challenges.
$1.90 per 1k requests · demo
The gateway reads the username. Country, city, ASN, and carrier are parameters, not separate hosts.
Ad verification
Load creatives from the geos and carriers where the campaign is supposed to run.
Price and catalog checks
Compare public storefronts by city without pinning the job to one office IP.
SEO and SERP
Read public search results the way a local visitor would, then store the HTML.
QA and release
Exercise geo-gated storefronts, payment pages, and CDN behavior before launch.
Accounts, sub-users, and reseller margins are a tenancy concern. They do not live inside the session allocator or the byte counter.
No. Every figure, credential, and invoice in this site is labeled demo data. Nothing here charges a card or opens a real exit node.
You pass a session id and a time window on the proxy username. The session service pins that id to one exit until the window ends or the node drops.
The customer edge is HTTP(S) and SOCKS5. Supply nodes reach the pool through the node registration contract, typically a reverse tunnel. The gateway itself is not built in this repo yet.
Yes, as parameters on the credential. Availability depends on the pool. The locations page is a showcase of the targeting model, not a live inventory.
Supply products (Tuxly, HiveBand, SilentPipe, NodePayout SDK) live in other repositories. They will register nodes against the contract in docs/integrations. This site does not operate those apps.
The tenancy model reserves accounts, sub-users, and reseller margins. White-label hostnames are a Scale-plan concept in the demo, not a provisioned product yet.