Qovery is an internal developer platform that sits on top of a customer’s own AWS, GCP, Azure, or Scaleway account and provides a Heroku-style experience for deploying applications to Kubernetes. Unlike fully-hosted PaaS offerings, Qovery runs the workloads in the customer’s own VPC on EKS, GKE, AKS, or a self-managed cluster, with Qovery only acting as the control plane.
The platform is organized around Organizations, Projects, Environments, and Services. Services can be containers, Git-backed applications (built with Buildpacks or Dockerfiles), managed databases (RDS, Cloud SQL, or in-cluster), Helm charts, Terraform modules, lifecycle jobs, or cron jobs. Each Environment is a self-contained namespace with its own ingress, databases, and configuration, which makes ephemeral preview environments per pull request straightforward. Qovery’s engine, written in Rust and open-sourced on GitHub, handles the reconciliation loop: reading desired state from the Qovery API and applying the necessary Terraform, Helm, and Kubernetes operations.
Qovery integrates with GitHub, GitLab, and Bitbucket for Git-driven deploys, with Datadog/New Relic for observability, and exposes a CLI, Terraform provider, and REST API for automation. Its target audience is engineering teams that have outgrown Heroku/Render but don’t want to build a platform team from scratch on top of raw Kubernetes.