Qovery v2 beta is out
At Qovery, we strive to build the future of the Cloud.
What's new?
New web interface
Thanks to our product team - we redesigned the web interface from scratch. Here is a brand new web interface for an outstanding user experience. Take a look at how easy it is to deploy your first app - from zero to hero with Qovery v2.
Mono repository support
You were more and more requesting the support of the mono repository. Qovery v2 supports it. Read more.
Juicy and efficient logs interface
A short video is better than thousands of words, right?
Fast performance
Give it a try - our web interface is just blazingly fast!
Open API
Our API is documented for you and us! The sky is the limit - you can integrate Qovery with all your tools.
What's coming next?
In the coming days, we will release the most important features like the support of Environment Variables and Secrets. Then this summer, we will launch the remaining features (historical metrics, deployment on your cloud account) to release the Qovery v2 final for late September.
- Environment variables - available next week.
- Secrets management - available in July.
- Historical metrics - available this summer.
- Deployment on your Cloud account - available this summer.
Check out our product roadmap.
Useful resources
- Check out https://discuss.qovery.com/t/read-me-first-getting-started-with-the-beta to better use the Qovery v2 beta.
- Qovery v2 beta is available: https://console.qovery.com/
- Qovery v1 is available: https://console-v1.qovery.com/
- Q&A or bug report: https://discuss.qovery.com/c/beta-v2/29
Warm thank you
I would like to warmly thank you, our community involved in the success of this new release. Thank you, Stun3R, Kartik, and Aggis, for your devotion and help to the community. You make the success of Qovery's DevOps automation tool.
.svg)
.svg)
.svg)
Suggested articles
The shift from AI copilots to autonomous agents is redefining infrastructure requirements. Discover how to build secure, stateful, and compliant Agentic AI systems using Kubernetes, sandboxing, and observability while meeting EU AI Act standards
Effective Kubernetes management in 2026 demands a shift from manual cluster building to intent-based fleet orchestration. By implementing agentic automation on standard EKS, GKE, or AKS clusters, enterprises eliminate operational weight, prevent configuration drift, and proactively control cloud spend without vendor lock-in, enabling effective scaling across massive fleets.
A Kubernetes single pane of glass is a centralized management layer that unifies visibility, access control, cost allocation, and policy enforcement across § cluster in an enterprise fleet for all cloud providers. It replaces the fragmented practice of switching between AWS, GCP, and Azure consoles to govern infrastructure, giving platform teams a single source of truth for multi-cloud Kubernetes operations.
Deploying a Docker container on Kubernetes requires building an image, authenticating with a registry, writing YAML deployment manifests, configuring services, and executing kubectl commands. While necessary to understand, executing this manual workflow across thousands of clusters causes severe configuration drift. Enterprise platform teams use agentic platforms to automate the entire deployment lifecycle.
At enterprise scale, managing provider-specific Kubernetes YAML across multiple clouds creates crippling configuration drift and operational toil. By adopting an agentic Kubernetes management platform, infrastructure teams abstract cloud-specific configurations (like ingress controllers and storage classes) into a single, declarative intent that automatically reconciles across 1,000+ clusters.
To stop GPU costs from destroying SaaS margins, teams must transition from static to consumption-based infrastructure by utilizing Karpenter for dynamic provisioning, maximizing hardware density with NVIDIA MIG, and leveraging Qovery to tie scaling directly to business metrics.
AI is helping developers write more code, faster than ever. But writing code is only half the story. What happens after? Building, deploying, debugging, scaling. That's where teams still lose hours.We're building Qovery for this era. Not just to deploy your code, but to make everything that comes after writing it just as fast.
.webp)