Product Update #37 - Deploy your apps on your AWS account ☁️
New Features
Deploy your apps on your AWS account
Finally, you can now install Qovery on your AWS account directly from the web interface. This is huge! In less than 30 minutes, Qovery is installed, then you can deploy your apps on your AWS account. And you know what? It's free up to 10 apps forever. Give it a try now! ⚡️
*No credit card required.
Buildpacks: Dockerfile is now optional (Beta)
To simplify application deployment, Qovery supports Buildpacks out of the box. Buildpacks determine the build process for an app and which assets and runtimes should be made available to your code at runtime. If your complex apps are running multiple languages, you can also use multiple buildpacks within a single app. Meaning, as a developer, you don't need to write a Dockerfile to build and run your app. Qovery Buildpacks takes care of everything for you. Read more...
Supported languages:
- Ruby
- Java
- Node.JS
- Python
- Javascript
- Typescript
- Python
- Golang
- PHP
We aim to support more languages like Rust and Kotlin in the coming weeks.
This feature is still fresh, so fallback on Dockerfile if app deployment goes wrong.
Improvements
instant TLS certificate delivery
We improved TLS certificate delivery for a newly deployed app. Now you no longer need to wait to have a valid TLS certificate (before you had to wait 1 minute or more).
Coming soon
Improved logs interface
We are improving the logs interface. Here are 2 screenshots of what we prepared.
Do you prefer Dark or Light? Vote by joining our Discord. We'll implement your favorite one first :)
Jobs
Feel free to let us know what you think by replying to this email or joining our Discord server.
The Qovery team 👋
.svg)
.svg)
.svg)
Suggested articles
The part teams consistently underestimate is that OPA Gatekeeper, the tool most people reach for first, only enforces policy at the cluster level. It blocks non-compliant resources from being created within a single cluster. Propagating consistent Gatekeeper policies across 300 clusters, and detecting when those policies drift, is a fleet orchestration problem that Gatekeeper was not designed to solve.
Training a model in a notebook is easy. What breaks teams is the step after, serving it reliably without haemorrhaging cloud budget or burying your SREs in YAML. The common trap: picking a platform that handles the model but not the surrounding stack. An AI deployment platform should orchestrate the full application graph (inference endpoints, vector databases, caching layers, and frontends) inside a single VPC, with GPU autoscaling that doesn't require a dedicated platform engineer to babysit.
The mistake teams make early is assuming Kubernetes namespaces provide sufficient isolation between workloads or teams. They do not. Namespaces share the control plane, the node pool, and the underlying network fabric. A misconfigured workload in one namespace can exhaust node capacity or crash the API server for every other namespace simultaneously. That is when the multi-cluster conversation starts.
Migrating from nginx Ingress to Envoy Gateway? Discover how Alan migrated 100+ services in one month, the technical hurdles they faced (like Content-Length normalization), and why staging isn't always enough.
Kubernetes assigns an entire physical GPU to a single pod by default. NVIDIA MIG solves the hardware partitioning side: one A100 becomes up to seven isolated slices. The part teams underestimate is the orchestration layer: device plugin configuration, node labeling, taints, and pod affinity rules all need to be correct before Kubernetes can actually schedule onto those slices.
The cluster coming up is the easy part. What catches teams off guard is what happens six months later: certificates expire without a single alert, node pools run at 40% over-provisioned because nobody revisited the initial resource requests, and a manual kubectl patch applied during a 2am incident is now permanent state. Agentic control planes enforce declared state continuously. Monitoring tools just report the problem.
The instinct when setting up Kubernetes observability is to instrument everything and send it all to your APM vendor. That works fine at ten nodes. At a hundred, the bill becomes a board-level conversation. The less obvious problem is the fix most teams reach for: aggressive sampling. That is how intermittent failures affecting 1% of requests disappear from your monitoring entirely.
Scaling your deployments to zero is only half the battle. If your cluster autoscaler does not aggressively bin-pack and terminate the underlying worker nodes, you are still paying for idle metal. True environment sleeping requires tight integration between your ingress layer and your node provisioner to actually realize FinOps savings.
.webp)