Overview
Qovery Engine is the open-source abstraction layer that powers Qovery's deployment platform. Written in Rust, it lets you deploy applications and databases onto your own AWS, GCP, Azure, or Scaleway accounts with a Heroku-like workflow, handling Kubernetes, networking, and infrastructure provisioning under the hood.
Where it falls short of Heroku
- It is the engine/library, not a turnkey product; the full UX is tied to Qovery's (paid) control plane.
- Designed to provision cloud infrastructure, so it expects an AWS/GCP/Azure/Scaleway account rather than a single box.
- Standalone self-hosting without the Qovery platform is poorly documented.
- Smaller community and narrower scope than full PaaS dashboards.
We list the gaps honestly so you can decide if the trade-off is worth owning your data.
Tags
Claim this listing to keep it accurate, add a deploy template, or feature it on relevant pages.
Embed the Qovery Engine difficulty badge in your README — it links back here.
[](https://openreplace.com/qovery-engine)Similar open-source projects
Other self-hostable tools in the same space worth comparing.
Automatic HTTPS web server and reverse proxy with zero config TLS
Cloud-native HTTP reverse proxy and load balancer for microservices
Self-hostable Heroku/Netlify alternative for apps, databases, and services
Self-hosted PaaS to deploy apps and databases with Docker and Traefik