Keep an automated record of truth
Unify your entire tech stack
Restoring knowledge & generating insight
Measure and improve software health
Action on cross-cutting initiatives with ease
Get actionable insights
Spin up new services within guardrails
Empower devs to do more on their own
Tap into API & Tech Docs in one single place
Set and rollout best practices for your software
Build accountability and clarity into your catalog
Free up your team to focus on high-impact work
We support leading engineering teams to deliver high-quality software, faster.
Explore our library of helpful resources and learn what your team can do with OpsLevel.
Resources, tips, and the latest in engineering insights
Practical resources to roll out new programs and features
Videos of our product and features
Live and on-demand conversations
See OpsLevel in action
Flexible and designed for your unique needs
Everything you need to deliver a better developer experience
OpsLevel contains a ton of information about your technical services and systems, but it doesn’t contain all of the information about your business. Fortunately the data in OpsLevel isn’t trapped there! In addition to our existing GraphQL API, we now support extracting all of your OpsLevel data into your ETL pipeline and data warehouse.
We all know that naming things is one of the two hardest problems in computer science (along with cache invalidation and off-by-one errors.) Naming your microservices is extra hard, as they’re almost like children: they’re practically these living, breathing things that you birth into the world and do your best to make sure they’re set up for success in life (i.e. in production.) Ok, perhaps people don’t agonize over the names of their microservices as much as the names of their children, but it’s still a big enough decision.
Last summer, our team gathered in the woodland heart of Parry Sound, Ontario for the inaugural OpsLevel HackDay. For 24 hours, participants were given total creative freedom while being tasked with creating a demo-able, team-based project. Skills were sharpened, bonds were strengthened, and marshmallows were roasted - it was a blast.
Pranav Krishnan is a Computer Science student at the University of Waterloo. I first started working at OpsLevel in May 2019 and it was my first ever co-op experience. I was extremely nervous, with no clue what to expect. Fast forward almost a year later and I find myself struggling with the idea of leaving this company behind.
OpsLevel is a great place to work. I love the product, the values…the snacks, but most importantly, the people. Our team isn’t large, but our size makes us extremely tightly knit. We eat lunch together, play lunchtime foosball, chat about things like kids and mortgage rates, and play after work video games (mostly Rocket League) almost every day.
A microservice catalog is only as good as the data it contains. OpsLevel is making it easier than ever to keep your service list up-to-date with its new Service Suggestions feature. With Service Suggestions, we automatically discover new services when they get deployed and help you add them to OpsLevel. For services that are already in OpsLevel, we can also help you easily attach those deployment streams to the right service.
Don’t you hate remembering all of your passwords? With OpsLevel’s Single Sign-On integration all of your microservice data is seconds away without the need for another long and secure password.
OpsLevel is intended to be your source of truth for microservice and ownership information. Today, we’re very excited to announce that we’ve taken a leap forward towards that vision with the launch of our GraphQL API.
Services and repositories come in many shapes and sizes. You can fully extend OpsLevel’s data model to fit your needs by tagging your services and repositories with key/value pairs. With our Tags feature, OpsLevel can track additional or custom attributes, as well as allow you to search and filter by these attributes.
OpsLevel is your one-stop shop for understanding the microservices you have running in your architecture. A key component to understanding your microservices is to actually see what code is running in production, and when/how that changes.
OpsLevel just completed its inaugural HackDays and company getaway. We all piled into a few cars and drove up to a beautiful cottage near Parry Sound, Ontario. Surrounded by some of Canada’s best scenery of trees, lakes, and trails, we first set about for 24 hours of programming. Given our geography, we thought about calling the event “Hack the North”, but that name is taken, so “OpsLevel HackDays” it is.
At OpsLevel, we’re big fans of the 2015 MacBook Pro. The newer 2019 MacBook Pro has some great features like Touch ID, 32 GB RAM, and USB-C power delivery that you can plug on either side. Unfortunately, it also suffers from a failure prone butterfly keyboard design and the dreaded Touchbar. The 2015 MacBook Pro was the last model manufactured by Apple before the switch to Touchbar and and the butterfly keyboard.
OpsLevel is a fantastic source of truth for all of the information around the microservices in your architecture, including all the tools you use to operate each of your microservices. But it’s not always the easiest to find and discover this information when you really need it - say during a major incident, or during a gameday.
So, OpsLevel is cool and all, but you know what’s not cool? Clicking around in a UI whenever you want to change some of the properties of a service. Well click no longer! Now, with our Git Repository Integration, all you need to do is to plunk down an opslevel.yml file at the root of one of your repositories and OpsLevel will use that to populate the corresponding service on OpsLevel’s side. (If the repository isn’t already mapped to a service, OpsLevel will create a new one.)
With our Git Repository integration, OpsLevel can continuously scan your code repositories and verify all of the operational best practices you’ve defined. Previously, we’ve shown you a Repo File Check, which can be used to verify that a given file exists in your repo, or verify that it contains some specific text.
After setting up a Git Repository Integration, OpsLevel can continuously scan your code repositories and verify all of the operational best practices you’ve defined. Along with the integration comes two new checks: the Repo File Check and the Repo Search Check.
You likely use a myriad of cloud-based tools to operate your services. At OpsLevel, part of our master plan is bringing various data points from all of these tools to help you gain insights and build more reliable software. We’re proud to announce our latest step on this journey with our new Github and Bitbucket integrations.
OpsLevel has become a lot more powerful with the addition of our newest features: Checks and Checklists. Now you can actually codify your best-practices around building and operating microservices and then view how these practices are being followed across your entire architecture.
Always ship and run production-ready services. Without the manual checklists.
Learn how to run more reliable, secure services in production.