Operations | Monitoring | ITSM | DevOps | Cloud

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.

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.

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.

StatusGator supports custom email branding on our Enterprise plan and as an add-on to other plans, allowing your customers or end-users to get an email that has your organization logo and sends from your organization’s email address. Previously, this email logo used the same image as your status page. Now, you can upload a custom logo to be used just for your emails. Enjoy improved branding by uploading a logo that fits the email perfectly.

HIPAA and GDPR compliance laws are both essential laws from Europe and America to protect user data. While HIPAA focuses on protecting medical and patient information to prevent the rise in healthcare data breaches, GDPR is broader, focusing on regulations that handle personally identifiable information (PII) of EU and UK citizens.

Understand what APRA CPS 230 means for your organization, and how to get compliance-ready by the July 2025 deadline. If you work for an Australian business in the financial services industry, you’ve likely already heard of the Australian Prudential Regulation Authority (APRA). You may also have heard that a new set of APRA regulations, CPS 230, will become mandatory for all APRA-regulated companies to comply with as of 1 July 2025.

Modern applications generate a deluge of telemetry data—logs, metrics, and traces—that hold the key to understanding system performance and reliability. However, managing this data effectively is a growing challenge for DevOps teams. Raw telemetry can overwhelm teams with complexity and noise even when collected via robust standards like OpenTelemetry.

For years, IT teams have lived and died by the ticket. Every incident, every request, every change: logged, routed, triaged, assigned. We built entire platforms, teams, and workflows around this idea. But the IT environment has changed. Complexity is exploding. Expectations are rising. And the ticket? It’s become a bottleneck. If you’re in IT operations, you already feel this. The relentless volume. The alert fatigue. The rising MTTRs and missed SLAs. The pressure to do more with less.

Over the last few years, more organizations have switched from relying solely on one cloud service provider (CSP) to several. The primary reasons for the change are minimizing dependence on a single CSP, preventing vendor lock-in, and providing greater flexibility. Recent trends include using a mix of cloud providers to take advantage of the cost savings several CSPs offer and using best-of-breed services for different applications, teams, or departments.