// the find
Qovery/engine
The Orchestration Engine To Deliver Self-Service Infrastructure ⚡️
Qovery Engine is a Rust library that sits between your application code and cloud provider APIs, using Terraform and Helm under the hood to provision Kubernetes clusters and deploy containerized apps. It's the open-source core of the Qovery commercial platform — a Heroku-like PaaS layer on top of EKS, GKE, and AKS. Aimed at teams that want self-service infrastructure without building their own internal developer platform from scratch.
The transaction model (create/rollback/commit) gives deployments an explicit state machine, which is the right mental model for infrastructure operations that can fail halfway through. Vendoring Helm charts directly into the repo under lib/ means your cluster bootstrap is reproducible without depending on upstream chart availability at deploy time. Karpenter integration for AWS node provisioning is a good choice over cluster-autoscaler — faster scale-up, more cost-efficient bin packing. Rust for this workload is a defensible call: long-running orchestration with heavy async I/O is exactly where you want ownership semantics and no GC pauses.
84 forks on a 2400-star repo is a telling ratio — this is used primarily as a backend for the commercial product, not something the community actually builds on. The README still shows Azure and GCP as 'vote to add' features behind links, which suggests the multi-cloud story is mostly marketing copy for AWS-centric reality. Calling Terraform and Helm as subprocesses (shelling out) rather than using their Go/Rust SDKs makes error handling brittle — you're parsing CLI output and hoping the binary version matches. If you want to run this standalone outside Qovery's control plane, you're mostly on your own: no first-party examples of how to wire it up without the commercial orchestrator.