Not to brag, but... people love us.

“We had no solution to catalog all our services, so we didn’t know who owns what or which services are actually out there unless you go poking around in their repositories on Github. But now you can just say go to OpsLevel to easily gather that information”

"Implementing OpsLevel was a frictionless process–the team was very friendly, proactive, and helpful. They met with us to discuss our specific needs and gave us recommendations so that we could get maximum value as quickly as possible."

"You can put this on a billboard: OpsLevel has helped us manage our microservice sprawl. I'm a lot less concerned about reliability than I was before. It’s hands-down one of my favorite tools.”

It’s hard to calculate the impact of OpsLevel, because it’s like we grew an entire arm we didn’t have before. We can do things that were literally unthinkable.

By taking care of this day-to-day maintenance, OpsLevel frees up more time for our platform teams to actually support our product teams to build bigger and better Duolingo features.

"OpsLevel is a key piece of how our engineering org operates: it tracks ownership, gives visibility into the progress our teams are making on operational excellence, and even incentivizes that work by enabling teams that achieve higher levels of maturity to deploy faster."

"We’ve tried spreadsheets, Backstage, custom-built scorecard software, etc. None of them did everything we wanted, but OpsLevel finally built the tool that’s helping us meaningfully improve our ownership and service quality."

"OpsLevel was the only IDP that could impactfully move the needle on Developer Experience across our organization. With OpsLevel, we've been able to provide our engineering teams with centralized, reliable microservice metadata, and build automation and tooling that improves everyone's day-to-day."

Components has added an easy way to keep tabs on assets that aren't traditionally considered services here at BigPanda. It's also allowed us to progress with our goal to get components to the GP Ready maturity level. Having a simple view of these components has improved efficiency.

If we want to make a holistic change across say 60 different services, it's really good to be able to get that fast visibility. Which services have already adopted this, or are yet to? And then we can put a Campaign in place to set a timeline around what a migration should look like, give people access to the relevant information about how to perform such a migration, and critically why we want to do that. That was where we started to find Checks and Campaigns extremely helpful.

"OpsLevel is a crucial tool for our engineering and data science teams - tracking what’s out there, who owns it, and if it’s meeting our standards. We use it in our org-wide ops review meetings to quickly understand how teams are managing their applications from a testing, reliability, and security standpoint."

"The checks are the most valuable feature of OpsLevel. They enable projects to have consistency across teams and also provide automated quantitative measures that engage engineers in improving the codebase. Shortly after we make a request, 70-80% of our team has already responded and made the upgrade.”

"We didn’t want to choose a solution where we would have to manually enter information for each of our 40 microservices. So when I saw the OpsLevel Kubernetes Syncer, I knew that I would just have to do the work once, because they would all be in Kubernetes and tagged the same way."

"Ownership of our critical repos and services is an important part of our security and compliance requirements. OpsLevel tracks that ownership info and integrates with our existing tooling to ensure no security issue goes unowned."

"We didn’t need to already have a full inventory of our services to use OpsLevel, which would've actually been a bit of a problem considering where we were coming from. Having a tool that could help us fill in missing information excited us."

We never really standardized a definition of service health, and then once OpsLevel came along, we were able to define that more clearly and put it into common terms that everybody could talk about.

We needed something more mature for standards enforcement. With OpsLevel, we didn't have to run our own developer portal, and the Scorecards and standards features were well-developed. So we made the switch.

"In addition to deprecating legacy tech, OpsLevel has also helped push infrastructure projects across the company. We were able to map out what services were missing, as well as get a status of each service. Using checks to track down legacy services, we were able to upgrade them to be compatible with the rest of our technology stack."