.svg)
Rootly now syncs your Cortex catalogs straight into Rootly. Turn on the Cortex integration with an access token, pick which entity types to bring in (services, teams, domains, APIs, and more), and Rootly pulls those entities into matching catalogs for you. Cortex stays the source of truth, and Rootly updates automatically .
If you already have a catalog with the same name, like Services, your Cortex entities flow into it instead of creating a duplicate. Properties that come from Cortex are read-only in Rootly, so the two systems can't drift apart. You can still add your own Rootly-only fields, like a Jira board ID, on top of the synced data, and run a sync on demand whenever you need an update before the next daily refresh.
What's included
- Self-serve setup from the integrations page using a single Cortex access token
- Choose which Cortex catalog types to sync, or filter to entities in a specific group
- Cortex entities map into existing Rootly catalogs by name, or create new ones automatically
- Cortex-owned properties stay read-only to prevent data drift, while your Rootly-only fields stay editable
- Automatic sync every 24 hours, plus an on-demand manual sync
Why it matters
Your business is always changing. New services spin up, ownership changes hands, and people move between teams. When that structure lives in Cortex but your incident response runs in Rootly, the two drift apart and responders end up acting on stale information. Keeping Rootly in sync means responders always work from the current state of your services, teams, and ownership, and the impact of every incident is measured against how your systems are actually structured today.
Getting started
Anyone with integration permissions can set up Cortex from the Rootly integrations page. See the documentation to learn more.
