Proxy Pricing Models Explained: GB, Speed, Time, and Unmetered Plans

Proxy pricing models decide whether you pay for traffic, speed, time, or fixed capacity, and the right unit is the one that lowers your cost per successful request. This guide maps each model to the workload it actually fits, so a price card stops being a guessing game.

The confusing part is that providers reuse the same words to mean different things. One page sells residential proxies by the gigabyte. Another sells datacenter proxies by IP count. A third advertises an "unmetered" plan that still has a speed ceiling. So the number in the headline rarely answers the question you actually have: what will this cost once the workflow runs at normal volume, every day?

Key takeaways

• GB-based pricing fits lighter or easy-to-forecast traffic where you want tight spend control before scaling.
• Unmetered and speed-tier pricing fit steady workloads where watching every gigabyte becomes friction.
• Time-based billing (hourly, daily, weekly, monthly) controls the cost of short tests and temporary jobs.
• Per-IP, per-port, and per-request models exist across the market, but they answer the same buyer question: what unit am I paying for, and what limit is attached to it?
• The best model is the one that lowers your cost per successful request without removing the location, protocol, session, or support controls your workflow needs.

ColdProxy keeps this comparison cleaner by publishing a pricing hub for four live proxy families. The trick is to read each plan by billing unit, coverage, session control, and speed tier, not just by the lowest number on the card.

The short answer: match the price unit to the shape of your workload

A proxy pricing model is the unit a provider uses to charge for access. For you, the unit matters because it changes which behavior gets expensive. A job with small responses but many target locations behaves nothing like a job that downloads heavy pages all day. A one-off QA check behaves nothing like a crawler that runs every morning.

Run this matrix before you compare a single plan card:

• Choose GB-based pricing when total traffic is predictable, jobs are intermittent, or you want a hard ceiling on spend before scaling.
• Choose unmetered or speed-tier pricing when the workflow runs often enough that traffic metering becomes a daily distraction.
• Choose a short time window when you need to validate a target, test a setup, run a temporary QA pass, or prove a small workload before committing longer.
• Choose per-IP or per-port pricing only when a product is sold that way and stable allocation matters more than traffic volume.
• Choose per-request API pricing when you are buying a finished result from a scraping or SERP API rather than running proxy infrastructure yourself.

The main proxy pricing models

1. GB-based pricing

GB-based pricing bills by the traffic that flows through the proxy. It is common in residential proxy markets because volume is a simple way to meter usage that varies week to week. Public pricing pages from Bright Data, Oxylabs, and Decodo all show how common per-GB residential plans are.

The upside is control. You start small, forecast spend, and never pay for capacity you do not use. The tradeoff: heavy pages, retries, images, redirects, and large responses can drain a pack much faster than a raw request count suggests. A "1,000 requests" estimate means little if each page pulls a megabyte of assets.

ColdProxy maps this model to Premium Residential Geo Target IPv4 (GB Based), which uses monthly traffic packs starting at $1.27/month for a 1 GB pack. You get the full Residential IPv4 targeting set — Country, State, City, ZIP, and ASN — with HTTP, HTTPS, and SOCKS5, TCP and UDP transport, User:Pass or IP Auth, and rotating or sticky sessions configurable from 5 seconds up to 24 hours. Reach for it when the job is light, easy to forecast, or still being proven out.

2. Unmetered residential IPv4 on a speed tier

"Unmetered" removes the per-GB counter, but it does not mean unlimited speed. The cleaner way to read it: you are not billed by the gigabyte, but you still pick the speed tier that fits the workflow. Throughput is shaped by that tier, not uncapped.

ColdProxy uses this pattern for Premium Residential Geo Target IPv4 (Unmetered). The plan is built around Mbps speed tiers starting at $106.24/month on the 5 Mbps tier, with no per-GB quota as a clarifier rather than the headline. It carries the same Residential IPv4 coverage as the GB plan — the two differ only in billing, not coverage — across 195+ countries drawn from a 70M+ global Residential IPv4 pool, with HTTP, HTTPS, and SOCKS5, TCP and UDP, User:Pass or IP Auth, and rotating or sticky sessions from 5 seconds to 24 hours. Buying is available hourly, daily, weekly, or monthly.

This is usually the better fit once the same residential workflow runs every day, once GB tracking becomes operational friction, or once several teams share one plan. A common path: an ecommerce team starts with GB-based checks for a few markets, then moves to unmetered Residential IPv4 once price monitoring becomes a daily habit and counting gigabytes stops being worth anyone's time.

