Software reliability platform company Nobl9 has released a channel program for systems integrators and solution providers to address the opportunity around service level objectives (SLOs). An SLO is an agreement on a certain measure such as an uptime or response time within the SLA.
Originating from the same area of Google’s reliability engineering (SRE) and DevOps as popular containers and Kubernetes, SLOs are a unit of reliability that provides a more quantitative and real-life way to measure reliability of services than traditional techniques such as service level agreements (SLAs).
Nobl9 has revealed its eight initial partners with its channel program, including Accenture as its first global integration system and ITSM Partner for the Year at Atlassian 2020, Isos Technology.
Michael Lauricella, Partnership Director at Noble9 is leading Nobl9’s channel program. “Adopting service level objectives as the standard metric for service reliability is the next big wave in DevOps,” said Michael Lauricella. “Enterprises that embrace Agile development understand the limitations of service level agreements, and that the modern DevOps cycles require a much more crucial understanding of how reliability is actually impacting customers. Nobl9 is working with global systems integrators and channel players that share our vision that SLOs will become the de facto unit for how developers, operations and business teams communicate reliability. This program formalizes the services and reseller agreement that we offer to partners to pursue high margin opportunities as SLO adoption takes off worldwide.”
Service Level Objective Strategy
In 2019, Nobl9 was established to codify reliability based on service level objectives (SLOs). Through its former start-up Orbitera’s acquisition by Google, the founding team of Nobl9 says it has gained experience in building a new, fundamentally more accurate and meaningful lingua franca for the control of system health in the reliability of its cloud services around SLOs that developers, reliability technicians and product owners have.
Nobl9’s reliability platform makes SLOs definable and consumable for the masses -conquering the hardest challenges for creating SLOs and error budgets (integration, data, alerting, math, and in-house/cultural obstacles. It would give enterprises a reliability heartbeat that can lead to superior service health observability and more informed decision-making.
“Almost every software organization has a set of common challenges that inhibit great customer experiences and increase costs,” said Stephen Elliot, Program Vice President, Management Software and DevOps at IDC. “Adopting SRE principles and a service level objective strategy can help reduce these pain points. They put the focus on the user, reducing political inertia and streamlining a vast array of internal, often opinion-driven discussions.”
Nobl9’s Partners Speaking About the Program
“Our clients are faced with many challenges during their SRE journeys, and Nobl9 provides several features to accelerate their efforts,” said Marco Torre, Senior Manager, Tech Strategy & Advisory at Accenture. “It simplifies the management of service level objectives through 3rd party monitoring integrations as well as providing real-time and historical reporting. SLOs-as-Code and error budget visualizations help teams realize the benefits of SRE quickly and with less effort.”
“Over the past 10 years Isos Technology has worked with hundreds of companies who modernized their software development approach through Agile methodology and Atlassian technologies. We see service level objectives as the next big wave for developer productivity,” said Thad West, CEO and co-founder at Isos Technology, Atlassian’s 2020 ITSM Solution Partner of the Year. “SLOs give developer teams a stronger, math-based framework for modeling expected behavior of software in terms of user outcomes, and a baseline software reliability metric that the entire business can understand. Through our services partnership with Nobl9, we are seeing massive interest from Agile teams to implement SLOs.”
