Data Platform Pricing: Examples & Companies

What is it

Data Platform Pricing is pricing for data platforms — scraping, enrichment, search API, and knowledge-graph vendors.

These are the companies that sell the structured data AI systems need for grounding, enrichment, and training. The category spans four overlapping sub-types: web-extraction and proxy platforms (Bright Data, Oxylabs, ScraperAPI, Firecrawl, Apify, Browse AI); search and knowledge APIs (SerpApi, Linkup, Diffbot, Nomic); GTM enrichment and analytics (Clay, Julius AI, Powerdrill, Rows); and the data infrastructure underneath them — vector stores, metering layers, and compute (turbopuffer, Upstash, OpenMeter, Anyscale).

What unites the category is a structural fact: the cost driver is volume of data, not headcount. A single account can run millions of automated requests or store terabytes of vectors, so seat-based pricing has no relationship to the cost of service. Every company on this page therefore meters something — requests, bandwidth, records, credits, or storage — even when it wraps that meter in a monthly subscription tier.

The category is also consolidating. ScraperAPI’s parent acquired Traject Data; the proxy and scraping vendors are converging on near-identical per-GB and per-1,000-results rate cards. The differentiation is no longer the meter itself but the generosity of the included volume, the steepness of the overage curve, and how honestly the unit math is exposed on the public pricing page. For the strategy behind these choices, see our introduction to usage-based pricing and the data pipeline use-case breakdown.

How it works

Data platforms pick a meter that tracks their dominant cost, then wrap it in either pure pay-as-you-go or a subscription tier that pre-buys volume. The five common meters and their canonical examples:

Worked example — credit-pool scraping. Firecrawl’s Standard plan is $83/mo for 500,000 credits, where 1 credit ≈ 1 scraped page. A pipeline scraping 480,000 pages/month stays inside the pool and pays the flat $83. Cross to 520,000 pages and the 20,000 overflow auto-recharges at the plan’s per-credit rate — the model behaves like a subscription until you exceed the pool, then like pure usage.

Worked example — per-GB proxy. Oxylabs residential proxies start at $6/GB on the $30/mo Starter (5GB), declining to $2.50/GB on the 1TB Corporate tier. Moving 200GB of residential traffic costs roughly $500–$1,200 depending on the committed tier — the unit math is identical to Bright Data’s $8 → $2.50/GB ladder, which is why included-volume and overage steepness, not headline rate, decide the deal.

Worked example — pure usage with a floor. turbopuffer meters writes, queries (now $1/PB after a February 2026 cut from $5/PB), and per-GB-month storage, but every tier carries a monthly minimum — $64, $256, or ≥$4,096. A workload billing $40 of metered usage on the $64 tier still pays $64; the floor is the real entry price. See usage invoicing and billing cycles for how minimums and overage are reconciled on the invoice.

Companies using this

The corpus tracks 21 data platforms spanning web extraction, search APIs, enrichment, analytics, and the vector and metering infrastructure underneath. The table below lists each company with its pricing model, billing units, free-tier status, and last-verified date.

Patterns observed

The meter follows the cost driver, and changes per product. Bright Data is the clearest case: bandwidth-heavy residential proxies bill per-GB, static ISP/datacenter proxies bill per-IP, scraping and SERP APIs bill per 1,000 results, and ready-made datasets bill per 1,000 records — four billing units under one roof, each tracking the dominant cost of its product line. Oxylabs mirrors this exactly: per-GB and per-IP proxies, per-1K-results scraper APIs. The lesson is that “data platform pricing” is rarely a single model; it’s a portfolio of meters.

Credits are the abstraction of choice for scraping and enrichment. Firecrawl (1 credit ≈ 1 page), ScraperAPI (per-request multiplier on a credit allotment), Diffbot ($0.001/credit on prepaid pools), and Clay (Actions capacity plus a Data Credits pool) all use a credit layer. Credits let these vendors expose many features — crawl vs scrape, standard vs premium proxy, basic vs AI enrichment — at different internal rates without forcing the buyer to learn each one, and let the vendor change underlying economics without renegotiating.

