2024 - What a Year - Welcome 2025
2024 in Review
2024 was an incredible year for Qovery! We joined the AWS ISV Accelerate program and help over 100 amazing companies — like Alan, Talkspace, and GetSafe — rely on us daily to ship faster and streamline their cloud infrastructure. We’re proud to help so many teams focus on building great products instead of battling DevOps complexity.
We Shipped Hard 💪🏼
- UX: New Logs (v5)
- Core: AWS EKS Karpenter instance Filtering
- AI: Migration AI DevOps Agent
- UX: Managed Kubernetes Cluster Diff
- Core: Qovery on your Local Machine
- Network: Use Existing VPC
- Network: AWS ALB
- Core: Kubernetes Annotations Group
- Core: Kubernetes Labels Group
- Core: Helm Deployment
- UX: Web Cloud Shell
- Security: Port Forwarding
- UX: New Helper
- Core: GPU Support with Karpenter
- UX: Helm Admission Controller
- Security: Microsoft, Bitbucket, and Google Authentication
- Core: AWS EKS Karpenter
- UX: Auto-completion for Environment Variables
- Core: Improve container registry cache usage
- UX: Customizable Icons for Services
- Core: Env Var Interpolation for Env as a File
- Core: Billing Usage Dashboard
- Partnership: AWS Marketplace
- Core: GCP GKE Autopilot
- Core: Bring Your Own Kubernetes (BYOK)
And, of course, we kept improving our interfaces daily:
- Web Console (GitHub)
- Terraform Provider (GitHub)
- CLI (GitHub)
- API (OpenAPI)
Happy New Year 2025
From our team to yours, we wish you a fantastic end of 2024 and the beginning of 2025.
As always, we’re grateful for your support.
Thanks for being part of our journey.
Pssst, we actively hire in New York 🇺🇸 and Paris 🇫🇷 :)
.svg)
.svg)
.svg)
Suggested articles
The cluster coming up is the easy part. What catches teams off guard is what happens six months later: certificates expire without a single alert, node pools run at 40% over-provisioned because nobody revisited the initial resource requests, and a manual kubectl patch applied during a 2am incident is now permanent state. Agentic control planes enforce declared state continuously. Monitoring tools just report the problem.
The instinct when setting up Kubernetes observability is to instrument everything and send it all to your APM vendor. That works fine at ten nodes. At a hundred, the bill becomes a board-level conversation. The less obvious problem is the fix most teams reach for: aggressive sampling. That is how intermittent failures affecting 1% of requests disappear from your monitoring entirely.
Scaling your deployments to zero is only half the battle. If your cluster autoscaler does not aggressively bin-pack and terminate the underlying worker nodes, you are still paying for idle metal. True environment sleeping requires tight integration between your ingress layer and your node provisioner to actually realize FinOps savings.
The structure, table, tool list, and code blocks are all worth keeping. The main work is fixing AI-isms in the prose, updating the case study to real metrics, correcting the FAQ format, and replacing the CTAs with the proper HTML blocks. The tool descriptions need the "Core strengths / Potential weaknesses" headers made less template-y, and the intro needs a sharper human voice.
For years, Red Hat OpenShift has been the safe choice for heavily regulated, on-premise environments. It operates as a secure fortress. But in the public cloud, that fortress acts as an expensive prison. Paying proprietary per-core licensing fees on top of your standard AWS or GCP compute bill is a redundant "middleware tax." Escaping OpenShift requires decoupling your infrastructure from your developer experience by running standard, vanilla Kubernetes paired with an agentic control plane.
Agentic Kubernetes resource reclamation is the practice of using an autonomous control plane to continuously identify, suspend, and delete idle infrastructure across a multi-cloud Kubernetes fleet. It replaces manual cleanup and reactive autoscaling with intent-based policies that act on business state, eliminating the configuration drift and cloud waste typical of unmanaged fleets.
Kubernetes focuses on container orchestration, but the reality on the ground is far less forgiving. Provisioning a single cluster is a trivial Day-1 exercise. The true operational nightmare begins on Day 2. Teams that treat multi-cloud fleets like isolated pets inevitably face crushing YAML configuration drift, runaway AWS bills, and severe scaling bottlenecks.
.webp)