SLOs by Customer Segment

Different SLOs for different customers.

Why segment SLOs

Customers are not equal. Premium tier paying $5k/month deserves tighter availability than Basic tier paying nothing. A single SLO across all customers averages the experience and hides the asymmetry.

Segmented SLOs let you commit different reliability tiers in pricing. A reliability SLA becomes a real product feature: pay more, get tighter availability. Without segmentation, every customer gets the same effort.

Operational priority follows segment. During incidents, free-tier degradation may be acceptable; premium degradation may demand all-hands response. SLOs encode this priority explicitly.

How to structure segment SLOs

Tag every request with customer segment at the edge. Authentication layer or API gateway adds a header. Downstream metrics carry the segment label.

Define per-segment availability and latency SLOs. Premium: 99.95% availability, p99 < 200ms. Standard: 99.9% / p99 < 500ms. Free: 99% / p99 best-effort.

Cardinality matters. Three to five segments works; ten segments creates dashboard sprawl and metric cardinality cost. Pick the segments that map to commercial commitments, not marketing personas.

Operating segment SLOs in production

Per-segment dashboard. Each segment's SLO health visible. Burn rate alerts per segment. Cross-segment correlation visible during incidents.

Capacity planning per segment. Premium segment may need dedicated capacity, separate connection pools, prioritised queue lanes. The SLO drives the architecture.

Incident triage looks at per-segment impact first. Sev 1 if premium is degraded, sev 2 if only standard. The severity rubric encodes the segmentation.

Trade-offs and gotchas

Maintenance burden. Each segment is another set of dashboards, alerts, runbooks. Don't add segments unless they correspond to real commercial differences.

Internal-only segments are usually a mistake. Engineering convenience is not a customer commitment. Stick to segments that match contracts.

Metric cardinality cost. The segment label adds a multiplier to time series count. At high volume this translates to real observability bill increases.

When to add segment SLOs

Add when pricing tiers exist with reliability commitments. Without that, segmentation is optics, not policy.

Add when premium customers complain about reliability that aggregate metrics show as fine. The segmentation surfaces what the premium customer experiences vs the average.

Don't add for engineering convenience. Don't add when the team is already drowning in operational complexity. Wait until pricing or contracts demand it.