Looking Back on 2023 and Our Plans for 2024
A Year of Accomplishments
2023 was a pivotal year for Qovery, marked by milestones that have solidified our place as a leading cloud infrastructure platform. Here are some of our proudest achievements:
Exponential Usage Growth
We witnessed an exponential increase in the number of deployments on Qovery, surpassing the 230,000 deployments per month 🚀.
This growth demonstrates the increasing adoption of our product among platform engineers and developers who appreciate its simplicity and effectiveness.
Financial Growth
On the financial side, We experienced remarkable growth in 2023, with our revenue increasing 4x and our customer base expanding by 3x. Our sales pipeline for Q1 is already full, indicating strong momentum heading into 2024.
Highly Recognized
We were recognized for our excellence by being named a Momentum Leader for the second time in the Cloud Infrastructure Automation category and achieving the 8th consecutive High Performer award in G2's Cloud Infrastructure Automation category.
Game-Changing Product Enhancements
We introduced game-changing features, including job deployments, cronjobs, deployment order, parallel deployment, ARM instance type support, stable Qovery Terraform provider, and audit logs. These enhancements significantly enhanced Qovery's capabilities, making it even more versatile and user-friendly for platform and engineering teams. (See all our changelogs in 2023)
Outstanding Developer Experience
We remained steadfast in our commitment to providing developers with an exceptional experience. We focused on streamlining the deployment process, simplifying onboarding, and providing comprehensive documentation.
These efforts have made Qovery the preferred platform for more than 60000 developers worldwide.
Key Partnerships
We forged strategic partnerships with three innovative companies, Doppler, Kubecost, and Usage.AI, to enhance our platform and provide developers with a holistic cloud deployment and management experience.
What's new for 2024?
As we embark on 2024, we're excited to announce our ambitious plans for continued growth and innovation. On the product side, we're thrilled to announce:
- General Availability of GCP and Azure Support: We're expanding our reach to support two of the world's most popular cloud platforms, giving platform and engineering teams even more flexibility and choice.
- General Availability of Qovery BYOK: We're empowering our customers to bring their own Kubernetes clusters to Qovery, providing them with complete control over their infrastructure. Read more about Qovery BYOK...
- Further Development of Replibyte and Torii: We're deepening our commitment to open-source tools by enhancing Replibyte, our database seeding tool written in Rust, and Torii, our Internal Developer Portal.
On the business side, we're aiming for significant growth in 2024:
- 3x Customer Base and 4x Platform Usage: We're confident in tripling our customer base and quadrupling the usage of our platform, fueled by our commitment to innovation and customer satisfaction.
- Achieving Profitability: We're on track to achieve profitability in 2024, a testament to our strong financial position and continued focus on operational efficiency.
- Hiring: We're excited to open new positions in the coming weeks to sustain our growth and continue delivering innovative features that empower platform and engineering teams.
- Growing Partnerships: We're deepening our partnerships with our strategic partners, including AWS, Doppler, Kubecost, and Usage, and working with additional partners like GCP and Azure to expand our reach and deliver more value to our customers.
Our Commitment to Our Community
As we look to the future, we remain deeply grateful to our community of customers, employees, investors, and partners. Your support has been instrumental in our growth and success. We're committed to delivering exceptional experiences and driving innovation that empowers platform and engineering teams to build and ship tomorrow's applications.
To further strengthen our commitment to the community, we'll continue to invest in attending key industry events like AWS summits and re:invent, which have already demonstrated great ROI in terms of engagement and brand awareness.
We believe that these events provide an invaluable platform to connect with platform and engineering teams, showcase our product, and foster collaborative partnerships.
Together, we'll continue to revolutionize the cloud infrastructure landscape and empower developers to achieve their full potential. Stay tuned for more exciting announcements and developments as we embark on this journey together.
.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)