Operations | Monitoring | ITSM | DevOps | Cloud

Three days, 20 talks at Devoxx France 2026. The through-line wasn't AI hype - it was discipline. Context engineering, code review under AI volume, and the local-vs-remote question now shaping security, cost, and sovereignty. Fabien is a senior software engineer at Qovery. He writes about platform engineering, AI tooling, context engineering, and the practical realities of running modern developer infrastructure.

Every enterprise contract I’ve signed in the last two years has the same clause. “Vendor will not use Customer Data to train machine learning models.” Sometimes it’s a paragraph. Sometimes it’s a whole section. The language varies but the intent is identical: don’t feed our production data into your AI. I get it. I sign the same clause as a vendor. But here’s what’s been bothering me: that clause is a promise, not an architecture.

Production secrets should live in one place and stay there, whether your next deployment is triggered by a developer or an AI agent. The Secret Manager integration connects AWS Secrets Manager, AWS SSM, or GCP Secret Manager to Qovery so secrets are referenced, never copied, and enterprise governance holds regardless of who deploys. Alessandro leads product at Qovery. He drives the changelog, roadmap, and product strategy - turning customer feedback into platform capabilities.

Let’s face it, refreshing devices used to be a guessing game. IT teams would swap out laptops and desktops on a fixed schedule, hoping to keep everyone happy and productive. But in today’s hybrid, cloud-first world, that old approach just doesn’t work. Employees expect seamless experience, and businesses can’t afford to waste money on unnecessary upgrades or risk productivity dips from outdated tech. That’s where Digital Employee Experience (DEX) comes in.