Operations | Monitoring | ITSM | DevOps | Cloud

In my recent posts, I looked back at the major features we shipped in 2025, highlighted all the exciting things going on in Flyway for Oracle databases, and shared the recent improvements to tracking dependencies for both SQL Server and Oracle databases. But that’s only part of the story. With four development teams working on Flyway, there’s a lot happening. Here’s a look at what’s recently been released, what’s in public preview, and what’s coming next.

This is a guest post from Maxime Drobot. This month we’re bringing you official GitHub Actions for Redgate Flyway, usability improvements in Flyway Desktop, and a look at what’s new, what’s in preview. Plus: earlier visibility of code‑review results, helping teams keep quality high and reviews flowing smoothly as AI increases the volume of changes.

--- Key Takeaway: Harness AI helped deflect 95% of the platform support tickets for a major financial institution --- These days, success is often measured by what doesn’t happen: When things go right, the software delivery platform is invisible. But what happens when an organization’s delivery velocity increases multifold? Can the platform still stay out of the way?

Modern engineering teams run on CI/CD. It’s where pull requests get validated, artifacts get produced, and releases get promoted to production. That also makes CI/CD migration very risky because you're not just moving a "tool"; you're moving the workflow that developers use dozens or hundreds of times a day. The good news: disruption is optional.

A host map is a visual representation of your infrastructure that displays hosts and related resources such as clusters, pods, and containers in a single, interactive view. We introduced the Datadog Host Map more than a decade ago to help you “know thy infrastructure” and answer critical questions: Does everything look healthy? Has anything changed? Does the shape of my environment match what I expect?

When you use CertKit, your private keys live in CertKit’s database, encrypted at rest. We’ve written about why the actual risk is smaller than it sounds. But some organizations have policies that prohibit storing private keys with any third party, regardless of how they’re protected. That policy isn’t going away. The Local Keystore enables those organizations to use CertKit and still keep their keys local.

If you run a software engineering tools team, you have almost certainly had this conversation: a developer asks for production data access to debug a real incident, and someone in the room says no. Not because the request is unreasonable (it isn’t), but because nobody wants to be the person who said yes when something goes wrong. That instinct is understandable. Production environments carry real risk. But the reflex to lock everything down has a cost that rarely gets accounted for.

Once upon a time, a monolith running on a handful of servers meant that incident management, even at 2:17 AM, was something a single generalist could handle. One person with enough context across the stack could reasonably diagnose whether the database was choking, a config had changed, or a server was running hot. They’d fix it and go back to sleep.