Operations | Monitoring | ITSM | DevOps | Cloud

Over the past 11 years, we have focused on one problem: ensuring complex conversion journeys work reliably in the real world. Across ecommerce platforms, travel services and large consumer websites, these journeys are where revenue is generated and where reliability matters most. In 2026, our focus sharpens further. The theme for the year is simple: Higher signal trust. Deeper intelligence. Stronger operational resilience.

CertKit is officially out of beta. We started building CertKit a year ago, and since then over 600 people signed up, issued certificates, and deployed to their infrastructure. Several are running it as their production certificate management platform right now. We built a lot during the beta. Some of it we planned: SSO, team management, alerting. Other things, users had to beat into us. The Keystore came from enterprise security requirements to keep private keys in house.

We are excited to announce the latest release of SecureBridge, EntityDAC, and the full family of dbExpress drivers. This update delivers expanded IDE compatibility, support for the latest database versions, new security components, and platform improvements that benefit developers across the Delphi and Lazarus ecosystem.

We’ve spent the last few months listening to how teams are running InfluxDB 3 in the wild. The feedback was clear: as you scale, you need less “guesswork” and more control. Today’s release of InfluxDB 3.9 is our answer to that. As more teams move InfluxDB 3 into production, our focus has shifted toward the operational experience: how you manage the database at scale, how you ensure it remains secure, and how you provide a seamless experience for users.

We release some good stuff this week with the CertKit agent version 1.8 from our roadmap, along with some small usability fixes in the CertKit web application.

This is not just a version bump. Raising the PHP floor allowed us to modernize the IPL codebase in ways that were not possible before: strict type declarations throughout, and a cleaner, more predictable API surface.

In a high-pressure incident, speed is everything. During incidents, engineers often jump between tools like traces, logs, and metrics, losing context at every step. This ruins the investigation state, slows down the process, and increases MTTR.