Deploy goes
beyond ArgoCD.
Containers, Terraform modules, managed databases, Helm charts - deployed together, rolled back together, previewed per PR. The unit of deploy is the environment, not the pod.
Apps and infra
live in
two worlds.
Your app deploys from ArgoCD. Your database from Terraform. Your third-party service from a custom script. Rollback means reverting all three, in the right order, at 2am. Deploy is the layer that treats the whole environment as one unit.
Apps + infra are two worlds
Terraform for infra, ArgoCD for apps, a script for the rest. Rollback means reverting all three in the right order.
Every team picks a different CI
GitHub Actions, GitLab CI, Jenkins, CircleCI - your platform team writes adapters for all of them. Forever.
External services are first-class
Redis, Postgres, S3, a third-party webhook - all part of your service graph. None of them deploy the same way.
The whole unit,
shipped.
Six capabilities that unify everything your team ships into one deployable graph. Apps, databases, Terraform, Helm - previewed, deployed, rolled back together.
Containers, managed databases, cron jobs, lifecycle jobs - all in the same environment definition. Deployed together.
Terraform modules are first-class. Deploy them alongside your apps. State managed. No separate pipeline.
Redis, S3, Stripe webhooks, any managed resource - declared, provisioned, and wired into your service graph.
GitHub Actions, GitLab CI, Jenkins, CircleCI - or no CI at all. Qovery builds and pushes. Your CI can still trigger.
Every PR gets its own full-stack environment. Apps, databases, seeded data. Merged → gone. < 30 seconds typical.
Progressive delivery strategies out of the box. One-click rollback that reverts the whole environment, not just one pod.
Your pipeline,
still yours.
Deploy does not replace your CI. It replaces the part that nobody wants to maintain - the deployment pipeline that glues build to cluster.
Trigger on push, PR, or tag. Qovery deploys after build.
Same pipeline, Qovery as the deploy step. No rewrites.
Existing ArgoCD? Qovery can orchestrate alongside, not replace.
Webhook trigger. Call the API. Qovery handles the rollout.
Inline modules or external state. First-class, not bolted on.
Helm charts deployed as services. Values per environment.
Any OCI image. Buildpacks or Dockerfile. Your registry or ours.
Monorepo support. Affected-only deploys. Change detection baked in.
The agent
ships the unit.
The Agentic layer treats the environment as one deployable thing. Ask it to add a cache, wire a webhook, clone prod - it drafts the plan, you approve.
Fixes the graph, not the pod
The agent understands that adding Redis means updating the app config, the network policy, and the cost forecast. One prompt, all three.
Wires dependencies for you
Secrets, environment variables, service discovery - the agent writes the glue that your team hates writing manually.
Tests before prod
Deploy to staging, run the tests, show the results, then ask for prod approval. The same workflow your team already trusts, now automated.
"We stopped arguing about whether to use ArgoCD or Flux. Qovery just deploys everything - apps, Terraform, databases - in one graph. Our Friday deploys went from stressful to boring."
Ship the whole unit,
not the pods.
Connect your repo and your cluster. Deploy apps, databases, Terraform modules, and Helm charts as one environment. Preview per PR. Rollback with one click.