📢 Request access to the Open Beta

Launching our Open Beta

António Araújo
|
April 13, 2022
|
3
min read
SLO Platform Open Beta Launch | detech.ai

tl;dr — We’re excited to announce that we are launching our Open Beta to the public. detech.ai makes it easy to stand up a Reliability Intelligence platform quickly. Our product will help: (a) decrease reliability issues that impact your business, (b) make engineers happier at work, and (c) increase development pace. Request access here

‍

Today, detech.ai announced the launch of its Reliability Intelligence platform in Open Beta. Users may now bring their existing observability tools and create SLOs in minutes based on out-of-the-box SLI recommendations. Soon, they will be able to define SLOs as code, automate rollbacks, among many other things (our roadmap is packed!). 

‍Check what we’ve been working on last quarter

We've heard from numerous users that they'd like to get started with SLO monitoring without the hassle of having to learn new tolling or complex formulas. detech.ai will both (1) bring the big picture visibility necessary for decision-making over reliability decisions, and (2) accelerate root-cause analysis (RCA) by providing a detailed view over an issue’s impact across user-journeys, services, products, and more. Additionally, through looking at the increase of engineers changing jobs due to alert fatigue, we can see that there is a strong desire for smarter incident management that minimizes the need for human input on non-business critical issues or false positives.

As the detech.ai platform is in Beta, we are looking for your feedback and use-cases that you'd like covered. Please request access here, give us feedback either through our Community Slack Group or via email at hello@detech.ai.

‍

Frequently Asked Questions

‍

1. What is launching today?

Today, detech.ai is launching its Reliability Intelligence platform in Open Beta: an easy and intuitive way for engineering teams to start leveraging Service Level Objectives at scale.

‍

2. Who’s behind detech.ai?

We are a startup from Lisbon, Portugal, check out our team here! We have amazing advisors and investors backing us as well, such as Techstars NY, TheVentureCity, and Shilling Capital. 

‍

3. How much does this cost?

Participation on the Open Beta is completely free for a limited period of time. Contact us to learn more. 

‍

4. How much will detech.ai cost after the Open Beta?

We’ll have flexible pay-as-you-go plans fit for all sizes. For now we’re choosing to share post-Beta pricing with registered users only. 

‍

5. How do I get access to the detech.ai platform?

Please take one minute to request access using this form. 

‍

6. What can I do with detech.ai?

Currently, as we launch the Open Beta, users can:

  1. Integrate your existing observability stack (Prometheus, New Relic, AWS, GCP, etc.) in minutes, no need to change instrumentation setup
  2. Define SLOs based on out-of-the-box SLI recommendations or custom built, giving dev teams ownership and visibility of how they’re contributing to the user experience
  3. Assess user experience in real time, per journey/customer/service/endpoint or any other dimension you’d like
  4. Make data-driven decisions regarding your reliability investments. (e.g. deciding between developing new features vs. tackling technical debt)

‍

7. What is a Service Level Objective (SLO)?

In a nutshell, an SLO is a reliability target or objective for a particular indicator. The indicator, also known as Service Level Indicator (SLI), represents the behavior of a certain service, product, user journey, from a particular point of view (availability, latency, throughput, etc.). In our blog Monitoring on SLIs and SLOs we explain this topic in detail.

‍

8. What are the benefits of SLOs?

SLOs provide many benefits to an organization, such as: 

  1. Data-driven indicators to be used in development & operational processes and decision-making
  2. Putting the focus of reliability monitoring on the customer experience and business-critical user journeys
  3. Enabling each team to understand their role in meeting the expected reliability goals
  4. Helping to prepare for failure and having different stakeholders agree on what the acceptable failure rate is, creating the concept of error budget
  5. Looking at reliability performance not as a black-box or a fuzzy concept but as standardized and easy-to-understand KPIs

‍

‍

Signup to Our Newsletter
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
By registering, you agree with the processing of your personal data by detech.ai as described in our Privacy Policy.
On this article
Frequently Asked Questions