New Feature: Deployment Pipeline
What is Qovery's Deployment Pipeline Feature?
A Deployment Pipeline consists of multiple stages, each with an assigned execution order within the pipeline. When you trigger the deployment of an environment, Qovery executes this pipeline to deploy every service defined within your environment. Each service belongs to one (and only one) Deployment Stage, allowing you to define at which moment of the deployment pipeline a service should be deployed and thus respect any service inter-dependency.
Why does it matter?
The Deployment Pipeline feature enables you to configure each stage and its order of execution, allowing for greater control over your deployment process. With this feature, you can ensure that services are deployed in the correct order to meet any dependencies between them. This is especially important when dealing with complex applications that have multiple services with varying dependencies.
For instance, you might need to guarantee that your Databases start before your Backend, your API Gateway starts after your Backend and your Frontends after your API Gateway.
Qovery's Deployment Pipeline feature allows for parallel deployment, which can significantly reduce the time it takes to deploy your services. By executing multiple steps in parallel, you can speed up the deployment process and reduce the risk of downtime during deployment.
How does it work?
Each stage in the deployment pipeline consists of multiple steps that can be executed in parallel. The steps can include building and deploying your services. Qovery's Deployment Pipeline feature allows you to configure each step and its order of execution within a stage, ensuring that everything runs smoothly during deployment.
Additionally, Qovery's Deployment Pipeline feature offers the flexibility to configure certain actions to be performed at specific stages of the pipeline. For example, you can seed your database after it has started but before the application starts, or perform a database backup when the environment is deleted. It's up to you to do whatever you need within your deployment pipeline.
What's next?
Qovery's Deployment Pipeline feature is just the beginning. We have a few enhancements planned that we're excited to share with you:
- A dedicated view to see the deployment pipeline and where it has failed, along with an enhanced view of the deployment logs to better see where the deployment process has failed.
- Retrigger a complete stage instead of the complete pipeline or a step.
- Decouple Build and Deployment phase: Decoupling the Build and Deployment phase will be possible to speed up the deployment process depending on the user use case. For instance, sometimes, the build can be done ahead of all deployments, but the deployment only must be ordered.
We're always open to feedback and suggestions, and we invite you to share your thoughts on our public roadmap.
Conclusion
Qovery's Deployment Pipeline feature is a big milestone for us, and we're excited to share it with our users. By enabling greater control over service deployment order and offering the flexibility to configure certain actions at specific stages of the pipeline, we're confident that this feature will make the deployment process even faster and smoother. We can't wait to see what you'll build with it!
Resources
.svg)
.svg)
.svg)
Suggested articles
Scaling your deployments to zero is only half the battle. If your cluster autoscaler does not aggressively bin-pack and terminate the underlying worker nodes, you are still paying for idle metal. True environment sleeping requires tight integration between your ingress layer and your node provisioner to actually realize FinOps savings.
The biggest mistake enterprises make when evaluating Kubernetes management platforms is confusing infrastructure provisioning with Day-2 operations. Tools like Terraform or kOps are excellent for spinning up the underlying EC2 instances and networking, but they do absolutely nothing to prevent configuration drift, automate certificate rotation, or right-size your idle workloads once the cluster is actually running.
For years, Red Hat OpenShift has been the safe choice for heavily regulated, on-premise environments. It operates as a secure fortress. But in the public cloud, that fortress acts as an expensive prison. Paying proprietary per-core licensing fees on top of your standard AWS or GCP compute bill is a redundant "middleware tax." Escaping OpenShift requires decoupling your infrastructure from your developer experience by running standard, vanilla Kubernetes paired with an agentic control plane.
Agentic Kubernetes resource reclamation is the practice of using an autonomous control plane to continuously identify, suspend, and delete idle infrastructure across a multi-cloud Kubernetes fleet. It replaces manual cleanup and reactive autoscaling with intent-based policies that act on business state, eliminating the configuration drift and cloud waste typical of unmanaged fleets.
Kubernetes focuses on container orchestration, but the reality on the ground is far less forgiving. Provisioning a single cluster is a trivial Day-1 exercise. The true operational nightmare begins on Day 2. Teams that treat multi-cloud fleets like isolated pets inevitably face crushing YAML configuration drift, runaway AWS bills, and severe scaling bottlenecks.
Rancher solved the Day-1 problem of launching clusters across disparate bare-metal environments. But in 2026, launching clusters is no longer the bottleneck. The real failure point is Day-2: managing the operational chaos, security patching, and configuration drift on top of them. Rancher is a heavy, ops-focused fleet manager that completely ignores the application developer. If your goal is developer velocity and automated FinOps, you must graduate from basic fleet management to an intent-based Kubernetes Management Platform like Qovery.
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
.webp)