> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rootly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cortex

> Integrate Rootly with the Cortex Internal Developer Portal to combine entity insights, ownership data, and automated incident management in one workflow.

## What is Cortex?

Cortex is the Engineering Operations Platform that enables organizations to continuously improve their operational maturity and reduce developer friction. With centralized visibility, clear ownership, automated Scorecards, and golden paths, we help engineering organizations operate as one.

## Integration Overview

The Rootly + Cortex integration is **bidirectional**, meaning data flows in both directions to create a seamless experience:

<CardGroup cols={2}>
  <Card title="Cortex to Rootly" icon="download" href="/integrations/cortex/cortex-to-rootly">
    Sync your Cortex Catalogs into Rootly
  </Card>

  <Card title="Rootly to Cortex" icon="upload" href="/integrations/cortex/rootly-to-cortex">
    Display Rootly incident data within Cortex portal
  </Card>
</CardGroup>

## How It Works

### Cortex → Rootly (Catalog Sync)

Rootly imports your Cortex catalogs, making Cortex the **source of truth** for your Catalog data in Rootly.

**What gets synced:**

* Cortex entities become Rootly entities, including all properties
* Changes made in Cortex are synced in Rootly

[Set up Cortex → Rootly integration →](/integrations/cortex/cortex-to-rootly)

***

### Rootly → Cortex (Incident Display)

Cortex pulls incident data from Rootly and displays it within your Internal Developer Portal.

**What you can do:**

* View active incidents on service pages in Cortex
* Create Rootly incidents directly from Cortex
* Build scorecards based on Rootly incident metrics
* Track service reliability using incident data

[Learn about Rootly → Cortex integration →](/integrations/cortex/rootly-to-cortex)

## Key Benefits

### Unified Catalog

Use Cortex as your single source of truth for your Rootly Catalog. When you update an entity in Cortex, the changes automatically flow to Rootly, ensuring consistency across your incident management workflow.

### Reduced Context Switching

Developers and on-call engineers can stay in Cortex while accessing incident information. Create incidents, check incident history, and view operational metrics without switching tools.

### Automated Service Ownership

Leverage Cortex's ownership data to automatically route incidents to the right teams. For example, when an incident affects a service, Rootly knows exactly who owns it based on Cortex's catalog.

### Data-Driven Reliability

Build Cortex scorecards using Rootly incident data to measure and improve service reliability. Track MTTR, incident frequency, and operational maturity across all your entities.

## Which Integration Do I Need?

**Both!** The integrations work together to provide the complete experience:

| If you want to...                 | You need...                                                                  |
| --------------------------------- | ---------------------------------------------------------------------------- |
| Keep entities in sync             | [Cortex → Rootly](/integrations/cortex/cortex-to-rootly)                     |
| View incidents in Cortex portal   | [Rootly → Cortex](https://docs.cortex.io/docs/reference/integrations/rootly) |
| Link incidents to Cortex services | [Cortex → Rootly](/integrations/cortex/cortex-to-rootly)                     |
| Create incidents from Cortex      | [Rootly → Cortex](https://docs.cortex.io/docs/reference/integrations/rootly) |
| Build reliability scorecards      | [Rootly → Cortex](https://docs.cortex.io/docs/reference/integrations/rootly) |

<Info>
  The **Cortex → Rootly** integration is configured in Rootly. The **Rootly → Cortex** integration is configured in Cortex and maintained by the Cortex team.
</Info>

## Getting Started

### Step 1: Sync Entities from Cortex

Start by [setting up the Cortex → Rootly integration](/integrations/cortex/cortex-to-rootly) to import your catalogs. This lets you build your incident response process around your business entities as defined in Cortex.

### Step 2: Display Incidents in Cortex

Next, configure the [Rootly → Cortex integration](https://docs.cortex.io/docs/reference/integrations/rootly) in Cortex to display incident data within your portal.

### Step 3: Leverage the Combined Power

Once both directions are configured:

* Entities in Rootly stay in sync with Cortex
* Incidents in Rootly appear on entity pages in Cortex
* Teams can work from either tool seamlessly

## Support

### For Entity Sync (Cortex → Rootly)

This integration is built and maintained by Rootly.

* Contact Rootly support through your account
* Visit [Rootly documentation](https://docs.rootly.com)

### For Incident Display (Rootly → Cortex)

This integration is built and maintained by Cortex.

* Email: [help@cortex.io](mailto:help@cortex.io)
* Visit [Cortex integration docs](https://docs.cortex.io/docs/reference/integrations/rootly)