Cortex (internal developer portal)

Definition

Cortex is an internal developer portal that gives engineering organizations a searchable catalog of their services, along with scorecards that measure each service against standards for reliability, security, and ownership. It is designed to give both individual engineers and leadership a single view of what exists in a system, who owns it, and how well it conforms to internal best practices.

Overview

As organizations grow past a handful of services, keeping track of what exists, who owns it, and whether it meets baseline engineering standards becomes difficult without dedicated tooling, and the problem compounds quickly once responsibility for services is spread across dozens of independent teams. Cortex was built to solve this by combining a service catalog with a scoring system, giving teams a structured answer to questions like which services lack on-call coverage or which still run an outdated dependency. Mechanically, Cortex ingests metadata about services from source control, CI/CD systems, incident tools, and cloud infrastructure, then organizes that metadata into entities representing services, resources, and teams. On top of this catalog, it runs configurable scorecards, rule sets that check things like whether a service has a README, an on-call rotation, or passes a security scan, and aggregates the results into a score that can be tracked over time and compared across teams, with historical trend lines showing whether a given initiative is actually gaining traction. Cortex belongs to the same category as Backstage, Port, and OpsLevel, all of which provide a software catalog plus some notion of a maturity or quality score, but Cortex is delivered as a hosted SaaS product rather than an open-source framework a team must operate itself, which is the defining difference from Backstage. Relative to Port, which emphasizes a highly configurable self-service action layer, Cortex has historically put more emphasis on scorecards and engineering standards as its core workflow, treating the catalog as the anchor for measurable improvement rather than as a launchpad for provisioning actions. In practice, platform teams adopt Cortex to run initiatives such as a security compliance push or a migration off a deprecated framework, using scorecards to track adoption progress service by service and surface laggards to team leads. Engineers use the catalog day to day to find ownership information, dependencies, and documentation links for services they do not maintain themselves, reducing the need to ask around in chat, and engineering leadership uses aggregate scorecard views to report technical health up to the rest of the organization. The trade-offs are the ones common to any SaaS internal developer portal: it requires integration work to keep metadata current, its value is proportional to how disciplined an organization is about maintaining accurate ownership and tagging, and adopting it introduces both a subscription cost and a dependency on Cortex's roadmap. Smaller organizations, or those already invested in a self-hosted Backstage instance with mature internal plugins, may find the switching cost outweighs the benefit of moving to a hosted alternative.

Key Features

• Maintains a searchable catalog of services, resources, and teams
• Runs configurable scorecards against reliability and security standards
• Ingests metadata automatically from CI/CD and source control systems
• Tracks ownership and on-call responsibility per service
• Surfaces engineering initiative progress across many teams at once
• Provides dashboards for leadership visibility into technical health

Use Cases

Alternatives

Frequently Asked Questions

Related in DevOps