Pricing

Prepaid balance, usage-based metering. No subscriptions, no monthly minimums.

Rotating traffic
Per-GB rates by pool type. Billed on actual bytes transferred — including failed requests. Temporary sticky sessions are free.
Pool typePrice
Residential$3.00 / GB
Datacenter$1.20 / GB
Mobile$6.00 / GB

Tiered top-up discounts

Larger top-ups earn bonus credit on your prepaid balance: $50+ → +5% · $200+ → +10% · $500+ → +15%. Bonus credit is spendable on any product and never expires.

Static identity (Persona)
Dedicated egress with a persistent IP, session and geography. Occupancy fee by region (accrued daily from your balance) plus traffic at rotating rates. Temporary sticky sessions don't need a Persona and are free.
RegionOccupancy
Japan$5.00 / IP·month
United States$4.50 / IP·month
Hong Kong$5.50 / IP·month
Singapore$5.00 / IP·month
United Kingdom$4.50 / IP·month
  • Dedicated exit — never shared with another customer
  • Occupancy accrues daily, stop anytime
  • 5 regions at launch; sold-out regions show as restocking
  • Health monitoring with migration alerts
Prepaid balance — no subscriptions

You do exactly one thing: top up a prepaid balance (one-click amounts or custom, via Stripe — Alipay and WeChat Pay supported). Every charge — rotating traffic and Persona occupancy — is deducted from that balance.

There is no monthly plan, no auto-renewing card charge, and no minimum commitment. Persona occupancy accrues daily rather than billing monthly up front. When your agents stop, charges stop. An optional auto-top-up can refill your balance below a threshold you set — still prepaid, never a subscription.

Billing FAQ

Do Personas cost money?

Persistent Personas carry an occupancy fee (per IP per month, priced by region and accrued daily from your prepaid balance) plus traffic at rotating rates. Temporary sticky sessions — minutes-to-hours reuse of a rotating exit — are free: you only pay for the traffic.

Are failed requests billed?

Gateway (direct proxy) traffic is billed on actual bytes transferred, including failed requests — the bytes still cross the network.

How do budget caps work?

Per-key budgets are enforced in the request path with real-time pre-deduction — not by after-the-fact reconciliation. Long-lived tunnels are metered in 8 MB slices, so a connection can be cut mid-stream within one slice of hitting your cap.

Start with a small top-up. Stop anytime.

Get your free API key