Skip to content
BENIBIX Learn

SLO vs SLA

People use SLO and SLA as if they meant the same, and they do not. An SLO is the goal a team sets for itself, like 99.95% of requests working. An SLA is a promise in a contract with buyers, and missing it costs money. The SLA is set lower, so the team misses its own goal first and has time to act.

Infrastructure📟 Reliability

Service Level Objective (SLO)

The goal a team sets for a number it measures. An example is 99.95% of requests working.

A service level objective is the target a team sets for one SLI. It says how good is good enough, like 99.95% of requests working over 30 days. It is an inside goal, not a promise to customers. It is set a little stricter than any contract. That way the team gets a warning before a promise is broken.

Example
Jack's team sets an SLO of 99.95% for logins each month. When the SLI drops to 99.96% mid-month, they slow down new releases.
Why it matters
It tells a team when things are fine and when they need work. It does this before users start to leave.
Full entry
Infrastructure📟 Reliability

Service Level Agreement (SLA)

A promise in a contract on how well a service works. It says what you get if it fails.

A service level agreement is a promise to customers about how well a service will work. It is written into a contract. It names a level, like 99.9% uptime a month, and what happens if it is missed. Often the customer gets money back as credit. Because missing it costs money, it is set looser than the team's own goal.

Example
A host promises 99.9% uptime a month. In a 30-day month that allows about 43 minutes down. If it is down longer, buyers get a credit on their bill.
Why it matters
It is what buyers can hold you to. Breaking it costs money and trust.
Full entry

In one line

Service Level Objective (SLO)
The goal a team sets for a number it measures. An example is 99.95% of requests working.
Service Level Agreement (SLA)
A promise in a contract on how well a service works. It says what you get if it fails.