Blog
Product
Qovery
3
minutes

Announcing Qovery V3: What's new?

Qovery V3, which is the most significant product evolution of the last twelve months, was launched in Alpha testing about two weeks ago now. We started gathering some feedback and also added some new functionality since then so let’s take a look on how’s going.
Albane Tonnellier
Product Marketing Manager
Summary
Twitter icon
linkedin icon

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:

Infrastructure logs

Soon to be accessible from the cluster page on the V3, it is now accessible from the organization panel on the V2:

Access to infrastructure logs

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:

Environment Variables tab

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:

Deployment rules tab

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:

Alpha tester feedback
PM answer

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. 💜

Share on :
Twitter icon
linkedin icon
Ready to rethink the way you do DevOps?
Qovery is a DevOps automation platform that enables organizations to deliver faster and focus on creating great products.
Book a demo

Suggested articles

AI
Infrastructure Management
Product
5
 minutes
GPU workloads on EKS just got way simpler with Qovery

Running GPU workloads on EKS has never been easy, until now. With Qovery’s latest update, you can enable GPU nodes, configure GPU access, and optimize costs automatically, all without writing a single line of YAML or touching Helm charts. Qovery now handles everything behind the scenes so you can focus entirely on your applications.

Alessandro Carrano
Lead Product Manager
Kubernetes
 minutes
Kubernetes Deployment Strategies: Pros, Cons & Use Cases

Master Kubernetes deployment strategies: Rolling Update, Recreate, Blue/Green, and Canary. Learn the pros, cons, and use cases to choose the right strategy based on your uptime, risk tolerance, and resources. Simplify complex rollouts with automation.

Mélanie Dallé
Senior Marketing Manager
DevOps
Developer Experience
 minutes
AWS ECS vs. EKS vs. Elastic Beanstalk: A Comprehensive Guide

Confused about which AWS container service to use? This comprehensive guide compares the trade-offs between simplicity, control, and complexity for ECS, EKS, and Elastic Beanstalk to help you choose the right platform for your application.

Mélanie Dallé
Senior Marketing Manager
DevOps
AWS
7
 minutes
Migrating from ECS to EKS: A Complete Guide

Planning your ECS to EKS migration? Learn the strategic business case (portability, ecosystem access), navigate the step-by-step roadmap, and avoid common pitfalls (networking, resource allocation). Discover how Qovery automates EKS complexity for a seamless transition.

Morgan Perry
Co-founder
DevOps
 minutes
Fargate Simplicity vs. Kubernetes Power: Where Does Your Scaling Company Land?

Is Fargate too simple or Kubernetes too complex for your scale-up? Compare AWS Fargate vs. EKS on cost, control, and complexity. Then, see how Qovery automates Kubernetes, giving you its power without the operational headache or steep learning curve.

Mélanie Dallé
Senior Marketing Manager
DevOps
Cloud Migration
 minutes
FluxCD vs. ArgoCD: Why Qovery is the Better Way to Do GitOps

Dive into the ultimate FluxCD vs. ArgoCD debate! Learn the differences between these top GitOps tools (CLI vs. UI, toolkit vs. platform) and discover a third path: Qovery, the DevOps automation platform that abstracts away Kubernetes complexity, handles infrastructure, and lets you ship code faster.

Mélanie Dallé
Senior Marketing Manager
Qovery
 minutes
Our rebrand: setting a new standard for DevOps automation

Qovery unveils its new brand identity, reinforcing its mission to make DevOps simple, intuitive, and powerful. Discover how our DevOps automation platform simplifies infrastructure, scaling, security, and innovation across the full DevOps lifecycle.

Romaric Philogène
CEO & Co-founder
Qovery
3
 minutes
We've raised $13M Series A to make DevOps so simple, it feels unfair

I'm excited to announce our $13M Series A, led by IRIS and Crane Venture Partners with support from Datadog founders and Speedinvest. This investment will fuel our mission to make DevOps simple and scalable, expand in the US and Europe, and accelerate product innovation.

Romaric Philogène
CEO & Co-founder

It’s time to rethink
the way you do DevOps

Say goodbye to DevOps overhead. Qovery makes infrastructure effortless, giving you full control without the trouble.