Announcing Qovery V3: What's new?
New functionalities
Following our goal of releasing an official Beta with all the features already available in the V2 by September, our team is working hard on all those core features and even more; let me walk you through the details.
Infrastructure logs
Those logs will facilitate the debugging and optimize the visibility and transparency of your infrastructure.
Now, the fun doesn’t stop there because if you have an error, an error tab will automatically display the information of the last issue in the logs.
Can’t wait to see what it looks like, well head to the console and find out for yourself, but if you really can’t wait, here is a snapshot of it:
Soon to be accessible from the cluster page on the V3, it is now accessible from the organization panel on the V2:
NB: We are still working on improving the error messages, so don’t hesitate to give a feedback if something is confusing 🙏🏻
Environment variables
Already available in the V2, the environment variable page is also here in the V3.
For the V3, the concept is a bit different as environment variables and secrets are merged; you can directly see the linked service, and soon you will even be able to create/edit your environment variable and deploy the application in one click.
Where can I find it in the V3?
On the console V3, head to the application page where you will see a “variable tab”, which should look like that:
Now you might already be aware of the power that this feature hold but if you don’t, here is a demo of Environment Variables management on the V3:
Deployment rules
Here we will talk about “Deployments Rules at project level” (applied by default on any new environment).
It is already available in the V2 and ready for you to use in the V3.
Didn’t make the most of it in the V2? Well, a Deployment Rule lets you configure the lifecycle of your Environments.
Why use the Deployment Rule?
- Cloud cost optimization Using the Deployment Rules is a good practice to reduce your cost drastically. Indeed, Qovery knows how to optimize your Cloud resources when your applications are not running. Then you can expect to reduce your Cloud cost by up to 60% using the Deployment Rules.
- Time optimization Configuring your environments, managing, starting, and shutting down all take valuable time from your developers. Deployment Rules allow you to declaratively set up how your resources should be used, let Qovery do the dirty job, allowing your employees to focus on important things.
If you want to know everything about the deployment rules, check out our documentation.
Where can I find the deployment rules on the V3?
Just head to the environment panel where you can find the “Deployment Rules” tab like, shown right below:
Feedback
It’s hard to get everything right from the start, and we are fortunate to have Alpha testers looking out for bugs or confusing flow in the V3, from design to reviewing the logs, our testers are an excellent help for the whole team, here is a small example:
Wrapping up
If you are an Alpha tester, thank you for making the V3 better with all your feedback, and if you’re not part of it, we hope you are as excited as us to try the Beta version that will be available to use in September. 💜
.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)