Are you ready for 2022?
Qovery is the simplest way to deploy your apps on AWS
2019, 2020, and 2021 in a nutshell
When we started Qovery in October 2019, we were 3 - Pierre (CTO), Morgan (CRO), and I (CEO). No user, no employee, no product. Today:
- 15237 developers from more than 100 countries use Qovery to deploy their applications on AWS (and other cloud providers).
- The Qovery team is composed of 15 outstanding people. Thanks to Patryk J., Benjamin D., Romain G., Yaël F., Enzo R., Benjamin C., Rémi B., Albane T., Florian L., Yann I., Tiago S., Bilel B., Morgan P., Pierre M., Romaric P.
- Qovery is an outstanding product used by fast-growing SaaS companies in Healthcare, Insurtech, Fintech industries.
- We fundraised $5 million in total from the co-founders of Datadog, Docker, Contentsquare and Crane VC, SpeedInvest VC.
What’s next for 2022?
New features
At Qovery, we build the future of the cloud, and to succeed in our journey, we need to give access to the most expected features by our customers. For 2022, you can expect to see the support of the Cronjobs, Lambdas, and even a Marketplace. We also plan to support 2 new cloud providers, Google Cloud Platform and Microsoft Azure. Check out our public roadmap for further details.
Qovery v3
Since we launched Qovery in January 2020, we have dedicated our time to making our platform production-ready for our customers. We took 2 years to build a product that you can use every day with extraordinary stability and excellent performance. The Qovery v3 will deliver the best Developer Experience out there. I am not going to give more details about it. But if you were delighted to use Qovery v2, you will be shocked how Qovery v3 will revolutionize the way you ship your products. Stay tuned; we will talk more about it in January 2022.
Continue to make our customers successful
First of all, thanks to all our customers in North America, South America, Europe, Africa, Asia, and Australia. We are so grateful for the trust you’ve placed in us, and our team is dedicated to making you succeed in your journey. We can’t wait to see what we will build together in 2022.
In 2022, we will continue to invest in support and close contact with our customers. It is part of what we call the “Qovery Experience”. Running production infrastructure deserved a high-quality product and team. We will continue investing in the Qovery Experience to make our customers successful in what they build.
Building the future of the cloud
We proudly own the domain meta.cloud and we didn’t want to sell it to… {you know who}. Our plan since day 1 is to build the future of the cloud. Meaning, helping the next generation of developers to build the next generation of applications in the cloud. And for that, we need to start to build the main foundations. Helping junior, experienced, senior developers to deploy their applications in the cloud is the first milestone. We will talk about the second milestone in the coming weeks. Stay tuned!
Hiring
Needless to say, to reach the very high level of our ambitions, we are hiring talented people. Check out our open positions here.
Purple is the new black
The Qovery team is ready to paint the cloud world purple. And speaking of “purple”: Pantone just announced the color of the year 2022. And guess what, it’s a shade of purple! A sign? I like to think so.
2022 looks already an extraordinary one!
--
Thank you! We would seriously not have done this without you and we hope you are as excited and pumped for 2022 as we are!
All the best to you and your loved ones,
The Qovery team
.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)