Operations | Monitoring | ITSM | DevOps | Cloud

To really make an impact, platform engineering teams need to start thinking like product managers. That means deeply understanding their users, measuring outcomes instead of outputs, and tying everything they do to real business value. Organizations who care about total cost of ownership and fast time to value are adopting this mindset.

Last week, hundreds of engineering leaders, SREs, platform teams, and developers joined us for Summer Scoop 2025, our biggest launch event yet. The way that we think about our product development at Cortex revolves around all the different types of users who are in our product every day.

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!

Whether it's ensuring a new service is fully equipped with security scanning, logging, and monitoring from the start, enforcing production readiness checks during deployment, or providing temporary credentials for a production database, Workflows directly support Engineering Excellence Initiatives around modernization and standardization.

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.