Thordata Pricing: Is It Worth It for Data Teams?

If you run a data team, you already know the pricing page is the most important page on any proxy provider's site. Everything else is marketing. Thordata has been climbing into the conversation alongside the usual heavyweights, and the question I keep getting asked is simple: is the pricing actually worth it, or is it just another "cheaper than Bright Data" pitch that falls apart at scale?

Short answer: for most mid-sized data teams, Thordata's pricing lands in a genuinely useful sweet spot, especially if your workload is residential-heavy and you don't need exotic geo-targeting. But there are caveats, and the marketing site does its best to hide them. Let's get into it.

What You're Actually Paying For

Proxy pricing looks simple until you read the footnotes. With Thordata, you're paying for one of four proxy types, billed in ways that don't line up perfectly across products:

• Residential proxies - billed per GB of traffic, the standard model
• ISP (static residential) proxies - billed per IP per month, with bandwidth tiers
• Datacenter proxies - cheapest, billed per IP or per GB depending on plan
• Mobile proxies - the premium tier, per GB and noticeably more expensive
• Web Scraper API - billed per successful request, not per GB

That last one matters more than people realize. If your team is currently running a homegrown scraper that burns 40% of its bandwidth on retries, blocked requests, and CAPTCHA loops, the per-request model can quietly save you more money than a 20% per-GB discount would.

The Headline Numbers

Residential traffic on Thordata typically starts around the $3-4/GB range on entry plans and drops into the $1-2/GB territory once you commit to higher monthly volumes (think 500GB+). That's competitive. It's roughly half of what Bright Data charges at the same tier and comfortably below Oxylabs' published rates.

Datacenter pricing is where the gap widens further - Thordata's datacenter pool is priced aggressively, which is great if your targets aren't sophisticated enough to fingerprint datacenter IPs. The catch: a lot of modern targets are. So the cheap datacenter tier is real savings only if you've actually validated it works on your specific URLs.

Where the Hidden Costs Live

Here's the part the comparison blogs skip. A few things to watch:

Failed requests on the Scraper API

Thordata, like most providers, only charges for successful requests on the Web Scraper API. Sounds great. But "successful" is defined by HTTP status, not by whether you got the data you wanted. A 200 response on a soft-block page (think a CAPTCHA or "are you human" interstitial) still counts. Build your validation layer accordingly.

Bandwidth on JavaScript rendering

If you turn on JS rendering for residential traffic, your per-GB consumption can 3-5x compared to raw HTML scraping. This isn't unique to Thordata, but the pricing calculator on their site uses raw-HTML assumptions. Budget realistically.

Geo-targeting premiums

City-level and ASN-level targeting is included on most plans, which is genuinely nice - Bright Data still charges extra for granular geo on lower tiers. But certain country pools (some Tier-1 European markets, parts of Southeast Asia) have thinner IP availability, which means more retries and effectively higher real cost.

How Thordata Compares to the Big Three

Let me put this plainly because the comparison tables online are mostly affiliate fluff.

vs. Bright Data: Thordata is cheaper, period. Bright Data has a wider IP pool, better dashboard, and more enterprise features (audit logs, SOC 2, dedicated account managers). If you're a regulated industry or doing $10k+/month, Bright Data's overhead pays for itself. If you're a 5-person data team trying to keep AWS bills sane, Thordata wins.

vs. Oxylabs: Closer fight. Oxylabs has slightly better residential coverage in some markets and a more mature Scraper API. Thordata is roughly 20-30% cheaper at comparable volumes. The right answer depends on your specific target sites - run a 7-day trial against your actual workload before committing.

vs. Smartproxy: Smartproxy has historically been the "cheap and friendly" option. Thordata now matches them on price and offers a deeper IP pool. Smartproxy's UX is still more polished for non-engineers.

If you're shopping the broader category, our best proxy services for web scraping roundup covers the trade-offs in detail, and the residential proxy comparison breaks down per-GB economics across nine providers.

Who Thordata Is Actually Good For

After helping a few teams pilot it, here's my honest take on fit:

