Proxy pricing: calculate the real cost before you buy

The four proxy pricing units

This page contains affiliate links. We may earn a commission if you buy through them, at no extra cost to you. We deliberately avoid quoting live prices because packages, discounts, locations and inventory change.

Pricing basis	What you are buying	The variable that drives cost	Typical fit
Per GB	Traffic through a rotating pool	Response size, uploads, retries and assets	Rotating residential or mobile
Per IP and term	A fixed number of endpoints for a period	Concurrent stable identities and duration	Static residential or datacenter IPv4
Per package and term	A defined allocation, often of many addresses	Required package size and compatibility	Datacenter IPv6
Per successful result	A managed extraction outcome	Request difficulty and completion rules	Scraping APIs, not the raw Proxy-Cheap products compared here

Do not compare $ per GB with $ per IP directly. They measure different resources. Convert each candidate into estimated total cost for the same workload.

Proxy-Cheap’s checkout integration documentation exposes the distinction clearly. Rotating residential orders take a bandwidth input. Static residential orders take quantity and rental period plus current location or ISP options. Datacenter IPv4 uses country, quantity and period; datacenter IPv6 uses country, package and period. The company also warns that those options and prices can change.

How per-GB proxy pricing works

Bandwidth billing counts data transferred through the proxy. Proxy-Cheap’s rotating residential setup guide explicitly says that both uploads and downloads are included. The expensive variable is therefore not “number of URLs” in isolation.

Use this first estimate:

monthly GB = requests × average transfer per request × retry factor ÷ bytes per GB

For example, your inputs might be 100,000 permitted requests, an average measured transfer of 150 KB and a retry factor of 1.15. Measure those inputs from a pilot; do not borrow them from someone else’s crawler. Include redirects, API payloads, browser assets and uploads that actually cross the proxy.

Then calculate:

estimated plan cost = required GB × current checkout rate

We do not fill in the current rate here. Open the live offer after you have the required GB, choose the closest suitable package and record the final total before tax or currency conversion.

Proxy-Cheap rotating residential proxies

This is Proxy-Cheap’s traffic-priced residential option for workloads that benefit from a changing exit IP. The official service page says it supports HTTP and SOCKS5, country and city targeting, random rotation and sticky sessions. Treat pool size, location coverage and prices as changeable merchant claims: verify the current plan in the dashboard before buying.

Best fit: distributed public-web collection and location-aware checks where IP rotation is useful. Watch-out: a stable login or long-running identity may fit a static service better.

Check the live offer

What quietly inflates bandwidth cost

• Loading unnecessary assets: images, video, fonts and advertising can dwarf the HTML.
• Browser rendering: a full browser often transfers more than a direct HTTP client.
• Retries without limits: a failing target can consume traffic without producing usable records.
• Oversized responses: requesting full documents when a smaller endpoint exists wastes transfer.
• Uploads: form bodies and API payloads also cross the proxy.

Optimise the permitted workflow before buying more GB. Block resources you do not need, cache stable responses, compress where supported and cap retries. This is engineering work with a direct commercial return.

How per-IP pricing works

Per-IP plans charge for endpoint quantity across a rental period. The primary question is not how many total tasks you run; it is how many simultaneous stable identities the system requires.

Start with:

required IPs = peak simultaneous stable sessions + tested replacement margin

Then:

term cost = required IPs × current price per IP for the required period

Avoid inventing a generous replacement margin. Pilot a small allocation, measure actual endpoint failures or incompatibility, and set the margin from evidence. If sessions can run sequentially through the same authorised endpoint, concurrency may be far lower than task count.

Proxy-Cheap’s static residential product is one example of this model. The merchant documents a dedicated, consistent ISP-associated address with current location and ISP choices. Its live checkout controls the available tier and term.

Proxy-Cheap static residential proxies

Proxy-Cheap positions this as a fixed ISP-address option for tasks that need the same exit IP over time. Its official page lists HTTP and SOCKS5 support, dedicated addresses, location targeting and bandwidth sold with the individual proxy rather than metered residential traffic. Confirm the available ISP, country and term in the merchant dashboard because inventory changes.

Best fit: persistent sessions and repeat access from one expected address. Watch-out: paying for a dedicated static address can be poor value for short, highly distributed jobs.

Check the live offer

Datacenter IPv4 also uses quantity and term in Proxy-Cheap’s documented checkout parameters. It can be the leaner route when a server-hosted address works for the target and residential provenance is not required.

Proxy-Cheap datacenter IPv4 proxies

This is the conventional server-hosted IPv4 option in Proxy-Cheap’s range. It is sold per address and is intended for buyers who value predictable endpoints and economical throughput more than residential network provenance. The service page is the source of truth for current countries, term lengths, authentication and protocol support.

Because the address comes from datacenter infrastructure, verify it against the intended public target before scaling; compatibility matters more than the low unit price.

Best fit: compatible high-volume tools, testing and collection from public pages. Watch-out: some destinations treat datacenter ranges more strictly than residential or ISP traffic.

Check the live offer

Package pricing and the IPv6 trap

Datacenter IPv6 may be sold in package sizes rather than a freely chosen individual quantity. The low apparent unit cost can be attractive, but only if the entire path supports IPv6: your application, proxy client and destination.

Proxy-Cheap tells buyers to use a package size and location currently displayed in checkout. Do not hard-code an old package into a purchasing model. More importantly, test the real destination. A successful connection to an IPv6 checker says nothing about an IPv4-only target.

