We raised $1M pre-seed round to simplify application deployment in the Cloud
Qovery is a DevOps Automation tool for developers. It helps any developer to deploy their applications in the cloud in seconds instead of days. Read more on Techcrunch...
“This pre-seed round is a great step for Qovery. Amazing business angels with strong Cloud industry expertise jumped on board. We are in a position to strengthen the team and tackle our next challenges with confidence. The coming months are going to be very exciting for Qovery.” - Romaric Philogene, CEO of Qovery.
Qovery was founded in 2019 by two experienced former engineers (Romaric Philogene and Pierre Mavro) at Red-Hat, Criteo, and Ullink. The Company has participated in the prestigious Techstars acceleration program in late 2019. A few months later, the Company raised $1M with top-notch investors from the best tech companies. Since then, the Company has expanded its footprint both in Europe and in the US.
Join us in making the Cloud simple again!
.svg)
.svg)
.svg)
Suggested articles
Scale your engineering organization without the headcount hit. Compare the top 10 DevOps automation tools for mid-market teams, from IaC leaders like Terraform to unified platforms like Qovery.
Static delivery pipelines are becoming a bottleneck. The best CI/CD tools for Kubernetes are those that move beyond simple code builds to provide total environment orchestration and developer self-service.
The Broadcom acquisition of VMware has sent shockwaves through the enterprise world, with many organizations facing license cost increases of 2x to 5x. If you are looking to escape rising TCO and rigid subscription bundles, these are the top vSphere alternatives for a modern hybrid cloud.
Is the "Heroku Tax" draining your budget? Compare Heroku vs. Kubernetes in 2026. Learn how to solve complex orchestration challenges, like queue-based autoscaling and microservice sprawl, without the DevOps toil.
Is the EKS operational burden outweighing its benefits? Learn how to migrate from EKS to ECS, the technical trade-offs of AWS-native orchestration, and how to get ECS-level simplicity without losing Kubernetes power.
.webp)