3. Speed-tier IPv6 pricing

Speed-tier pricing is similar in spirit to the unmetered model — the plan is shaped by throughput, not traffic volume. It is common when the buyer cares about predictable capacity for automation, monitoring, or API-style workloads.

ColdProxy applies speed-tier pricing to Residential IPv6 and Datacenter IPv6, and the two are genuinely different products:

• Residential IPv6 delivers USA residential IPv6 routes (think a city cue like "USA - Ashburn"), an included /32 IPv6 subnet, sticky sessions from 5 seconds to FOREVER or rotating, HTTP/HTTPS/SOCKS5, TCP/UDP, User:Pass or IP Auth with up to 50 whitelisted IPs, 1 to 5,000 ports, and CDN-aware IPv6 reachability for supported CDN-fronted domains. Buying runs hourly through monthly. Choose it when the target is IPv6-ready and you specifically want USA residential routes.
• Datacenter IPv6 gives you all supported Datacenter IPv6 locations in a single order — a real metro list including US cities plus Toronto, London, Frankfurt, Amsterdam, Paris, Tokyo, Singapore, Sydney, and more — with one private /48 subnet per supported location, the same 5-seconds-to-FOREVER sticky-or-rotating model, and CDN-aware IPv6 reachability. Buying runs daily through monthly. Choose it when speed, broad metro coverage in one order, and private /48 allocation matter more than residential reputation.

A quick note on the IPv6 reachability feature: when a supported CDN edge answers over IPv6 but a customer domain has no published AAAA record, ColdProxy can land the connection on the CDN's real IPv6 edge. It stays ordinary IPv6 traffic — not IPv4 fallback, NAT64, or tunneling.

4. Time-based billing windows

Time-based billing is plan duration: hourly, daily, weekly, or monthly. It is not a separate proxy type, but it has the biggest effect on test cost. A short window lets you validate targeting, protocol support, session behavior, and target compatibility before committing to a longer plan.

ColdProxy publishes hourly-through-monthly windows for the unmetered Residential IPv4 and Residential IPv6 plans, monthly-only buying for the GB-based Residential IPv4 plan, and daily-through-monthly windows for Datacenter IPv6. There is no free trial, so the shortest public billing window for a plan is your supported live-test path — and the free proxy checker and what's-my-IP tools are diagnostics, not a trial.

5. Per-IP, per-port, and per-request pricing

These show up across the wider market but are not how ColdProxy frames its four current public families. Per-IP or per-port pricing makes sense when you rent fixed allocation and stability matters more than volume. Per-request pricing fits APIs that bill for completed results instead of raw proxy access. Guides such as DataResearchTools and ProxyHat cover these broader units — which is exactly why so many buyers arrive confused.

If you are weighing those models against ColdProxy, translate every one of them into the same three questions: what unit am I paying for, what limit is attached, and what happens when the job scales?

How ColdProxy plans map to the pricing models

The product name alone does not tell you the billing risk — Residential IPv4 can be GB-based or unmetered, and IPv6 can be residential or datacenter. Here is the current map:

• Premium Residential Geo Target IPv4 (Unmetered): speed-tier Residential IPv4 with no per-GB quota, 195+ country coverage, HTTP/HTTPS/SOCKS5, TCP/UDP, User:Pass or IP Auth, and sticky or rotating sessions from 5 seconds to 24 hours. Hourly, daily, weekly, and monthly buying.
• Premium Residential Geo Target IPv4 (GB Based): monthly traffic packs over the same broad Residential IPv4 targeting — Country, State, City, ZIP, ASN — with HTTP/HTTPS/SOCKS5, TCP/UDP, User:Pass or IP Auth, and sticky or rotating sessions from 5 seconds to 24 hours.
• Residential IPv6: speed-tier USA residential IPv6 routes with an included /32 subnet, sticky sessions from 5 seconds to FOREVER or rotating, HTTP/HTTPS/SOCKS5, TCP/UDP, up to 50 whitelisted IPs, and CDN-aware IPv6 reachability. Hourly, daily, weekly, and monthly buying.
• Datacenter IPv6: speed-tier Datacenter IPv6 across all supported metros in one order, a private /48 per location, sticky sessions from 5 seconds to FOREVER or rotating, HTTP/HTTPS/SOCKS5, TCP/UDP, up to 50 whitelisted IPs, and daily, weekly, or monthly buying.

A short billing period lowers the cost of testing, but it never replaces confirming that your target actually supports the protocol, location, and session behavior you plan to use.