• Good fit: Mid-sized data teams (3-15 engineers) running steady-state residential scraping at 100GB-2TB/month, with a workload that's already been hardened against blocks. You'll get real savings without losing meaningful capability.
• Decent fit: Solo founders and small startups doing under 50GB/month. The entry pricing is reasonable, but at that volume the hourly cost of switching providers later can outweigh the savings. Pick based on stability, not price.
• Bad fit: Enterprise teams that need procurement-friendly contracts, SSO, detailed audit logs, or 24/7 dedicated support. Thordata's support is responsive but isn't structured for enterprise compliance workflows yet.
• Bad fit: Teams scraping highly protected targets (major social platforms, some travel aggregators) where IP quality matters more than per-GB price. You'll pay less but retry more, and net cost per useful row of data may actually be higher.

A Realistic Cost Model

Let's run the numbers on a typical mid-sized data team workload: 500GB/month of residential traffic, 80% raw HTML, 20% JS-rendered, scraping moderately defended e-commerce and SaaS sites.

On Thordata's mid-tier residential plan, you're looking at roughly $750-1000/month all-in, factoring in the JS-render multiplier and a realistic 15% retry overhead. The same workload on Bright Data lands closer to $1800-2200. Oxylabs sits around $1100-1400. Smartproxy is comparable to Thordata but with slightly less flexibility on geo-targeting.

That $800-1200/month difference vs. Bright Data is real money for a small data team. Whether it's worth the trade-offs (smaller IP pool, lighter dashboard, less enterprise polish) is your call. For most teams I've talked to, the answer is yes.

What I'd Actually Test Before Committing

If you're seriously evaluating Thordata, don't rely on the marketing comparison. Run this 5-day pilot:

1. Your top 10 target domains. Not the easy ones. The ones that block you most. Measure success rate per dollar spent.
2. Peak-hour performance. Run identical workloads at 9am ET and 9pm ET. Some providers degrade under load.
3. Geo-targeting accuracy. Spot-check 100 requests claiming to be from specific cities. Verify against IP geolocation databases.
4. Support response time. Open a real ticket about a real issue, not a sales question. See what happens.
5. Real per-row cost. Forget per-GB. Calculate dollars per useful, validated row of data extracted. This number is the only one that matters.

If you want a structured framework for this kind of evaluation, our guide on how to evaluate web scraping providers walks through it step by step.

The Verdict

Thordata pricing is, for the workloads it's designed for, genuinely good value. It's not a Bright Data killer - the enterprise features aren't there yet - but for the sweet spot of small-to-mid data teams running steady-state residential scraping, it's hard to beat on cost-per-GB without giving up meaningful capability.

The risk isn't the headline price. It's all the second-order stuff: retry rates on your specific targets, JS-render bandwidth multipliers, and how much your team's time is worth when something breaks. Run the pilot. Trust the numbers, not the comparison table.

For teams already deep in the proxy ecosystem, you might also want to look at Oxylabs and Smartproxy as direct alternatives, or browse the full data extraction tools category for the broader landscape.

Frequently Asked Questions

Is Thordata cheaper than Bright Data?

Yes, materially. At equivalent residential volumes, Thordata typically runs 40-50% cheaper per GB. Bright Data justifies the premium with a larger IP pool, more enterprise features, and better support tiers - which matter for some teams and don't for others.

Does Thordata charge for failed requests?

On the Web Scraper API, only successful HTTP responses are billed. On raw proxy traffic, you pay for all bandwidth used, including blocked requests. Build retry logic that gives up faster on consistently failing targets to keep costs in line.

What's the minimum spend on Thordata?

Entry residential plans start in the $50-100/month range, which is fine for prototyping. The real per-GB savings kick in around 100GB+/month, and the best rates require committing to 500GB+ tiers.

Can I pay as I go on Thordata?

Thordata offers monthly subscriptions and pay-as-you-go residential traffic, though PAYG rates are noticeably higher per GB than committed plans. For predictable workloads, the monthly tier almost always wins.

Is Thordata good for scraping JavaScript-heavy sites?

The Web Scraper API handles JS rendering and CAPTCHA solving and is priced per successful request, which is the right model for JS-heavy work. Pure proxy + your own headless browser will be cheaper per request but more engineering overhead. Pick based on your team's bandwidth.

Does Thordata offer city-level or ASN targeting?

Yes, granular geo-targeting (country, state, city, ASN) is included on most residential plans without extra fees - a meaningful advantage over providers that gate this behind premium tiers.

Is Thordata SOC 2 compliant?

As of this writing, Thordata doesn't publicly advertise SOC 2 Type II certification the way Bright Data and Oxylabs do. If your industry requires that level of audit, this is a real blocker - confirm directly with their sales team before committing.