Cortex beta program and release phases

At Cortex, we’re constantly building new features to improve operational maturity and reduce developer friction through engineering operations. Our beta program allows you to get early access to upcoming features, help shape their development, and provide valuable feedback before they reach general availability.

​

Release phases

Cortex uses a phased approach to release new features, allowing us to gather feedback and iterate based on real-world usage. Understanding these phases helps you know what to expect when trying out new features.

​

Current beta features

We’re currently running beta programs for several exciting features:

​

AI Impact Dashboard for GitHub Copilot (Public Beta)

Measure adoption and impact of AI coding tools, starting with GitHub Copilot, across your engineering teams. Learn more Key features:

• Team-level AI adoption correlated with delivery and reliability
• Impact of recent AI usage on engineering performance
• Detailed user-level AI adoption trends over time

​

OpEx Review (Public Beta)

OpEx Review is an AI-powered operational excellence review based on the DRIVE framework that turns your Eng Intelligence data into a recurring, narrated report. On a schedule you set, Cortex summarizes what changed since the last cycle and highlights the trends worth your attention, so leaders can spend less time assembling metrics and more time acting on them. Learn more Key features:

• Scheduled, narrated reports - Cortex generates a report on the cadence you choose and writes a plain-language overview of each cycle.
• Metrics organized by operational pillars - Related metrics are grouped into pillars, each with an AI insight explaining what the movement means.
• AI insights on every metric - Each metric includes its current value, the change from the prior period, its trend over time, and AI-generated insights that explain what’s driving the movement and how it connects to other metrics.
• Cortex AI chat (Research Preview) - Open a chat with Cortex AI about any metric; ask follow-up questions, dig into why a metric moved, and pull in related data without leaving the report. Learn more

​

Relationship graphs (Public Beta)

The redesigned relationship graph gives you a visual map of how an entity connects to the rest of your catalog. Instead of loading every entity at once, you start from a single entity and expand outward one relationship at a time, so you can trace dependencies, domain hierarchy, ownership, and custom relationship types without losing your place. The previous view is still available from the graph. Learn more Key features:

• Start from any entity - Pick an entity from the graph’s landing page, or click View in relationship graph on any entity’s details page to open the graph with that entity already selected.
• Expand on demand - Click the count badges on a node to load its parents or children, and choose which relationship types to show.
• Custom relationship types - Explore the relationship types your workspace defines alongside dependencies, domains, and ownership.
• Entity details side panel - See an entity’s relationships, add or remove relationship types from the graph, and refocus the graph on any related entity.
• Ownership inheritance at a glance - Edge styles show which owners are inherited and appended, and which are inherited as a fallback.
• Search and filters - Highlight matching entities with catalog search syntax, and filter by entity type, group, owner, team, domain, or AWS account and region.
• Shareable views - Copy a link to the exact graph you’ve built, including the nodes you’ve expanded.

​

Ownership Recommendations (Public Beta)

Cortex predicts owners with a machine learning model that matches services and service-like entities in your catalog with teams in your catalog. It draws on the structure of your entire catalog, including code contribution activity, the owners of related services, service names and descriptions, domain structure, service metadata, and connections to other tools, such as on-call and issue tracking tools. Learn more Key features:

• View all ownership recommendations in a single page.
• Accept or reject recommendations.
• Work with recommendations through the Cortex REST API and Cortex MCP.

​

Harness CD pipelines and deployments (Public Beta)

Cortex now imports pipelines and deployments from Harness and connects them to the services in your catalog. Service owners can see where each service deploys, whether each deployment succeeded, failed, or rolled back, and which version went out, with a link to the run in Harness. Learn more Key features:

• Pipelines and deployments on entity pages - View each entity’s Harness pipelines and deployment history, filtered by environment or infrastructure.
• Automatic service matching - Cortex links Harness services to entities by name, identifier, or cortex.entity tag. You can also register services in the entity YAML or from the entity’s details page.
• Workspace-wide view - See every imported pipeline and deploy on the Integrations › Data page.
• Eng Intelligence metrics - Harness deployments count toward deployment frequency, rollback frequency, and change failure rate.
• CQL and Scorecards - Write rules on Harness data with cicd.deployments() and cicd.pipelines().

​

Rootly on-call and incidents (Public Beta)

Cortex now imports on-call schedules from Rootly alongside incidents, and connects both to the entities in your catalog. Service owners can see who’s on call now and next, and which incidents affected their services, without leaving Cortex. Learn more Key features:

• On-call on entity pages - View who’s on call now and next for an entity, and see upcoming rotations in the My on-calls block on your homepage.
• Automatic matching - Cortex links Rootly services to entities by the Cortex ID from Rootly’s Cortex integration or by service name, and links on-call through each service’s escalation policy and each schedule’s owning team. You can also register services, schedules, and teams in the entity YAML or from the entity’s details page.
• Workspace-wide view - See every imported incident and on-call shift on the Integrations › Data page.
• Eng Intelligence metrics - Rootly incidents count toward incident frequency and mean time to resolution (MTTR).
• CQL and Scorecards - Write rules on Rootly incident and on-call data.

​

Cortex AI Chat (Research Preview)

Cortex’s AI-powered chat assistant answers questions about your engineering data in plain language and grounded in your real Cortex data. Open it beside whatever page you’re on with ⌘J, or give it a full page of its own for longer sessions. Learn more Key features:

• Ask from anywhere - A side panel that opens over your current page, plus a dedicated page with conversation history.
• Grounded in the page you’re on - Ask “who owns this?” on an entity or Scorecard page without naming it.
• Reaches your workspace - Catalog, Scorecards, Initiatives, Workflows, Engineering Intelligence metrics, the Cortex documentation, and more.

​

Join our beta program

​

Why join?

• Early Access. Be among the first to try new features before they’re available to everyone.
• Shape the Product. Your feedback directly influences feature development and prioritization.
• Exclusive Perks. Beta participants may receive special recognition, early access to future features, or other benefits.
• Direct Collaboration. Work closely with our product team to ensure private beta features meet your needs.

​

How to join

1. Review the current beta features listed above to see what interests you.
2. Try out any public beta features already enabled and provide any feedback through the link on the feature’s public beta banner.
3. Click Request Access on any private beta feature you’d like to try.
4. Fill out the brief form to tell us about your use case.
5. We’ll review your request and follow up within 3-5 business days.

Not all requests can be accommodated for private beta features due to capacity constraints, but we’ll do our best to include as many participants as possible.

​

What we ask of beta testers

• Provide Feedback. Share your experiences, both positive and negative, through our feedback channels.
• Report Bugs. Help us identify issues by reporting them promptly with detailed information.
• Be Patient. Beta features may have rough edges or change during the testing period.