Across all four, ColdProxy publishes a ~99.9% success rate and up to 0.6s response time as its reliability proof.

Choose by workload pattern, not by sticker price

When traffic volume is unknown

Start with the model that limits the downside. For Residential IPv4, that usually means a GB-based monthly pack while you estimate page weight, retry rate, location mix, and session behavior. If the job stays small, GB pricing can remain the cleaner model. If it grows into daily operations, unmetered Residential IPv4 removes the metering overhead.

When the job is steady and heavy

Look at unmetered or speed-tier plans. A product-data pipeline, a recurring market monitor, or a high-volume QA system gets awkward under GB tracking because every retry and rich page carries a cost implication. Here, compare the speed tier, not just the entry price.

When the target is IPv6-ready

Do not buy IPv6 just because it exists. First confirm the target resolves and responds over IPv6. Then pick Residential IPv6 for USA residential routes, or Datacenter IPv6 when broad metro coverage in one order and speed-first infrastructure fit better. This is where ColdProxy's plan boundaries matter: Residential IPv6 is USA-only, while Datacenter IPv6 ships its full supported metro list in a single order. For IPv4-only targets, a Residential IPv4 plan is the safer starting point.

When you are testing a provider

Use the shortest public billing window for the plan and test the real workflow: authentication, target location, sticky duration, protocol, transport, success rate, and support response. For ColdProxy that means hourly where the plan supports it, daily where it does not, and monthly for the GB-based Residential IPv4 plan. You can confirm exit IP and location with the public echo endpoints — https://api.vipv6proxy.com/api/checker/my-ip for IPv4 and https://api6.vipv6proxy.com/api/checker/my-ip for IPv6 — instead of a third-party service.

And before any public-data collection: review the target site's terms, respect robots and rate-limit expectations, and check the data-protection laws that apply to you. A good price never makes an unsafe workflow acceptable.

A quick word on what these numbers don't cover

Proxy pricing moves often, especially discounts, coupons, and entry prices, so treat this as a model-selection guide and open the live pricing pages for the current number before buying. No single model is universally cheaper, either: a GB pack can beat an unmetered plan for a small job, and an unmetered speed tier can beat GB billing for a continuous one. Residential IPv6 and Datacenter IPv6 only make sense when your target path supports IPv6 well enough for the workflow — otherwise a Residential IPv4 plan is the dependable default.

Frequently Asked Questions

What is the best proxy pricing model?

There is no universal best. GB-based pricing wins when traffic is predictable or light. Unmetered and speed-tier pricing win when the same workload runs often enough that metering becomes operational friction. Time-based windows win for short tests and temporary jobs. Match the unit to the job and the cost follows.

Is unmetered proxy pricing the same as unlimited speed?

No. Unmetered means the plan is not billed by transferred gigabytes — it can still have a speed, port, or capacity limit. ColdProxy's unmetered Residential IPv4 is built on Mbps speed tiers, so "no per-GB quota" describes the billing, while throughput depends on the speed tier you select. It starts at $106.24/month on the 5 Mbps tier.

Which ColdProxy plan is GB-based?

Premium Residential Geo Target IPv4 (GB Based) is the GB plan, built around monthly traffic packs from $1.27/month for a 1 GB pack. It keeps the same broad Residential IPv4 targeting and session controls as the unmetered Residential IPv4 plan; only the billing is tied to traffic volume.

Does ColdProxy offer hourly proxy plans?

Yes, for the plans that support hourly buying. The pricing hub shows hourly through monthly windows for Premium Residential Geo Target IPv4 (Unmetered) and Residential IPv6. Datacenter IPv6 starts at daily windows, and the GB-based Residential IPv4 plan is monthly. Because there is no free trial, the shortest public window is the live-test path.

Should I choose residential or datacenter proxies to control cost?

Choose by workload fit first. Residential proxies are usually the better call when residential reputation and geo-targeting matter. Datacenter proxies are usually better when speed, infrastructure predictability, and broad metro coverage matter more. Cost control comes from matching the billing unit to the real job, not from assuming one proxy type is always cheaper.

A better way to compare proxy prices

The next step is not to hunt for the lowest sticker. Build a small workload estimate, pick the billing model that matches it, then test the controls that actually decide success: location, protocol, authentication, sticky duration, and target compatibility. Once you know the shape of your workflow, the pricing page reads itself.

Start with the ColdProxy pricing hub to compare all four current plan families side by side, then open the proxy product page that matches your billing model and workload. If a public plan does not fit, ColdProxy can shape a tailored option around your speed, traffic, or deployment needs.