Operations | Monitoring | ITSM | DevOps | Cloud

Our first turnkey dashboard gives you a real-time pulse on engineering health. Every chart is interactive: click any bar or data point to drill down into the underlying PRs, commits, or incidents. And we’re just getting started; more dashboards are already on the way!

Today we’re thrilled to announce the launch of Entity Relationships, a powerful new capability that gives you more flexibility and control over the data model in your IDP. By allowing you to create custom relationships between entities in your catalog, you can model your internal developer portal to accurately reflect your own organization’s taxonomy, letting you better answer deep questions about your environments, releases, packages, and beyond.

Today marks an exciting milestone not just for Cortex, but for every organization looking to foster a culture of engineering excellence. Knowing who owns what is one of the hardest and most important challenges for engineering teams. Without clear ownership, incidents take longer to resolve, migrations stall, and enforcing standards becomes nearly impossible.

With over 50 built-in integrations, Cortex customers have an always-up-to-date, single interface for their engineering priorities, tools, and tasks. But large organizations have a lot of tools. And if you're running internally hosted tools, or for policy or security reasons would prefer to keep your access tokens private, that used to limit what was possible in your internal developer. Not anymore.

Gartner Market Guide for Internal Developer Portals offers “Platform engineering teams are tasked with improving developer experience, ensuring consistent governance, and enabling discovery and access to software development and delivery capabilities. Platform engineering leaders can use internal developer portals to address these challenges.” Organizations with a current Gartner license can check out the report here.

Change is constant in engineering organizations. Whether you’re growing quickly and onboarding dozens of engineers—or navigating the difficult process of layoffs—your systems, services, and institutional knowledge don’t pause. That’s where an Internal Developer Portal (IDP) becomes indispensable.

Every engineering leader knows the stress of an upcoming seasonal spike. Whether it’s tax season, open enrollment, or Black Friday, there’s always that moment where someone says, “Are we actually ready?” It’s usually followed by a scramble: auditing services, chasing down owners, updating spreadsheets, running perf tests, checking alerting thresholds, verifying infra configs—much of it manual, fragmented, and slightly different every time. It’s exhausting.

Being in the cloud is table stakes in 2025, and simply lifting and shifting workloads to the cloud barely scratches the surface of what's possible. Yet many engineering teams find themselves managing glorified data centers in the cloud—missing out on key capabilities like auto-scaling, serverless computing, and cloud-native security features. Cloud modernization is the true game-changer for turning legacy systems into agile, scalable architectures.

Not too long ago, engineering organizations were in a headlong rush to “innovate or die” by hiring more developers and shipping more code at breakneck speed. This expansion brought short-term velocity gains—but also created a tangle of orphaned services, inconsistent processes, and developers spending more time firefighting than innovating. Today, the reality is that you can’t just keep throwing headcount at complexity.

Cloud infrastructure powers everything from streaming services to enterprise databases, yet many organizations still run critical workloads on legacy systems. With the cloud migration market projected to reach $806.41 billion by 2029, growing at a CAGR of 28.24%, organizations of all sizes are racing to modernize their infrastructure and applications. This shift means companies need to stay competitive in a landscape where agility and scalability are non-negotiable.