Number of Seats/Users: Zyte offers discounts based on the number of users or seats. A higher volume typically leads to a better discount structure, especially for enterprise-level usage.

Commitment to a Long-Term Contract: Discounts are often provided to companies that commit to using the service for a longer period (e.g., 1-year or 3-year contracts). A longer commitment shows Zyte that the company is serious and willing to invest in the platform long-term.

No Active Discounts: Companies that are not already receiving other active discounts may have a better chance of qualifying for additional discounts from Zyte. Zyte reserves discounts for new customers or those not currently under promotional pricing.

Volume or Usage Commitment: Zyte offers discounts if you agree to a minimum amount of usage or transaction volume. This could be based on data storage, transactions, or other metrics tied to how much you will use the platform.

Enterprise-Level Negotiation: Companies that qualify as “enterprise” due to their size or complexity (e.g., having large teams, multiple departments, or geographical presence) may be eligible for additional discounts from Zyte. Such companies are often in a position to negotiate for better pricing.

Early Renewal or Prepayment: Zyte often offers discounts if you renew early or prepay for the entire contract period. This is a common approach to securing a lower price.

Here at Spendbase our internal data shows that Zyte (ex‑Scrapinghub) is generally seen as a strong, production‑grade option for web data extraction, with a few clear patterns around cost control and usability that matter for budgeting.

From what Spendbase clients share, the main strengths are:

• Reliability and scale
• Very high uptime and stability.
• Handles millions of requests and high concurrency once properly configured.

• Crawlera / Smart Proxy Manager “just works” for many teams, removing the need to manage proxy farms.

• Data quality and coverage

• Access to 90%+ of required web resources in many cases.

• Lower error rates and latency compared with generic proxy vendors.

• Developer experience (for technical teams)

• Tight integration with Scrapy, easy deployment of spiders.
• Good dashboards and monitoring for hosted crawlers.
• Helpful and responsive technical support in most cases.

At the same time, our internal data shows some recurring pain points that affect total cost of ownership:

• Pricing & cost control
• Multiple Spendbase clients mention that pricing feels high, especially for startups or mid‑volume workloads.
• Time‑based subscriptions are not ideal for teams that would prefer per‑request or flexible consumption models.

• A few cases of unexpected overage bills and confusion around spend limits; billing support can feel rigid.

• Onboarding & usability

• Non‑technical stakeholders find the platform harder to use without developer support.
• UI can feel dated or less “premium” compared with modern dev tools.

• Portia and Splash are often seen as clunky or hard to debug.

• Advanced use cases

• Anti‑bot and difficult sites (Amazon, Distil‑protected, some geo‑specific locations) still require tuning or extra spend.
• Some clients report limited IP diversity in certain regions.

From a Spendbase savings perspective, Zyte tends to be an excellent fit when:

• You have an engineering team that can fully leverage Scrapy + Zyte.
• You need high reliability and are replacing DIY proxy farms or multiple smaller vendors.
• You actively manage usage (concurrency, retries, regions) to avoid bill spikes.

Where we usually find optimization opportunities is in plan sizing, switching from time‑based to better‑fitting tiers, and tightening spend controls around concurrency and high‑latency targets.