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
Kubernetes success is determined by Day 2 execution, not Day 1 deployment. While migration is a bounded project, maintenance is an infinite loop that often consumes 40% of senior engineering capacity. To protect margins and velocity, enterprises must transition from manual toil to agentic automation that handles scaling, security, and cost.
Day-0 is planning, Day-1 is deployment, and Day-2 is the infinite lifecycle of maintenance. While Day-0/1 are foundational, Day-2 is where enterprise operational debt accumulates. At fleet scale (1,000+ clusters), managing these differences manually is impossible, requiring agentic automation to maintain stability and eliminate toil.
A multi-cluster Kubernetes architecture distributes application workloads across geographically separated clusters rather than a single environment. This strategy strictly isolates failure domains, ensures regional data compliance, and guarantees global high availability, but demands centralized Day-2 control to prevent exponential cloud costs and operational sprawl.
Stop overpaying for Kubernetes observability. Learn how in-cluster monitoring and AI-driven troubleshooting with Qovery Observe can eliminate APM ingestion fees, reduce SRE bottlenecks, and make your cloud costs predictable.
Kubernetes multi-cluster management is the Day-2 operational practice of orchestrating applications, security, and configurations across geographically distributed clusters. Because native Kubernetes was designed for single-cluster orchestration, enterprise platform teams must implement a centralized control plane to prevent configuration drift and manage a global fleet without scaling manual toil.
Achieving zero-downtime deployments on Kubernetes requires more than running multiple pods. It demands a standardized architecture utilizing Pod Disruption Budgets (PDBs), precise liveness and readiness probes, pod anti-affinity, and graceful termination handling. At an enterprise scale, these configurations must be enforced via a centralized control plane to prevent catastrophic configuration drift.
.webp)