Per-IP pricing means you pay a fixed fee for each proxy IP, usually per month, often with unmetered traffic. For a side-by-side of other billing schemes (per port, per GB, pool access), see proxy pricing models and plan types.
How Per-IP Billing Works
Per-IP plans charge a recurring fee for each allocated address, commonly with unlimited bandwidth and a concurrency ceiling tied to the number of IPs you hold. You typically authenticate via username/password or IP allowlisting and keep the same IPs until you swap or the term ends.
Under the hood, providers assign you a list of IPs (datacenter or static ISP/static-residential). These IPs stay stable for long sessions, cookies, and device fingerprints. Some vendors offer dedicated (exclusive) access, while others sell shared access to lower the price. Swaps are handled by policy: a fixed number free per cycle, then paid per extra.
When Per-IP Fits Best
Per-IP fits when you need stable identity and long-lived sessions, not constant rotation. It is the default for datacenter proxies and a common option for static ISP or static-residential IPs.
Typical patterns include account-per-IP setups, store or page ownership per IP, or any workflow where frequent IP changes break trust and verification flows. Teams that parallelize many tasks at once also benefit because concurrency usually scales with IP count.
Advantages of Per-IP Plans
You get predictable costs and persistent identity that survives cookies and device fingerprints. Concurrency is straightforward to plan because it generally increases with your IP count.
Budgeting is simple (number of IPs multiplied by unit price), session stickiness is built in, and many providers include high or effectively unmetered throughput per IP. In larger teams, IP lists are easy to distribute across workers or containers.
Drawbacks and Trade-offs
You pay for every IP even when it sits idle, and bans persist until you swap or the term ends. Diversity is lower than a large rotating pool, so coverage across many subnets or cities may be limited.
Expect more list management work: tracking reputation, distributing load, and scheduling swaps. If you are weighing exclusive vs pooled access, read the comparison of private vs shared proxies for how exclusivity, pricing, and risk trade off in practice.
Typical Price Ranges
Market baselines look like this. Treat them as planning anchors; actual quotes vary by exclusivity, swap allowance, geo depth, and bundled support.
| Type | Typical unit price (monthly) |
| Datacenter, shared access (pooled) | ~$0.10 - $0.50 per shared IP |
| Datacenter, small dedicated volume | ~$2/IP |
| Datacenter, large dedicated volume | ~$1/IP |
| Static ISP or static residential | ~$2 - $5/IP |
Billing, Renewal, and Swaps
Most vendors bill monthly from the purchase date and renew automatically unless you cancel before the notice window. First cycles may be prorated when you add capacity mid-month.
Swap policies matter. Many plans include a limited number of free swaps per cycle; extra swaps are charged. Annual prepay sometimes unlocks discounts, but confirm how swaps and mid-term upgrades work on long commitments before you lock in.
Operating Per-IP Efficiently
Start with a small pack, verify success rates on your targets, then scale in batches. Distribute accounts evenly across IPs and run lightweight health checks to catch blocks early. Follow your provider’s documented usage limits so throughput or session caps do not create avoidable failures. If your steady workload fits Per-IP but peak bursts spike traffic, add a small per-GB pool for overflow.
Worked Example: 50 Static IPs
If you operate 50 accounts that each must keep a stable identity, 50 static ISP or static-residential IPs at ~$3 per IP cost roughly $150 per month. The bill does not swing with traffic, and you can plan concurrency by IP count.
With a per-GB model, cost moves with actual data transfer. That can be efficient for light or sporadic usage, but budgets become harder to predict when actions grow or when pages include heavy assets. Per-IP gives you a steady baseline for long-lived sessions; per-GB is better for highly bursty loads.
Pitfalls to Avoid
Oversizing is the most common mistake. Buy only what you will use in the next cycle and add capacity once performance is verified. Ensure the geo and city you need actually exist in stock, and confirm the swap fee for bad or blocked IPs. Understand the lock-in: discounts may require multi-month commitments that limit flexibility if your workload changes.
A quick checklist before you buy:
- Required geos and cities are available today.
- Swap allowance and paid swap price match your risk profile.
- Exclusivity, if needed, is clearly stated and verifiable.
- Concurrency and any soft bandwidth ceilings are documented.
- Cancellation and proration terms are clear if you add or reduce capacity mid-cycle.
FAQs
Do Per-IP plans really include unlimited bandwidth?
Often yes, but unlimited can still sit behind fair-use clauses. Check whether there are soft caps or concurrency ceilings that throttle you under load.
How many accounts can I run per IP?
There is no universal number. It depends on the target site’s tolerance and your behavior. Treat one stable account per IP as the safest baseline and add more only if your tests show it remains stable.
What if an IP gets blocked?
You usually keep paying for it until you use a swap. Many plans include a fixed number of free swaps; beyond that there is a fee. Read the swap rules before purchasing.
Can I mix Per-IP with Per-GB?
Yes. A common pattern is to keep long-lived sessions on Per-IP and route bursts or exploration traffic through a small Per-GB pool.
Are Per-IP plans dedicated or shared?
Both exist. Dedicated (exclusive) costs more and reduces cross-user risk. Shared lowers price but can carry reputation from other users.