Enterprise tier

The platform that scales without losing the indie shape.

Same yourspace.yml, same one-command deploy. The Enterprise tier adds the procurement-side surface — auditor reports, named oncall, region-locked deploys, custom contract terms — without replacing the platform underneath.

SOC 2 Type II

Annual audit covering security, availability, confidentiality, privacy. Report + DPA + subprocessor list available under signed NDA. Anchored to NIST 800-53.

Region-locked deploys

Pin a site's bundle store and edge-function execution to a specific geographic set. Useful for residency requirements (EU-only, US-only) and for latency-sensitive customer cohorts.

Dedicated SE + 24/7 oncall

A named solutions engineer for onboarding, integration questions, and capacity planning. Named oncall rotation for incident escalation.

Custom contract terms

Annual contract; net-30 invoicing; volume-priced bandwidth + edge invocations; uptime SLA with credits. MSA + DPA + BAA on request.

Distributed tracing + chaos pipeline

Enterprise customers get the full distributed-tracing surface — OpenTelemetry traces flow through the proxy, the edge runtime, and the API tier; every request reachable by trace ID for 45 days. The same substrate drives the quarterly chaos exercises that surface drift between platform behaviour and customer-facing documentation.

Post-exercise reports are shared with Enterprise accounts under NDA before they land on the public status page; customers can map the timeline against their own observability data.

What the Enterprise contract typically covers

Volume bandwidth tier. Custom bands above the Team tier's 5 TB/month. Pricing is tiered + volume-discounted.
Edge invocations at scale. Custom invocation tiers above the Team tier's 50M/month, with per-route SLOs available on request.
Member seats. Unlimited seats; SSO integration (SAML 2.0, OIDC); SCIM provisioning. Audit-log export to your SIEM.
Uptime SLA. 99.95% target with credits below the threshold. Excludes customer-side misconfiguration; the platform's distributed trace identifies the boundary.
Support response times. Critical: 1 hour. Major: 4 business hours. Standard: 1 business day. Critical defined as a customer-visible outage on a production site.

Contact sales

Tell us about your traffic profile, residency requirements, and procurement timeline. We'll come back within one business day with a tailored quote and an introductory call slot.