Frequently Asked Questions
Pricing, Compliance & Architecture
Clear, definitive answers to help your engineering, procurement, and legal teams understand how Crawlexa's fully managed data pipelines operate.
What is Crawlexa's pricing structure and what is included?
Our baseline finalized pricing is $500 per 1,000,000 records ($0.0005 per record / $0.50 per 1,000 records).
- Growth Plan: $500/month for up to 1,000,000 records ($425/mo on annual billing).
- Scale Pro Plan: $1,500/month for up to 3,000,000 records ($1,275/mo on annual billing).
- Custom Enterprise: Dedicated high-concurrency clusters for 10M+ records/month.
All plans include unlimited residential proxy bandwidth, headless browser infrastructure, schema normalization, and continuous 24/7 DOM maintenance. There are zero setup fees ($0 development fee on your first project).
What is the exact distinction between a "Page" and a "Record"?
A Page is an HTTP request, API call, or headless browser DOM rendering cycle. A Record is a clean, normalized, schema-validated entity output (e.g., a single product SKU, listing, real estate property, or user review).
Crawlexa charges based on verified extracted records. If our crawler has to paginate through 10 pages or retry challenges to harvest 100 valid products, you are only billed for the 100 verified records.
How fast can Crawlexa deliver an initial sample dataset?
We deliver representative 1,000-record proof-of-concept samples within 4 business hours of receiving your target URL or mobile app endpoint and required schema fields. Production pipelines are typically engineered and scheduled within 24 to 48 hours.
Is web scraping and mobile app data extraction legal?
Yes. Crawlexa exclusively harvests publicly available data that does not require an authenticated login or breach a paywall. This practice is supported by established legal precedents (such as the landmark US Ninth Circuit hiQ Labs v. LinkedIn ruling).
We strictly enforce polite crawling rate limits to avoid server degradation, respect robots exclusions where legally applicable, and filter out any personal identifiable information (PII) to maintain GDPR and CCPA compliance.
What delivery formats and cloud destinations are supported?
We deliver data in whatever format your stack requires: JSON, NDJSON, CSV, TSV, and Apache Parquet.
Delivery destinations include automated direct pushing to Amazon S3, Google Cloud Storage, Google BigQuery, Snowflake, Azure Data Lake, PostgreSQL, or real-time streaming REST webhooks.
How do you overcome Cloudflare Turnstile, DataDome, and WAF blocks?
We utilize an automated proxy orchestration mesh of over 45M+ ethically sourced residential, mobile 4G/5G, and datacenter IP addresses across 190+ countries. Our headless browser mesh emulates human mouse trajectories, WebGL canvas signatures, and randomized TLS fingerprints to reliably sustain a 99.8%+ target extraction success rate.
What happens when a target website alters its HTML or DOM layout?
Our infrastructure maintains automated schema telemetry that evaluates incoming payload completeness, missing field thresholds, and structural drift. If a target changes its DOM, our on-call data SRE engineers patch the extractor within our SLA, ensuring zero disruption to your downstream applications.