New Pricing that Will Give You Peace of Mind
A new article has been published here to explain how pricing works with concrete examples
Why and What’s Your Benefit?
As you might know, Qovery provides on-demand environments on AWS that allow any engineering team to significantly faster deployments without friction and risk. We initially based our pricing model on this deployment value (we charged by the number of deployments), and as much as it can be convenient for some users, we realized that it could be a source of stress for most. The difficulty of predicting how much you are going to pay at the end of the month and the fact that the bill can vary from one month to the other even pushed some of you to disable some of our key features, such as the “Preview Environment” since it increases the number of deployments.
With our new pricing model, you can leave those fears and say hello to unlimited deployments and a bill based on your organization’s active users!
What is The New Pricing?
As mentioned, we are moving our pricing from the number of deployments ($50 per 100 deployments/month) to per active user (starting from $49/month/user).
What is an Active User?
An Active User is someone who made a code change on git or deployed an application in the last 30 days. We do not count contributions to public (open-source) repositories.
Before vs. After
Free Plan
The free plan remains (obviously) free. You still get the community support (Forum), but you now have access to the Preview Environment Feature, an unlimited number of developers, 1 cluster, and up to 5 Environments.
Team Plan (former Professional Plan)
The Professional Plan is now the Team Plan! You still get all the FREE features and 24/5 support (email and chat), but the main difference is that you now get unlimited deployment and environments, and rather than being charged by deployments, you now pay by active users.
Business Plan (removed)
The Business plan has been removed for simplicity since most customers subscribed to the Professional and Enterprise plans.
Enterprise Plan
You still get all the TEAM features (like unlimited deployments). Still, you also have unlimited clusters, extended security and compliance, usage reports, role-based access control (RBAC), and custom customer support.
If you want to see everything in detail, the before and afters are just below.
When will this change be effective?
If you are an existing monthly customer
The change will be effective from the 1st of October 2022, so you have plenty of time to get used to it.
If you are an existing yearly customer
The change will be effective at the renewal of your yearly contract.
If you are a new customer
The new pricing will be effective right now! So don’t hesitate and give it a try to Qovery 💜
Summary
Qovery keeps on growing, and while we do, we want to ensure that you can grow, too by enjoying every feature you need without the stress of higher costs at the end of the month. The deployment should not be a hindrance. It is even the core of Qovery's value. With this new pricing model, you will be empowered, but you will also be given the transparency and predictability you need to achieve anything you need to.
We hope you will enjoy this new and more transparent pricing, and don’t hesitate to contact us in the Forum if you need any extra information or have any questions!
.svg)
.svg)
.svg)
Suggested articles
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.
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)