Free volume is table stakes, but only on the legible meters. Diffbot gives 10,000 credits/month free, Firecrawl 1,000 credits, SerpApi a free monthly search allowance, and Linkup a recurring $20 balance (~4,000 searches). The free tier sits on the request/credit meter where marginal cost is low. Raw bandwidth and bulk datasets — where Bright Data charges from the first GB — rarely get a free allowance, because the cost of serving is real and immediate.

Subscription tiers are increasingly just pre-bought usage. ScraperAPI’s seven-tier ladder, Firecrawl’s six tiers, and Julius AI’s credit-pool subscriptions all present as flat monthly plans but are sized by an included usage allotment with overage beyond it. This hybrid framing — predictable floor, metered ceiling — is now the default for the category, blending the budgeting comfort of subscription with the cost-alignment of usage.

Counterexamples & variants

Storage-and-query infra prices nothing like a scraper. turbopuffer and Upstash are data platforms, but they store and serve data rather than extract it, so their meters are writes, queries, vectors indexed, and GB-month storage — not requests or records. turbopuffer’s tier-scaled monthly minimum (up to ≥$4,096) is a commitment mechanic that scraping APIs almost never use, because their buyers expect to start at zero. Treating these vector/cache platforms as interchangeable with scraping APIs would mislead on both the meter and the entry price.

The human-data marketplaces have no public meter at all. Mercor and micro1 sell data partnerships and human-labeling/RL-environment work to frontier AI labs, and both are sales-quoted with no visible price — Mercor discloses only the hourly expert pay, not the buyer take-rate. They sit in the data-platform category because the product is data, but the pricing motion is enterprise sales-led, the opposite of the self-serve per-request norm. They’re a reminder that “data platform” spans both a $0.005-per-request API and a multi-million-dollar custom data contract.

Open-core breaks the usage frame entirely. OpenMeter is the metering-and-billing platform other usage-based vendors run on, and it’s priced open-core: a free Apache-2.0 self-hosted edition plus a contact-sales managed cloud (now Kong Metering & Billing). There is no per-event public rate — the free tier is the entire software, and revenue comes from the managed and enterprise upsell. It’s a variant where the “data” being platformed is the customer’s own usage events, and the pricing logic inverts the rest of the category.

What this means for buyers vs vendors

For buyers

Forecast on your actual cost driver, not the headline tier. A scraping pipeline should model credits-per-page or successful-results-per-1K; a proxy workload should model GB-per-month; a vector store should model writes, queries, and stored GB plus the tier minimum. The headline rates across Bright Data and Oxylabs are near-identical, so the deal is decided by included volume and overage steepness — get both in writing. Watch for floors: turbopuffer’s monthly minimum means low-usage months still cost the tier price, and ScraperAPI’s concurrent-thread caps can throttle throughput regardless of credit balance. Use the free allowances — Diffbot’s 10,000 credits, Firecrawl’s 1,000, Linkup’s recurring $20 — to benchmark real per-job cost before committing to a tier.

For vendors

Pick the meter that tracks your dominant marginal cost, and don’t be afraid to run multiple meters if you sell multiple products — Bright Data’s four-unit portfolio proves buyers tolerate this when each meter is intuitive for its product. Use a credit abstraction when you need to expose many features at different internal rates or expect to change economics, as Firecrawl and Diffbot do — but keep the credit-to-output mapping legible (1 credit ≈ 1 page) or buyers will distrust it. Put a free allowance on your cheapest-to-serve meter to drive self-serve acquisition, and reserve commitment minimums for infra products like vector and cache stores where buyers expect them. If you’re building the metering itself, study OpenMeter’s open-core path; for the broader strategy, our usage-based pricing introduction and billing-cycle guide cover floor reconciliation and overage design.