Book a demo

Your portal to better software awaits

OpsLevel helps teams of all sizes move fast, without adding more manual upkeep.

"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."
Alex Ianus
Engineering Manager, Infrastructure

Book a call

Tell us about you
1
Choose a time
2
Talk to us!
3
Testimonials

What our customers say

"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."
David Goaté
Co-founder & Chief Architect
"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."
Albert Strasheim
VP Engineering - Infrastructure
"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.”
Leonardo Gallardo
Lead QA Engineer
“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”
Mickey Wu
Architecture Engineering Manager
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.
Drew McAuliffe
Senior Architect, Keller Williams
"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."
Alex Turek
Principal Engineer
"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.”
Kelvin
Senior Engineering Manager, Platform Operations
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.
Kieran McStay
SRE, BigPanda
"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."
Richard Luong
Engineering Manager
"OpsLevel has transformed our immediately-obsolete spreadsheets into an interactive and self-documenting system where teams can immediately identify what assets they own are out of compliance, what work they need to do to get into compliance with our standards, who owns services, and more."
David de Regt
Senior Director, Foundations Engineering
"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."
Alex Ianus
Engineering Manager, Infrastructure
"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."
Shawn Wowk
Manager of Development Operations
"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."
Yahel Agassi
Cloud Architect
"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."
Maciej Sobkowiak
Principal Site Reliability Engineer
"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."
Ben Johnson
SVP, Engineering
Your questions, answered

Frequently asked questions

How does Service Detection work?

We set rules and criteria to determine what constitutes a “service” in your repositories. Then, once you integrate your git provider(s), we will pull everything that meets these criteria into OpsLevel, consolidating everything we find into a proposed catalog.

What is Service Detection?

Service Detection identifies all services within your git repositories and pulls them into OpsLevel as suggested catalog objects or items—making it faster and easier than ever to get started. Learn more about Service Detection in our docs.

What if Service Detection suggests something that I don't want in my catalog?

You will need to approve or ignore each entry we surface—you can do this individually or in bulk. If you ignore a service, it goes into an ignored state that can be revived later.

How is Service Detection different from Discovered Services?

Discovered Services uses a webhook in your CI pipeline to monitor what it’s being deployed to. Service Detection monitors everything in your git repo(s) to identify and entire catalog, whether or not a deploy is happening.

What is AI in OpsLevel?

OpsLevel’s AI assistance generates automated service descriptions using the contents of your repository files and data from across your services architecture.

What are the benefits of inferred service descriptions?

Many services are missing descriptions in OpsLevel. This information offers critical context for broader engineering teams, but motivating service owners to keep them updated is a chore. With AI-generated service descriptions you get meaningful context added to your catalog automatically, without the hassle.

How do I get access?

The feature is currently disabled by default on all existing customer accounts. As of Thursday, October 12, 2023, it will be enabled by default for new accounts. Access to the feature can be turned on (or off) at any time through the settings panel in your account.

How does it work?

In addition to OpsLevel’s typical code-scanning functionality, we’re using a large-language model hosted by OpenAI. If this feature is enabled, your repository contents could be submitted to the OpenAI API for analysis. OpenAI will read any repository content; it prefers documentation, but it will also read code.

We then leverage OpenAI’s GPT o1 and o1-mini to generate proposed service descriptions for any catalog entity missing one, based on the context it’s found in your linked repositories. 

How can OpenAI use my data?

We have an agreement with OpenAI that none of your code is stored at rest permanently. Per OpenAI API Data Usage Policies, OpenAI will not use your data to train their models.

The agent transiently scans your documentation and code and uses it to make an inference about what a service’s description should be.

Similar to our repo checks, after computing a result, the original input code and documentation is eventually discarded.

What is OpsLevel's privacy policy?

We care deeply about who has access to your code and where it is stored. We handle your data in accordance with our Privacy Policy and data protection regulations. As always, our complete subprocessor list is available on our trust portal.

What is docs-as-code?

Documentation as Code (docs-as-code) refers to the philosophy of writing documentation with the same tools as code. It also means doc writers (developers themselves or dedicated technical writers) follow the same workflows as development teams. This approach can be applied to internal and external software documentation. Learn more about docs-as-code here.

What is OpsLevel?

OpsLevel is an internal developer portal that gives teams self-service access to the tools and knowledge they need to move faster without sacrificing standards. Engineering leadership at some of the best companies in the world rely on OpsLevel to help them drive standardization while improving developer experience and efficiency.

How does Service Creation work under the hood?

With Service Creation, Platform/SRE teams are able to define reusable templates that contain all the necessary scaffolding to set up a new service. Developer teams can then use these templates by entering in template variables to configure their service. This accelerates the pace at which developer teams can get started, while allowing platform teams to encode best practices and organizational standards into the services right from initial creation. Learn more about this in our docs.

My organization isn't using a docs-as-code approach. Can we still use Tech Docs?

You must be storing your internal docs in a git repo that's integrated with OpsLevel in order to use this feature. But our Checks and Campaigns can help you drive this change within your organization—your developers will thank you!

Do developers need to install any tooling or require additional access to use Service Creation?

No, there is nothing for developers to install or maintain locally. They only need access to OpsLevel. Learn more about the benefits of Service Creation on our blog.

What languages or frameworks does Service Creation support?

Cookiecutter is entirely language agnostic. Templates can be defined to create new services of any kind.

Is Tech Docs a solution for external, public facing documentation?

No. Tech Docs is designed strictly for internal docs. Only authenticated users of your OpsLevel instance will be able to access Tech Docs.

How is OpsLevel priced?

OpsLevel is priced based on the number of developers using the portal. We also can customize pricing within your unique needs and offer volume discounts. Please book a meeting to learn more.

How are templates defined and exposed in OpsLevel?

OpsLevel admins can import any Cookiecutter template into their OpsLevel template library. Template definition happens outside of OpsLevel, before a template is imported. Learn more in our docs.

Our internal docs already live in Confluence/Notion/Google Docs—how is Tech Docs different?

External docs solutions, or docs solutions that aren't designed for developers, tend to create silos. When information is siloed like this it often gets forgotten or goes stale.

With Tech Docs, the opposite happens. Your internal docs are centralized and live alongside all the important metadata in your service catalog, like ownership, dependencies, or Service Maturity level. Tech Docs are easily discoverable and searchable by all developers. Tech Docs are more visible to the entire organization, and so better updated and maintained.

What level of support do you offer?

We provide support over email, dedicated per-customer Slack channels, and via in-app chat.

What security standards does OpsLevel follow?

OpsLevel is SOC2 Type 2 certified. More details are available on our security page.

What happens after I request a meeting?

If OpsLevel is a potential fit for your organization, we’ll book a session with someone from our team. During the meeting, we can give a quick look at the product, dive into the problems you're trying to solve, and answer any questions you might have.