Enterprise
For the API that other companies build businesses on.
When your API is a dependency in someone else's production, the questions change: where does the data live, who is on call, what happens at renewal, and can your security team read the architecture before signing.
- 30 daysTypical pilot length
- 4 hoursTarget first response on Scale
- 3Processing regions available
- 90 daysMaximum standard retention
Capabilities
What changes at this tier.
Private regions
A dedicated collector fleet and store in a region you choose, isolated from shared capacity, with its own maintenance window.
Self-hosted collectors
Run capture inside your own network. Only aggregate metrics and the wakes you choose to forward leave your boundary.
Contractual targets
Availability and support-response targets written into the agreement, with service credits and a quarterly report against them.
Named engineer
A solutions engineer who knows your architecture, joins your incident channel and runs a quarterly review with your platform team.
Procurement support
Security questionnaires, DPAs, subprocessor disclosure and architecture review sessions handled by people who can answer, not forward.
Flexible commercials
Annual invoicing in USD, EUR or GBP, committed-use discounts and a shared overage pool across business units.
How it goes
Four steps, roughly six weeks.
No procurement theatre. The pilot produces a written outcome that your team can take to a decision meeting.
- 01
Architecture call
Sixty minutes with an engineer. Your topology, your capture requirements, your constraints. No slides.
- 02
Scoped pilot
One environment, one region, thirty days. Real traffic, your own redaction rules, a written outcome at the end.
- 03
Security review
We answer your questionnaire, hold a review session with your team and provide the documentation your legal process needs.
- 04
Rollout
Environment by environment with your naming, your roles and your CI integration. The named engineer stays on after go-live.
Included
Enterprise
Private regions, contractual availability targets and a named engineer.
- Dedicated or self-hosted collectors
- Custom retention beyond 90 days
- Contractual availability and support targets
- Named solutions engineer and quarterly review
- Procurement, security review and DPA support
- Annual invoicing in USD, EUR or GBP
Bring your architecture diagram.
Sixty minutes with an engineer who will tell you honestly whether the pilot is worth running.