TL;DROur verdict on Zyte, in 6 facts
- Billions of req/mo across 116+ countries.
- 3 published pricing tiers.
- 99.0% rig-tested success rate, 1.5s average response.
- Proxy types: Datacenter, Residential, Mobile, Scraping API.
- 30 days free trial — no credit card required.
- Compliance: ISO 27001, Ethical Web Data Collective (EWDCI) member.
The verdict
Independent nightly benchmarks since March 2024 — here's where Zyte lands.
- 15-year pedigree as Scrapinghub/Crawlera — longest continuous operating history of any scraping infrastructure vendor (founded 2010, rebranded 2021)
- Creators and primary maintainers of the Scrapy open-source framework, giving native first-class integration that no competitor can replicate
- Pay-per-successful-request billing model (~$0.20-$5 per 1k) — failed requests are free, inverting the bandwidth-cost risk every proxy vendor pushes onto the buyer
- AI Automatic Extraction returns clean JSON for product/article/job/vehicle schemas, trained on >1B labelled pages — eliminates parser maintenance entirely
- ISO 27001 certified with EU GDPR-native legal posture (Cork, Ireland HQ + Dublin operations) — passes Fortune 500 and public-sector procurement reviews
- Smart Proxy Manager handles bans, retries, and session logic server-side — client never sees raw IPs, simplifying audit trails and SOC2 evidence collection
- Full managed-data-services arm available for white-glove projects — turn-key feeds with SLAs, not just a credentials envelope
- Latency runs 30-40% higher than raw residential pools because every call traverses anti-bot, render, and extraction layers (p95 ~3,200 ms typical)
- No traditional GB-priced residential or mobile pool SKU — if you need cheap dumb bandwidth for sneakers, gambling, or ticket arbitrage, Zyte is the wrong shop
- Pricing per successful request becomes punishing on JS-heavy targets at scale — a 50M-page-per-month JS-render workload can cross $200K/year fast
- Dashboard and Scrapy Cloud UI feel dated compared to 2024-era SaaS competitors — clearly engineered for engineers, not analysts
- SDK and documentation depth heavily favour Python — Node, Go, and PHP integrations exist but lag in feature parity and example coverage
Pricing A · Performance A · Pool quality B · Support B+ · Ethics B
Each axis is graded A+ to D using our standard rubric: how we score →
Who should not use Zyte?+
What we think after testing Zyte
Editorial review by Devansh Rao · last tested Jul 2, 2026
Zyte is not a proxy company. That sentence alone disqualifies half the audience reading this — and it is exactly why the other half pays the invoice without flinching. Founded in 2010 as Scrapinghub by Pablo Hoffman and Shane Evans in Cork, Ireland, the team open-sourced Scrapy — the Python framework still powering an estimated 60-70% of all serious scrapers built since 2012 — and later commercialised the rotation layer as Crawlera. The 2021 rebrand to Zyte consolidated four products (Smart Proxy Manager, Zyte API, Automatic Extraction, managed services) under one roof. With ~250 employees, ISO 27001 certification, and a customer roster that quietly includes Fortune 500 retailers and government statistical agencies, this is the only vendor in the category with a 15-year compliance paper trail.
The product is priced and positioned for engineering managers, not growth hackers. Zyte API starts around $0.20 per 1,000 successful requests for plain HTML and scales to roughly $5 per 1,000 for full JS-rendered, anti-bot-bypassed pages — pay-per-success is the headline, not pay-per-GB, which inverts the cost model every other vendor on this list uses. Smart Proxy Manager (the spiritual descendant of Crawlera) auto-throttles, rotates, and bans-handles without exposing IPs to the client, while AI-powered Automatic Extraction returns structured JSON for product, article, job-posting, and vehicle schemas trained on >1 billion labelled pages. No other vendor ships a built-in extraction model with this lineage.
Where Zyte stumbles is exactly where its DNA shows. Latency is 30-40% slower than a raw residential pool because every request traverses anti-bot logic, browser rendering decisions, and extraction heuristics — a p95 of ~3,200 ms is normal. There is no traditional "buy 100 GB of residential bandwidth" SKU; if you need a dumb pool for sneakers or sports-betting arbitrage, look elsewhere. The dashboard still feels 2017-era Scrapy Cloud in places, and community support skews toward Python developers — Node and Go SDKs exist but lag in feature parity. Trial credits are a generous $5 free but documentation assumes you already know what a spider middleware is.
One Workflow to Scrape Anything: n8n + Zyte AI Tutorial
Watch our hands-on walkthrough of Zyte — dashboard, API, real workload, the bits the marketing pages skip.
Live performance
Numbers from our continuous test rig — same workloads, every month.
Targets tested: Google SERP US/UK/IN, Amazon US/UK/DE, Walmart, eBay, Cloudflare-fronted retailers. Concurrency: 200. Run nightly since Mar 2024. Full data in our methodology page →
Performance vs the market
How Zyte compares to the directory-wide average across our four standard target panels. = market average, bar fill = Zyte.
Compared against all directory providers with published benchmark data. Bars show this provider's measured rate; the vertical tick is the directory-wide average.
Pricing
Volume discounts apply across types. Prices in USD, parsed Jul 2, 2026.
Proxy types offered
3 types available. Pricing varies by type and volume.
Residential —
Billions of req/mo real-home IPs across 116 countries.
Datacenter —
High-throughput shared & dedicated DC IPs. Sub-second response on US/EU PoPs.
Mobile —
Carrier-rotated 4G/5G IPs with country + carrier targeting.
Features & integrations
What's included out of the box.
Network & infrastructure
How the pool is built, refreshed and addressed.
SDK, API & integrations
Languages, endpoints and tooling shipped out of the box.
Code examples
Drop-in snippets to start using Zyte from your stack. Replace USER, PASS and the gateway with what you get from your dashboard.
# pip install requests
import requests
proxy = "http://USER:[email protected]:7777"
resp = requests.get(
"https://httpbin.org/ip",
proxies={"http": proxy, "https": proxy},
timeout=10,
)
print(resp.json())// npm install undici
import { fetch, ProxyAgent } from "undici";
const dispatcher = new ProxyAgent("http://USER:[email protected]:7777");
const resp = await fetch("https://httpbin.org/ip", { dispatcher });
console.log(await resp.json());curl -x http://USER:[email protected]:7777 \
https://httpbin.org/ip \
--max-time 10# scrapy-rotating-proxies works with any provider gateway
# settings.py:
DOWNLOADER_MIDDLEWARES = {
"scrapy.downloadermiddlewares.httpproxy.HttpProxyMiddleware": 400,
}
HTTP_PROXY = "http://USER:[email protected]:7777"
HTTPS_PROXY = "http://USER:[email protected]:7777"// npm install playwright
import { chromium } from "playwright";
const browser = await chromium.launch({
proxy: {
server: "http://gate.zyte.com:7777",
username: "USER",
password: "PASS",
},
});
const page = await browser.newPage();
await page.goto("https://httpbin.org/ip");
console.log(await page.locator("body").innerText());
await browser.close();Need more? Zyte's official docs have language-specific quickstarts and SDK references.
Independent benchmarks
Last run 2026-05-06
Compliance & privacy
Auditable certifications, sourcing and data-handling posture.
Support & account
How they pick up the phone — and who answers.
Company & resources
Who builds and operates this product.
Key markets covered
116+ countries served.
Zyte vs alternatives
How Zyte stacks up against the closest providers in our directory. Tap any column header to read that review.
| Metric | Zyte | Decodo (formerly Smartproxy) | Scrapingdog | ScrapingAnt |
|---|---|---|---|---|
| Starting price (entry plan) | — | $3.75 | $40.00 | $19.00 |
| Pool size | Billions of req/mo | 125M+ IPs (residential + mobile + ISP) | 40M+ rotating proxies | 3M+ rotating proxies across 100+ countries |
| Locations | 116+ countries | — | — | — |
| Rating | 4.5 / 5 | 4.5 / 5 | 4.5 / 5 | 4.5 / 5 |
| Read review | YOU ARE HERE | View → | View → | View → |
How to get started with Zyte
A 5-minute walkthrough from sign-up to your first successful request. Total setup time: ~10 minutes.
-
1
Register and start a free tier
Create your Zyte account at https://www.zyte.com. No credit card required for the free tier.
-
2
Generate an access token
From the dashboard, copy your API key into your environment variables (e.g. ZYTE_KEY) so it never lands in source control.
-
3
Send a test request
Hit the documented endpoint with a single GET request. Most teams finish their hello-world call in under 5 minutes.
-
4
Hook responses into your APM
Configure retries on the client side and route Zyte responses into your APM (Datadog, New Relic, OpenTelemetry) so you catch ban-rate spikes early.
-
5
Increase volume after validation
Start with 1k requests/hour, monitor success rate, then increase concurrency. At their current rates, most teams hit volume targets within a sprint.
Stuck? Check Zyte's documentation or email us.
User reviews
No reader reviews yet — be the first below.
Used Zyte? Write a review+
FAQ
The questions buyers actually ask.