Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

OpenSLO

openslo.com

  • Free plan
  • Windows
  • macOS
  • Linux
7.6 Club score Visit openslo.com

Apache License 2.0

Free

Open source

What the maker publishes

Alert destinations
Alert notification targets are implementation-specific, and the examples include email, Slack, a webhook, and Opsgenie. source
Alert limit
An alert policy allows only one alert condition, which is a burn-rate comparison. source
Budgeting methods
An SLO must use Occurrences, Timeslices, or RatioTimeslices budgeting. source
CLI platforms
The Oslo release configuration builds Windows, Linux, and Darwin binaries for amd64 and arm64. source
Go SDK status
The Go SDK decodes, validates, and encodes OpenSLO objects, is still in active development before v1, and expects breaking API changes. source
Metric integrations
Data source type is implementation-defined, with Prometheus and Datadog given as examples, and connection details may include endpoints or authentication. source
Name limit
Object names must be 1 to 63 characters and match an RFC-1123 label. source
Object model
Version 1 defines Service, SLO, SLI, DataSource, AlertPolicy, AlertCondition, and AlertNotificationTarget objects. source
Oslo CLI
Oslo validates and formats OpenSLO YAML and JSON locally or in CI/CD, and it can be installed with prebuilt binaries, Go, Homebrew, Docker, or from source. source
Scope limit
Platform-specific implementation details are outside the specification, which is meant to stay vendor-agnostic, Kubernetes-YAML compliant, and extensible. source
SLOs as code
Users define thresholds, metrics, and goals for applications and infrastructure in a Git-oriented workflow. source
Support
Contributions are reviewed by maintainers, and community discussion is directed to the Slack linked from openslo.com. source
Vendor neutrality
The specification is implementation neutral so multiple vendors and projects can share SLOs in one format. source
What it is
OpenSLO is a YAML language for declaring service level objective reliability and performance targets. source
Who it is for
It is aimed at the reliability engineering ecosystem and at organizations that create, operate, and run cloud services and applications. source

Checked against the maker's pages on 14 Nov 2026.