The Future of Qovery - Week #2
This series will reveal all the changes and features you will get in the next major release of Qovery. Let's go!
Read the previous article: The Future of Qovery - Week #1.
Qovery Environment
Qovery has been built to manage complex Production, Staging, and Dev environments seamlessly. Complex means that your production environment has probably up to hundreds of applications, and you may want to keep synchronized your staging and dev environments from your production environment. Qovery promises to keep you safe from any bug while promoting your changes in production.
Each Git branch that the developer creates is an Environment. It is very convenient to validate your pull requests/bug fixes/improvements with the same configuration as in production.
Revamped Environment
Thanks to our community for their hundreds of feedback using Qovery's DevOps automation tool. We decided to enhance the Environment interface by giving you more granular control over your applications, databases, and other resources.
For instance, with the new Environment interface, you'll be able to:
Restart, pause, stop a single application or database
Rollback a single application
Know precisely who made an action
See the entire deployment history.
Get alerted if something goes wrong.
And this is only the beginning. Besides simplifying application deployment in the Cloud, Qovery's goal is to make you and your team focus on what you do best — developing great products.
See you next week — same hour, same place. 👋
Read the following article: The Future of Qovery -- Week #3
Romaric from Qovery -- We are hiring
.svg)
.svg)
.svg)
Suggested articles
Is Kubernetes complexity killing your team’s velocity? Compare Docker vs. Kubernetes in 2026 and discover how to get production-grade orchestration with the "Git Push" simplicity of Docker.
Comparing VMware Tanzu vs. Red Hat OpenShift for enterprise Kubernetes? Explore their features, pros, cons, and discover why Qovery is the smarter alternative for rapid application delivery.
Struggling with Kubernetes configuration sprawl and long deployment queues? Discover how to identify technical vs. workflow bottlenecks and why shifting to a self-service Kubernetes management platform like Qovery is the key to scaling your engineering velocity.
Following the end of maintenance of the Ingress NGINX project, we have been working behind the scenes to migrate our customers’ clusters from Kubernetes Ingress + NGINX Ingress Controller to Gateway API + Envoy Gateway.
.webp)