Zyte review

Zyte sells tools and services for collecting web data, from a scraping API to managed data delivery and crawler hosting. Its homepage describes the workflow as access, extraction and delivery, with structured data options for e-commerce. The API chooses an access strategy for each URL, while its extraction features can return product fields such as name, price, currency, availability, SKU and images.

There are several ways to use the stack. Teams can build crawlers with Scrapy, Zyte’s open-source framework, and run them on Scrapy Cloud rather than managing their own servers. Or Zyte can build and maintain a collection, then deliver deduplicated, schema-ready data to a warehouse on a chosen cadence. The practical distinction is how much you want to own: Zyte can provide API access, infrastructure, or more of the data pipeline. Those are different services, so confirm which one you need before comparing costs.

The main appeal is range. Zyte combines a scraping API, structured extraction, Scrapy and crawler hosting, with managed data available for teams that do not want to maintain the collection themselves. That can reduce the number of separate tools to coordinate, though it does not mean every service has the same price or scope.

For e-commerce, the listed extraction fields cover common catalog needs: product name, price, currency, availability, SKU and images. Zyte also supports collecting listings, reviews and inventory data. Scrapy is open source, so teams can build around the framework rather than treating every crawler as a proprietary service. Scrapy Cloud runs, monitors and scales crawlers without requiring you to own servers, according to the product description.

The API pricing page offers pay-as-you-go with no subscription, plus a $5 trial credit. It lists HTTP rates from $0.13 to $1.27 per 1,000 requests and browser-rendered rates from $1.01 to $16.08, across five website pricing tiers. The price varies enough that the broad domain coverage matters more than the headline starting rate. A commenter on r/Entrepreneur described Zyte as an all-in-one scraping option; that is a user opinion, not a guarantee of fit.

The price is not one simple per-request rate. According to the pricing page, pay-as-you-go HTTP requests range from $0.13 to $1.27 per 1,000, while browser-rendered requests range from $1.01 to $16.08. The page lists five website pricing tiers, so your bill depends on which sites you scrape and whether rendering is needed. The starting price is not a reliable estimate for a mixed retail workload.

Committed tiers require a monthly minimum: $100, $200 or $500. Their listed HTTP rates range from $0.10–$0.95, $0.08–$0.76 and $0.06–$0.61 per 1,000, respectively; browser-rendered rates also vary by tier. Annual billing is not listed. Usage above the minimum is charged at the discounted rate with no overage penalty, but some advanced features may add usage-based charges whose amounts are not published. The listed pricing also does not establish separate costs for managed data or crawler hosting. A 30-day trial is listed, but the free-plan field is false; the pay-as-you-go offer includes $5 in trial credit. Reddit users caution that domain mix and JavaScript rendering can change effective costs, so price a representative URL set before committing.

Zyte’s pay-as-you-go plan has no subscription, but rates vary by website tier and request type: HTTP costs $0.13–$1.27 per 1,000 requests, while browser-rendered requests cost $1.01–$16.08 per 1,000. The pricing page lists a 30-day trial with $5 in credit; there’s no free plan.

Committed plans start at a $100 monthly minimum. That tier lowers rates to $0.10–$0.95 per 1,000 HTTP requests and $0.75–$12 per 1,000 browser-rendered requests. The $200 tier drops the ranges to $0.08–$0.76 and $0.60–$9.60; the $500 tier drops them to $0.06–$0.61 and $0.48–$7.68. The trade-off is a $100 jump between the listed commitments, with lower rates at each step. Usage above the minimum is billed at the discounted rate, with no overage penalty. Some advanced features may add usage charges, but amounts aren’t published. Annual billing isn’t listed, and enterprise pricing is custom.

The effort depends on what you’re replacing. Moving scraping requests to Zyte means adapting your collection workflow to its API; teams already using Scrapy may have a more direct route because Scrapy is open source and Zyte offers crawler hosting. Managed data is a bigger operating change: Zyte builds and maintains collection and delivers schema-ready data to a warehouse, but the published material doesn’t specify export formats, migration tooling, or how to take over a managed pipeline.

Before switching, confirm where your data lands, how you can retrieve it, and what happens to crawlers and schemas if you leave. Those details aren’t published here, so don’t assume portability. The published sources contain no Reddit posts, so we can’t attribute common reasons for leaving to users. The stated fit limits are clearer: a fixed monthly bill, fully published costs, or a free plan may push a buyer elsewhere. Price a representative mix of sites before committing.