Proxy-Cheap datacenter IPv6 proxies

Proxy-Cheap’s IPv6 datacenter service is the lowest-friction option only when the target and client both support IPv6 properly. The service is sold per address, but a low unit price is irrelevant if the destination is IPv4-only or your software cannot use the supplied format. Verify compatibility before purchasing a larger allocation.

Best fit: IPv6-capable tools and destinations where address scale matters. Watch-out: IPv6 support is still uneven across websites and software.

Check the live offer

The relevant metric is not addresses per dollar. It is usable, compatible capacity per dollar. An enormous IPv6 allocation has zero economic value for a job that cannot reach its destination.

Calculate cost per completed job

The cleanest comparison normalises every plan to the same output:

cost per completed job = (plan cost + variable fees + operator cost) ÷ completed jobs

Include these inputs:

• Plan cost: the actual checkout total for the required package and term.
• Variable fees: overages, speed upgrades or other selected extras shown before purchase.
• Infrastructure: browser workers, servers, storage and monitoring needed to use the proxy.
• Retries: traffic and compute spent on work that had to be repeated.
• Operator time: setup, replacement, support and incident handling.
• Completed jobs: outputs that pass your validation, not merely HTTP 200 responses.

This exposes false economies. A plan can have the lowest unit price and the highest completed-job cost if it creates more failures or manual work. The opposite can also happen: an apparently expensive address can be economical when it preserves a valuable authorised session and removes repeated recovery.

A simple pricing worksheet

For a bandwidth plan

1. Measure average upload plus download per successful task.
2. Measure retries and calculate a real retry factor.
3. Forecast monthly task volume.
4. Add a modest, explicit growth margin.
5. Match the resulting GB to the current package.
6. Divide the full checkout total by forecast completed tasks.

For an endpoint plan

1. Count peak simultaneous stable sessions.
2. Confirm the required country, ISP and IP version.
3. Measure whether endpoints can be reused sequentially.
4. Add a replacement margin supported by the pilot.
5. Choose the shortest term that covers the validated need.
6. Divide full cost by completed tasks or supported sessions.

Put both results in one spreadsheet with the same currency, tax treatment and time period. If you cannot normalise the units, you do not yet have a comparison.

Pick the type before optimising the price

A cheaper billing model cannot rescue a technically wrong product. Make these decisions in order:

1. Network source: residential, datacenter or mobile.
2. IP version: IPv4 for broad compatibility or IPv6 after validation.
3. Session behaviour: rotating, sticky or static.
4. Geography: country, region, city or ISP as the task requires.
5. Protocol: confirm the application and product share a supported method.
6. Billing unit: only now compare GB, address or package economics.

Our residential vs datacenter proxies guide resolves the first choice, while the session requirement resolves whether rotation or a static address is appropriate. Skipping those decisions is how buyers end up optimising a price for a product that cannot do the job.

Why we do not publish a “cheapest proxy” table

Current price tables age quickly. Promotional discounts end, inventory changes, packages are renamed and one country or ISP can cost differently from another. Proxy-Cheap’s own help documentation says the live order form is the source of truth for product availability and pricing.

There is a second problem: a cheapest-provider table usually compares unlike units. A tiny traffic allowance, one shared endpoint and an IPv6 package can each produce an impressively small headline number. None answers whether the allocation fits your workload.

We would rather give you a reproducible model. Record the checkout total and date in your worksheet, rerun it before renewal and keep the workload assumptions beside it.

Trial and scale rule

Start with the smallest allocation that can produce a meaningful test. Define the pass condition before purchase:

• the workflow reaches the required authorised target;
• the session survives for the required period;
• the location and protocol match;
• completed-job cost stays below your ceiling;
• manual intervention remains acceptable.

Scale only when the pilot passes. If it fails on compatibility, change product type. If it fails on bandwidth, reduce transfer or change billing model. If it fails on operational time, improve automation or price that labour honestly.

Limitations

We have not tested Proxy-Cheap throughput, latency, uptime or target success, and we do not publish live price claims in this guide. Product facts come from official service and help-centre pages verified on October 1, 2026. Checkout remains the current authority for package size, availability, terms and final price.

Your measured traffic and success criteria matter more than a generic example. Currency conversion, tax and payment fees may also affect the final budget.

Frequently asked questions

How much do proxies cost?

There is no useful single number. Rotating pools may be billed by GB, while static and datacenter products may be billed by address quantity and term. Define the product, location, IP version, session model and volume, then check live checkout.

Is price per GB the best comparison?

Only between plans that satisfy the same technical requirement. Add retries, uploads and operational work, then calculate cost per completed task. A low per-GB rate can still be poor value if the exit type is wrong.

Are unlimited-bandwidth proxies always cheaper?

No. A fixed endpoint with generous traffic can be good value for a stable, compatible workflow, but it may not supply the rotating pool or geographic breadth you need. “Unlimited” also does not mean unlimited speed, concurrency or acceptable use.

Should I pay monthly or choose a longer term?

Use the shortest term that validates the workload. A longer discount only saves money if the configuration remains useful for the entire period. Check cancellation, renewal and refund terms before committing.

What is the cheapest sensible starting point?

The smallest plan that can test the real workflow and produce enough completed tasks to measure cost. Do not buy a large block merely because the unit rate falls. Turn the selected plan into a controlled pilot before you scale it.