Pricing that follows usage
Use this page to understand the model. Exact public plans should only appear after pricing is verified.
Pricing should be easy to reason about
SpiderFly pricing copy stays conservative until exact public plans are verified.
Usage follows work done
Fetches, browser-backed requests, crawl volume, and extraction work should map to understandable usage units.
Start with API access
Use the product console to create keys and test workloads before committing to larger usage.
Scale after review
Larger workloads should be scoped against traffic shape, browser needs, and data handling requirements.
Good for early evaluation
Create an API key, run real examples, and review which requests need browser rendering or crawl volume.
Ready for larger workloads
Bring expected URL volume, rendering needs, and data handling requirements before scaling usage.