Our Regional Infrastructure
BlazeCrawl operates in three geographic regions. Your data stays in your chosen region.
🇺🇸 United States
Primary: us-central1 (Iowa)
DR: us-east4 (Virginia)
Endpoint: us.api.blazecrawl.dev
🇪🇺 European Union
Primary: europe-west4 (Netherlands)
DR: europe-west1 (Belgium)
Endpoint: eu.api.blazecrawl.dev
🌏 Asia Pacific
Primary: asia-southeast1 (Singapore)
DR: asia-northeast1 (Tokyo)
Endpoint: ap.api.blazecrawl.dev
Data Residency Commitment
Your data never leaves your region unless explicitly required for routing or billing.
What stays in your region
- Crawl jobs and results
- Extracted data and content
- Screenshots and checkpoints
- Vector store configurations
- Export files
- Audit events
- Usage data
What may be global (allowlisted)
- Workspace ID → region mapping (for routing)
- Billing aggregates (Stripe integration)
- User authentication (SSO)
How It Works
1. Request Routing
When you make an API request, our Cloudflare edge worker determines your region from your workspace configuration and routes to the correct regional endpoint.
2. Regional Enforcement
Our region guard middleware validates that requests hit the correct region. If a request reaches the wrong region, it returns a 421 Misdirected Request with the correct URL.
3. Storage Isolation
Each region has its own infrastructure:
- Regional PostgreSQL (Cloud SQL)
- Regional Redis (Memorystore)
- Regional GCS buckets (NOT multi-region)
- Regional BigQuery datasets
- Regional KMS keyring
GDPR Compliance
For EU customers, data residency is built into our architecture:
- Data stored exclusively in europe-west4 (Netherlands)
- No cross-region replication of customer data
- EU-specific DPA available
- Sub-processor list includes only EU infrastructure
Changing Your Region
Workspace region is set at creation and cannot be changed without a migration process. Contact enterprise@blazecrawl.dev if you need to migrate to a different region.
Disaster Recovery
Each region has a dedicated DR site:
- US: us-central1 → us-east4
- EU: europe-west4 → europe-west1
- APAC: asia-southeast1 → asia-northeast1
RTO Target: 15 minutes
RPO Target: Less than 1 minute
Performance
Our regional architecture ensures low latency:
- Intra-region p95 latency: < 200ms
- Edge caching with 60s TTL
- Direct regional endpoints available for latency-sensitive use cases
Questions about data residency?
Contact our security team at security@blazecrawl.dev or our enterprise team at enterprise@blazecrawl.dev.