What’s New in Qovery Q1 2025: Faster Deployments, Smarter Scaling, and More Control
Let’s dive into what’s new and what’s next for Qovery.
What's New ⚡
Karpenter for Production
Karpenter is now fully integrated and production-ready in Qovery. You can automatically scale your workloads based on real-time demand while drastically reducing compute waste 🔥.
Why it matters:
- Up to 60% infrastructure cost savings.
- Faster pod scheduling and optimized node utilization.
- Zero manual tweaking - it just works.
It is ideal for teams with fluctuating workloads who want to align Kubernetes computing with real usage and avoid wasting money.
Simplicity does not mean limited. So, you can also possibly configure additional Karpenter settings, such as the type of nodes, spot instances, consolidation, limits, and, soon, even custom node pools.
Deployment Pipeline v5
We’ve re-engineered our Deployment Pipeline from the ground up. Version 5 brings better visibility into each deployment stage.
Your developers focus on delivering features instead of wasting time debugging deployments.
Deployment History View
Quickly inspect what was deployed, when, by whom - and with which commit an image tag. The new Deployment History View makes this fully traceable.
Deployment Queuing
It’s finally here… you can now queue deployment requests within the same environment! 🎉
Remember the toaster message saying an action couldn’t be performed because a deployment was ongoing? That’s a thing of the past!
You can trigger a new deployment within the same environment, even if another one is in progress. Every new request will be added to a queue and processed as soon as the ongoing deployment is completed.
Bonus: To speed up overall deployment time, queued requests are automatically merged into a single deployment whenever possible (if triggered by the same user and with the same action).
See the documentation of this feature.
Kubernetes Ephemeral Debug Pod
We’ve introduced a new CLI command that simplifies connecting to your Kubernetes cluster without requiring credentials. This feature is restricted to admins; all connections are logged in the audit logs for security and transparency.
Technically, this feature deploys a dedicated debug pod on your cluster, preloaded with valuable tools like kubectl and k9s. It’s an invaluable resource for debugging or investigating issues directly from your local machine.
What’s Coming Next 🔮
Here’s what you can expect in Q2 2025:
- Built-in Observability and Monitoring: Track CPU, memory, network, and app logs directly inside Qovery.
- DevOps AI Agent: Automatically analyze misconfigurations, suggest infra optimizations, and even detect cost anomalies.
- Qovery on VMware (EKS Anywhere): For companies running on-premise or hybrid, we’re bringing Qovery to VMware with EKS-A support.
- AKS (Azure Kubernetes Service) Support: With Karpenter, for those running in Microsoft Azure.
- AWS STS (Service Token Service): Enabling fine-grained access management and secure cross-account workflows.
The Future of Qovery 🎉
Qovery is evolving into the complete Kubernetes management platform that combines:
- Infrastructure Management
- CI/CD
- Observability
- FinOps
- SecOps
By Q3/Q4 2025, our mission is to deliver a self-service platform that gives dev teams the speed of Heroku, the power of Kubernetes, and the financial transparency of a FinOps-native platform - all in one.
It's a Wrap
Whether you’re scaling your platform, controlling cloud costs, or accelerating releases, our latest features are designed to give you the leverage you need. As always, you can follow our full changelog at qovery.com/changelog, and if you want a live demo or to explore any of these features, just reach out.
Stay tuned for the next wave of releases - and thank you for building with Qovery.
--
Feel free to watch the full demo day 👇🏼
.svg)
.svg)
.svg)
Suggested articles
In the 2026 regulatory landscape, manual audits are a liability. This guide explores using GitOps to generate DORA-compliant audit trails through IaC, drift detection, and automated segregation of duties. Discover how the Qovery management layer turns compliance into an architectural output, reducing manual overhead for CTOs and Senior Engineers.
Kubernetes success is determined by Day 2 execution, not Day 1 deployment. While migration is a bounded project, maintenance is an infinite loop that often consumes 40% of senior engineering capacity. To protect margins and velocity, enterprises must transition from manual toil to agentic automation that handles scaling, security, and cost.
Day-0 is planning, Day-1 is deployment, and Day-2 is the infinite lifecycle of maintenance. While Day-0/1 are foundational, Day-2 is where enterprise operational debt accumulates. At fleet scale (1,000+ clusters), managing these differences manually is impossible, requiring agentic automation to maintain stability and eliminate toil.
A multi-cluster Kubernetes architecture distributes application workloads across geographically separated clusters rather than a single environment. This strategy strictly isolates failure domains, ensures regional data compliance, and guarantees global high availability, but demands centralized Day-2 control to prevent exponential cloud costs and operational sprawl.
Stop overpaying for Kubernetes observability. Learn how in-cluster monitoring and AI-driven troubleshooting with Qovery Observe can eliminate APM ingestion fees, reduce SRE bottlenecks, and make your cloud costs predictable.
.webp)