Operations | Monitoring | ITSM | DevOps | Cloud

DevOps Team Extension: Qovery engineers watching your infrastructure every month

DevOps Team Extension gives growing engineering teams a named Qovery engineer, a continuous infrastructure scan, and a monthly remediation plan, so they can scale reliability, security and compliance without hiring a DevOps team first. Romaric founded Qovery to make Kubernetes accessible to every engineering team. He writes about platform strategy, developer experience, and the future of cloud infrastructure.

Replacing NGINX with Envoy Gateway on Hundreds of Clusters: What the Plan Missed

In February we planned to move every Qovery-managed cluster from ingress-nginx to Envoy Gateway by the end of March. It took until October. Here is the rollout model, every class of problem we hit, and what I would do differently. Benjamin is a staff engineer at Qovery focused on infrastructure automation, Kubernetes internals, and building the deployment engine that powers thousands of clusters.

Inside a DevOps Team Extension engagement: an infrastructure review and a Typesense architecture session

How Qovery assessed a growing B2B SaaS company's infrastructure across about 150 controls, what the review with their team changed, and why a Typesense high-availability project turned into a sharding plan. Romaric founded Qovery to make Kubernetes accessible to every engineering team. He writes about platform strategy, developer experience, and the future of cloud infrastructure.

How we investigate Sentry errors with an AI agent

We built an AI agent on Qovery to investigate Sentry alerts before our team picks them up. Here’s how the workflow runs, what it delivers, and where engineers still need to step in. Rémi is a staff frontend engineer at Qovery. He writes about frontend architecture, developer experience, and building scalable UI systems for platform engineering tools.