Integrations

Every tool. Every workflow. One place.

Connect your stack with 50+ native integrations or custom and community-built connectors. Then shape the data, dashboards and permissions to fit how your teams work.

Integrations

Native integrations, instant value

Native integrations for GitHub, Datadog, Kubernetes, Snyk and dozens more come with reliable, best-practice defaults out of the box. They're built for developer adoption and work the way your teams already do.

FireHydrant

FireHydrant helps engineering teams manage incidents with speed and clarity. By integrating FireHydrant with OpsLevel, you can display real-time incident status alongside the full context of your services. This ensures your teams always know which systems are impacted and how incidents map to your service catalog.

GitHub Advanced Security

GitHub Advanced Security includes the ability to search for potential security vulnerabilities and coding errors in your code using CodeQL. GitHub makes extra security features available to customers under an Advanced Security license. This integration allows OpsLevel to our GitHub integration provides the option to sync code scanning alerts from GitHub Advanced Security into your catalog. This feature powers code issue checks and populates code issues and code issue projects on your repositories and services while giving you the option to extend functionality with Custom Integrations and Data Mapping. By leveraging this, you can ingest additional metadata, map custom fields, and create richer relationships between GitHub Advanced Security data and your OpsLevel service catalog.

Rootly

Rootly automates incident management, helping teams coordinate response and remediation with speed. By integrating Rootly with OpsLevel, you can automatically link incident timelines and actions to the services they impact. This brings valuable operational context into your catalog and ensures your teams can connect the dots between incidents and services.

Through Custom Integrations and Data Mapping, you can extend Rootly’s integration to ingest richer metadata, track service ownership during incidents, and streamline post-incident analysis.

‍

Incident.io

Incident.io is an incident response and management platform.

Google Cloud Platform (GCP)

GCP powers modern infrastructure with scalable compute, storage, and data services. By integrating GCP with OpsLevel, you can automatically ingest and map your cloud resources to services in your catalog. This provides clear visibility into what’s running in GCP and how it relates to your service ecosystem.

With Custom Integrations and Data Mapping, you can extend the GCP integration to include additional metadata such as labels, billing data, and service usage — creating a richer foundation for operational excellence.

‍

Azure Infrastructure

Azure provides enterprise-ready cloud services for infrastructure, applications, and AI. With OpsLevel’s Azure integration, you can import infrastructure objects and service metadata into your catalog. This helps teams maintain visibility, enforce best practices, and reduce operational risk.

Using Custom Integrations and Data Mapping, you can extend the integration further by ingesting metadata from resource groups, policies, and configurations — helping you align Azure usage with organizational standards.

‍

Check out all of our native integrations

Custom integrations

Bring in data from any system

Some of your most important tools aren't on any marketplace. Custom integrations pull data from any API or take it in through a webhook, then map it into your catalog with a short YAML config. You can see exactly what data moves between OpsLevel and your tools, in both directions, and how each record was mapped.

  1. 1

    Data flow

    Push data in from a webhook or API, or let OpsLevel poll the tool's API on a schedule.

  2. 2

    Extract

    Set up HTTP polling, authenticate with OAuth or an API key, and define the rules for what to pull. OpsLevel stores the raw data.

  3. 3

    Transform

    Map fields onto your data model, create objects and link relationships.

    38 services updated2 records skipped, no match

Custom properties

Catalog anything

Services, infrastructure, databases and anything else you run. Define the properties you need to capture so nothing important slips through. Your rules, your structure.

This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.

Custom properties

ServicesDatabasesQueues
PropertyTypeExample
tierEnum1, 2 or 3
pci_scopeBooleantrue
cost_centerTextCC-4120
runtime_versionTextgo 1.23
Tagsteam:paymentsregion:us-eastlifecycle:ga

Dashboards

Dashboards that match how each team works

Arrange reports and data with a drag-and-drop editor. Embed third-party data, put key metrics first and remove anything your team doesn't need.

This is some text inside of a div block.
This is some text inside of a div block.

Engineering overview

Editing
Scorecard level by team
Payments
Identity
Search
Open security issues
7
2 critical, from Snyk
Services without owners
0
Down from 14 last quarter
Drop widget here

Access control

Roles built for how teams own software

Control who can view or edit each part of OpsLevel. Team members can only edit the services they own, so responsibilities stay clear and developers can build without putting other systems at risk.

This is some text inside of a div block.
This is some text inside of a div block.

Roles and permissions

RoleView catalogEdit servicesManage checksManage integrations
Admin✓✓✓✓
Team member✓Owned only--
Security reviewerCustom✓-✓-

Payments can edit checkout-api because they own it.

Fast to set up, flexible as you grow

Unified visibility

See CI builds, incidents, security issues and more in one catalog.

Developer velocity

Less switching between tools. Developers get the context they need right away.

Room to grow

Shape the data model to fit your teams without taking on extra engineering work.

Frequently asked questions

How many native integrations does OpsLevel have?

More than 50, including GitHub, Jenkins, Jira, Datadog, Kubernetes and Snyk.

What if a tool isn't supported?

Build a custom integration. Push data in through a webhook or API, or have OpsLevel poll the tool's API, then map the data into your catalog with a YAML config.

How do custom integrations authenticate?

With OAuth or an API key.

Can I add my own fields to the catalog?

Yes. Define custom properties, tags and attributes for services, infrastructure, databases or any other component type.

Can I limit who edits what?

Yes. Role-based access control lets you decide who can view or edit each part of OpsLevel, limit edits to the services a team owns and create custom roles.

Start today

Connect your whole stack to OpsLevel