Discover 7 New Major Features on Qovery
The 7 New Major Features
1. GCP GKE Integration
Our journey into the cloud has taken a significant leap with the integration of Google Cloud Platform's Google Kubernetes Engine (GKE). This feature allows you to seamlessly deploy and manage your applications on GKE, embracing the power and flexibility of Google Cloud.
Qovery now supports AWS, Scaleway, and Google Cloud Platform (GCP).
2. Bring Your Own Kubernetes (BYOK)
With BYOK, we're tearing down the walls of limitation. You can now bring any Kubernetes cluster to Qovery, whether it's on-premise, in the cloud, or even on your local machine.
This flexibility ensures that you can enjoy the Qovery experience on your terms.
3. Helm Deployment Support
The complexity of deploying Helm charts is now a thing of the past.
Our native support for Helm deployments means you can easily deploy and manage your Helm charts directly through Qovery, streamlining your deployment processes.
4. Port Forwarding
Security is paramount, and with our new Port Forwarding feature, you can securely connect to any service within your Qovery environment without exposing it to the public internet.
This feature ensures your internal services remain secure while accessible.
5. Use Existing VPC
For those who require granular control over their network configurations, you can now deploy Qovery within your existing VPC.
This capability ensures that you can adhere to your organization's networking policies while leveraging Qovery's powerful platform.
6. Bulk Actions
With Bulk Actions, you can perform actions on multiple services simultaneously, reducing the time and effort required to manage your applications.
7. Google and Microsoft Authentication
In our quest to simplify access to Qovery, we've introduced authentication options for both Google and Microsoft accounts.
This update means faster, more secure access to Qovery using the credentials you already trust.
What's Next?
Check out our public roadmap 😎
Conclusion
These features represent our ongoing commitment to providing you with an unmatched developer experience. They're designed to make your life easier, allowing you to focus on what you do best: building amazing applications.
We're eager to hear your thoughts on these new features. Your feedback is invaluable as it helps us tailor Qovery to better meet your needs. Try them out, push their limits, and let us know your experiences.
To explore these features, sign up or log in to your Qovery account today.
Happy coding!
.svg)
.svg)
.svg)
Suggested articles
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.
Kubernetes multi-cluster management is the Day-2 operational practice of orchestrating applications, security, and configurations across geographically distributed clusters. Because native Kubernetes was designed for single-cluster orchestration, enterprise platform teams must implement a centralized control plane to prevent configuration drift and manage a global fleet without scaling manual toil.
Achieving zero-downtime deployments on Kubernetes requires more than running multiple pods. It demands a standardized architecture utilizing Pod Disruption Budgets (PDBs), precise liveness and readiness probes, pod anti-affinity, and graceful termination handling. At an enterprise scale, these configurations must be enforced via a centralized control plane to prevent catastrophic configuration drift.
.webp)