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
Kubernetes success is determined by Day 2 execution, not Day 1 deployment. While migration is a bounded project, maintenance is an infinite loop that often consumes 40% of senior engineering capacity. To protect margins and velocity, enterprises must transition from manual toil to agentic automation that handles scaling, security, and cost.
Day-0 is planning, Day-1 is deployment, and Day-2 is the infinite lifecycle of maintenance. While Day-0/1 are foundational, Day-2 is where enterprise operational debt accumulates. At fleet scale (1,000+ clusters), managing these differences manually is impossible, requiring agentic automation to maintain stability and eliminate toil.
A multi-cluster Kubernetes architecture distributes application workloads across geographically separated clusters rather than a single environment. This strategy strictly isolates failure domains, ensures regional data compliance, and guarantees global high availability, but demands centralized Day-2 control to prevent exponential cloud costs and operational sprawl.
Stop overpaying for Kubernetes observability. Learn how in-cluster monitoring and AI-driven troubleshooting with Qovery Observe can eliminate APM ingestion fees, reduce SRE bottlenecks, and make your cloud costs predictable.
Kubernetes multi-cluster management is the Day-2 operational practice of orchestrating applications, security, and configurations across geographically distributed clusters. Because native Kubernetes was designed for single-cluster orchestration, enterprise platform teams must implement a centralized control plane to prevent configuration drift and manage a global fleet without scaling manual toil.
Achieving zero-downtime deployments on Kubernetes requires more than running multiple pods. It demands a standardized architecture utilizing Pod Disruption Budgets (PDBs), precise liveness and readiness probes, pod anti-affinity, and graceful termination handling. At an enterprise scale, these configurations must be enforced via a centralized control plane to prevent catastrophic configuration drift.
.webp)