What is it
Per-IP pricing is a billing unit where each reserved proxy IP address is metered on allocation, not traffic — used by web-scraping and proxy providers.
In the proxy market an IP address is infrastructure, not just a routing detail. A static, dedicated IP serves cases a rotating pool cannot: cookie-persistent crawling where the same IP must appear across a multi-page session, account management where a site ties behavior to IP history, and ISP-grade deliverability where residential-quality IPs stay stable. Per-IP pricing encodes exactly that stable identity into a flat monthly rate per address.
Bright Data and Oxylabs both run this meter as a secondary line: most customers buy per-GB residential plans and add static IPs where a project needs them. To size the alternative meter, see the introduction to usage-based pricing.
How it works
A reserved IP is exclusive to one customer, so it carries a fixed cost the provider cannot recoup by reselling the address — that is why the fee is per allocation rather than per byte. The unit rate falls as the reserved block grows, reflecting bulk-provisioning efficiency.
| Company | IP product | Per-IP price (real, captured 2026-06-04) |
|---|---|---|
| Bright Data | ISP (static residential) proxies | $1.8/IP at 10 IPs → $1.3/IP at 1,000 IPs |
| Bright Data | Datacenter proxies | $1.40/IP at 10 IPs → $0.90/IP at 1,000 IPs |
| Oxylabs | ISP proxies | from $1.60/IP ($16/mo for 10 IPs) |
| Oxylabs | Dedicated datacenter proxies | from $2.25/IP |
| Oxylabs | Shared datacenter proxies | from $1.20/IP (or $0.59/GB) |
The unit math for per-IP pricing:
Monthly IP cost = number_of_dedicated_IPs × monthly_rate_per_IP
Worked example: 100 Bright Data ISP IPs bill at $1.45/IP (the 100-IP tier) → $145/mo, regardless of how much bandwidth flows through them. The same 100 IPs on Bright Data’s datacenter line price at $1.0/IP → $100/mo. Because the fee is per allocation, a light-traffic project running 100 static IPs pays that flat amount whether it moves 1 GB or 100 GB.
A proxy bill therefore has two independent drivers: how much data moves and how many exclusive identities are held. The Oxylabs split is explicit — residential and mobile proxies bill per GB (from $6/GB and $7.50/GB) while ISP, datacenter and dedicated-datacenter proxies bill per IP. Picking which meter fits your workload is the core decision in choosing the right usage metric.
Companies using this
Two companies in the corpus meter proxy IP addresses as a billing dimension: Bright Data, which prices ISP and datacenter proxies per reserved IP alongside its per-GB residential line, and Oxylabs, which bills ISP, datacenter and dedicated-datacenter proxies per IP. Both pair per-IP allocation with bandwidth-based billing to cover static and dedicated IP use cases.
| Company | Product | Pricing model | Billing units | Free tier | Verified |
|---|---|---|---|---|---|
| Bright Data | Web data platform — proxy networks, scraping APIs, a managed scraping browser, SERP and unlocker APIs, ready-made datasets, and eCommerce insights | Yes | 2026-07-23 | ||
| Oxylabs | Web data collection: residential, datacenter, ISP & mobile proxies plus Web Scraper API and Web Unblocker | Yes | 2026-08-04 |
Explore this theme in the knowledge graph
FAQ
What is per-IP pricing in web scraping and proxy services?
Per-IP pricing meters the number of static or dedicated proxy IP addresses allocated to an account, rather than the data volume flowing through them. Bright Data bills ISP proxies from $1.8/IP down to $1.3/IP and datacenter proxies from $1.40/IP down to $0.90/IP across 10–1,000 IP tiers; Oxylabs bills ISP proxies from $1.60/IP and dedicated datacenter proxies from $2.25/IP. Each reserved IP is a stable, exclusive identity that persists across a scraping session.
How does per-IP pricing differ from per-GB bandwidth pricing in proxy services?
Per-IP and per-GB are two different value metrics the same vendor runs side by side. Bandwidth (per-GB) meters how much data moves; per-IP meters how many exclusive identities you hold. Bright Data and Oxylabs both bill rotating residential proxies per GB (Bright Data $8→$2.50/GB, Oxylabs from $6/GB) while billing ISP and datacenter proxies per IP — the meter follows the product's cost driver, not the customer's choice.
Which companies use per-IP pricing?
In the UsagePricing corpus, Bright Data and Oxylabs both meter proxy IP allocation as a billing dimension. Both are web-data collection platforms that sell static IP products (ISP and datacenter proxies) priced per reserved IP per month, alongside their per-GB residential proxy lines.
Why do dedicated IPs cost a flat monthly fee instead of per-usage?
A dedicated IP is reserved for one customer's exclusive use, so it carries a fixed cost whether or not it is heavily used — the provider cannot resell that address simultaneously. Bright Data's datacenter IPs run $1.40/IP at 10 IPs and Oxylabs' ISP proxies start at $1.60/IP ($16/mo for 10), charged by allocation, not utilization.
Related billing units
- Credit-Based BillingA billing unit where customers pre-purchase or are allocated a pool of credits that deplete as they use the product, often at variable rates per feature.
- Token-Based PricingA billing unit common in LLM and AI products, where customers are charged per input and output token processed.
- Per-Seat PricingA billing unit where the vendor charges a fixed fee per named user, regardless of how much each user consumes.
- Per-Resolution PricingA billing unit unique to AI customer-support products, where the vendor charges only when an AI agent resolves a customer issue without escalation.
- Bandwidth-Based PricingA billing unit where customers are charged per gigabyte of data transferred out of the platform.
- Per-Function-Invocation PricingA billing unit where customers are charged per serverless function invocation, often combined with a separate compute-time charge.
- CPU-Hour PricingA billing unit where customers are charged for the CPU time their workloads consume, typically measured in vCPU-seconds or vCPU-hours.
- GB-Hour PricingA billing unit where customers are charged for the memory their workloads consume over time, measured in gigabyte-hours.
- GPU-Hour PricingA billing unit where customers are charged for GPU time consumed, typically measured per-second or per-hour by GPU type.
- Per-API-Call PricingA billing unit where customers are charged per API request, regardless of payload size or processing time.
- Per-GB Storage PricingA billing unit where customers are charged per gigabyte of data stored on the platform per month.
- Media-Minute PricingA billing unit where customers are charged per minute of audio or video processed — used by speech, voice, and video AI vendors.
- Per-Request PricingA billing unit where customers are charged per request served — the generic meter for inference endpoints, search, scraping, and browser infrastructure.
- Per-Event PricingA billing unit where customers are charged per event ingested — the native meter of observability and billing-infrastructure platforms.
- Vector Storage PricingA billing unit where customers are charged for vectors stored or indexed — the storage dimension of vector database pricing.
- Per-Character PricingA billing unit where customers are charged per character of text processed — the standard meter for text-to-speech and translation.
- Per-Document PricingA billing unit where customers are charged per document processed or generated — common in AI writing, SEO, and document-intelligence tools.
- Per-Page PricingA billing unit where customers are charged per page crawled, parsed, or rendered — the meter for web scraping and document parsing.
- Per-Transaction PricingA billing unit where customers are charged per financial or billing transaction processed — the meter of billing and accounting platforms.
- Active-User PricingA billing unit where customers are charged per monthly or daily active user rather than per provisioned seat.
- Per-Task PricingA billing unit where customers are charged per task an automation or agent executes — Zapier's historical unit, now spreading to AI agents.
- Per-Unit PricingA billing unit used by robotics, hardware AI, and some SaaS companies where the metered object is a physical or abstract 'unit' — a robot deployed, a device sold, or a defined deliverable.
- Workflow Execution PricingA billing unit where each end-to-end workflow or automation run is metered and billed, regardless of the compute steps it contains.
- Per-Message PricingA billing unit where each individual message or reply in a conversation is metered, common in AI chat and voice platforms.
- Per-Invoice PricingA billing unit used by billing infrastructure platforms where each invoice generated or processed is metered as the primary cost driver.
- Per-Action PricingA billing unit where each discrete action taken by an AI agent or automation is metered — common in browser automation and agentic workflow tools.
- Per-Image PricingA billing unit where each AI-generated image is metered, common in image generation APIs and multimodal AI platforms.
- Per-Conversation PricingA billing unit where each complete customer conversation — from first message to resolution — is metered as a single chargeable event.
- Per-Record PricingA billing unit where each data record processed, labeled, or extracted is metered — common in data platforms and web scraping services.
- Per-Word PricingA billing unit common in translation and localization platforms where the metered object is the word count of content processed.
- Per-Video PricingA billing unit where each AI-generated video is metered, common in video generation and synthetic media platforms.
- Milestone-Based PricingA billing unit used in drug discovery and biotech AI where payment is tied to achieving defined research milestones rather than time or compute consumed.
- Per-Outcome PricingA billing unit where payment is triggered by verified outcomes delivered — distinct from outcome-based pricing models, this refers specifically to 'outcomes' as a countable billing unit.
- Per-Datapoint PricingA billing unit where each individual data measurement or signal ingested is metered — common in cloud cost intelligence and ML evaluation platforms.
- Per-Interaction PricingA billing unit where each patient-agent or user-agent interaction is metered, common in healthcare AI and customer engagement platforms.
- Data Licensing PricingA pricing structure where access to proprietary datasets or data assets is licensed separately from the software or services, common in AI training data and clinical data platforms.
- Robot-Hour PricingA billing unit where each hour a robot or autonomous system operates is metered — the robotics equivalent of a GPU-hour.
- Per-Contact PricingA billing unit where each contact or lead in the database is metered, common in AI sales development and outbound automation platforms.
- Per-Mailbox PricingA billing unit where each connected email mailbox or sending account is metered, common in AI outbound sales and email automation platforms.
- Browser-Hour PricingA billing unit where each hour of headless browser compute time is metered, common in web scraping and browser automation platforms.
- Per-Generation PricingA billing unit where each AI-generated creative asset — image, video, or design — is counted as a 'generation' and metered accordingly.
- Per-Ticket PricingA billing unit where each customer support ticket handled by an AI agent is metered — common in AI customer service platforms.
- Per-Log PricingA billing unit where each LLM request log ingested or stored is metered — common in AI observability and evaluation platforms.
- Per-Trace PricingA billing unit where each distributed trace — a complete record of an LLM request chain — is metered, common in AI observability platforms.
- Per-Device PricingA billing unit where each hardware device or endpoint connected to the AI platform is metered.
- Per-Case PricingA billing unit used in legal AI platforms where each case or matter processed by the AI is metered.
- Per-Report PricingA billing unit where each AI-generated report or analysis document is metered as a discrete output.