What a bundle includes
| Component | Typical role |
|---|---|
| Residential traffic | Crawlers, verification sweeps, research |
| Per-IP SOCKS5 | Profiles and identity-bound automation |
| Static ISP | Accounts that must never change address |
| API access | Programmatic endpoint and sub-account creation |
Sizing a first bundle
Start from the identity count, not the traffic estimate: one IP per profile, plus enough gigabytes to cover the crawl. Top-ups are always possible at the same rate, so there is no advantage to over-buying. Code IPD30 applies 30% off a first order.
Why bundling lowers cost
Buying products separately means paying entry pricing three times. A bundle applies volume pricing across the whole order, and because balances do not expire the unused portion is not wasted when a project pauses.
Frequently asked questions
Can I split a bundle across products?
Yes. One balance funds residential traffic, per-IP SOCKS5 and static ISP, and you decide the split as the project runs.
Do bundle balances expire?
No. Unused traffic and IPs stay on the account indefinitely.
Is a bundle cheaper than buying separately?
Yes — volume pricing is applied across the whole order rather than to each product's entry tier.
Can I top up later?
Yes, at any time and at the same rates. Top-ups merge into the existing balance.