TL;DR
- Pay-as-you-go is usually easier for a one-off crawl; subscription billing becomes useful when workloads are continuous and predictable.
- Compare the billable unit, included credits, concurrency, proxy charges, storage, and retry behavior—not only the headline URL rate.
- Nstdata Crawl documents both balance-based use without a subscription and subscription plans with included credits; proxy usage is separate.
- The right estimate is cost per accepted page or usable record, not cost per request.
The short answer: choose by workload shape
For a current product example, review Nstdata Crawl before comparing billing models.
Choose pay-as-you-go when volume is uncertain, a project is exploratory, or you need to avoid recurring commitment. Choose a subscription when recurring batches, higher concurrency, or included credits reduce effective cost enough to justify a monthly commitment. Nstdata’s Crawl pricing page is the primary source for the current model; exact plan values change and should be checked before purchase.
Pay-as-you-go versus subscription
| Decision field | Pay-as-you-go | Subscription |
|---|---|---|
| Best fit | Tests and irregular batches | Recurring pipelines |
| Commitment | No recurring plan required | Monthly plan commitment |
| Unit economics | Simple usage rate | Lower effective rate may apply at volume |
| Capacity | Lower default concurrency may apply | Higher limits depend on plan |
| Credits | Account balance funds usage | Included credits offset eligible usage first |
| Risk |
