What is enterprise web scraping?
Enterprise web scraping is web data collection that meets the requirements a large organization's security, legal, and procurement teams set before any vendor touches production data. The scraping itself is the same as on a self-serve plan; what changes is everything around it: audited security controls, guarantees about what happens to scraped data, identity and access management, reserved capacity, and contracts. A tool that cannot pass a vendor security review never reaches production, however good its output is.
| Requirement | What the reviewer asks | What to look for |
|---|---|---|
| Audited security | Has an independent auditor tested the controls? | SOC 2 Type II report |
| Data retention | Does the vendor store what we scrape? | Zero data retention for scrape, browser sessions, and search |
| Privacy law | Who is the processor, and is it in writing? | Data Processing Agreement, GDPR and CCPA support, PII redaction |
| Identity | Can access follow our identity provider? | SAML or OIDC SSO, SCIM provisioning |
| Network access | Can we lock keys to our networks and allowlist the vendor? | IP restrictions, key restrictions, static outbound IPs |
| Capacity | Will our jobs be starved by other traffic? | Custom and reserved concurrency, spend limits |
| Support | Who answers when a pipeline breaks? | Priority support SLA, dedicated channel |
Enterprise requirements usually show up in a predictable order. Security review comes first (SOC 2, retention, DPA), then IT asks for SSO and SCIM so access is managed centrally, and finally the platform team needs capacity guarantees once multiple teams share one account. Choosing a vendor that already has all three avoids a second procurement cycle a year later. Self-hosting is the other route, but it moves every one of these obligations onto your own team.
What Firecrawl Enterprise includes
Firecrawl Enterprise covers each requirement above for scrape, crawl, search, parse, and interact:
- Security and compliance: SOC 2 Type II; zero data retention for scrape, interact, and search, including end-to-end search ZDR where the upstream search provider also retains nothing; PII redaction; Data Processing Agreements, custom MSAs, and vendor security reviews.
- Identity and access: SAML or OIDC single sign-on and SCIM directory sync (Okta, Entra ID, Google Workspace, and more); static IP allowlisting; IP restrictions and key restrictions per API key.
- Scale: custom and reserved concurrency, custom credit volumes pooled across teams with per-team usage reporting, spend limits per key or team, extended credit rollover, and volume pricing.
- Support and buying: priority support SLA and a dedicated Slack channel, with purchase through AWS Marketplace or Google Cloud Marketplace to draw down existing cloud commitments.
See the enterprise docs for every control, or contact sales to scope a plan.