| The service | Available, fast, correct and secure to the service levels of your plan | Choosing the plan your use needs |
| Your keys | Never seeing a live key after it is created; revoking within a minute of your request | Keeping keys in a secret store; rotating them; scoping them narrowly |
| Network | The edge and everything behind it | Your network to the edge; private connectivity on your side |
| Your data | Keeping none of it; processing it only in your jurisdiction | Sending only what is needed; naming series opaquely; keeping the mapping |
| Segments | Returning them deterministically per profile version | Storing them; drawing them; deciding what they mean for your users |
| Real-time | Answering the same edge and bars with the same result; keeping nothing; delivering events at least once | Storing segments and edges in one write, one writer per series; resending unchanged on retry; deduplicating events |
| Failover | Moving your traffic within the plan's recovery time | A client that resends unanswered requests and reconnects (Resilience) |
| Capacity | Provisioning your plan's figures; adding more within 10 business days of notice | Telling Patternode before you go beyond them |
| Change | Releasing safely, outside your blackout periods | Setting blackout periods; reading the changelog; pinning profile versions where you need to |
| Incidents | Detecting, communicating and reporting as Support says | Watching the status page; opening Severity 1 by phone |
| Compliance | The assurance in Compliance | Your own regulatory obligations |