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 is a distributed orchestration engine that automates container deployment and scaling. At an enterprise level, its core mechanisms—control planes, schedulers, and worker nodes—provide foundational infrastructure resiliency. However, operating these components natively across thousands of clusters creates massive configuration drift, requiring intent-based control planes to manage Day-2 FinOps, RBAC, and multi-cloud abstraction globally.
Kubernetes autoscaling relies on three dimensions: horizontal (pod count), vertical (resource size), and cluster (node count). While CPU-based scaling is standard, enterprise fleets require advanced Day-2 strategies (such as custom Prometheus metrics and priority-class overprovisioning) to prevent node boot delays and memory bottlenecks during severe traffic spikes.
Agentic Kubernetes resource reclamation is the practice of using an autonomous control plane to continuously identify, suspend, and delete idle infrastructure across a multi-cloud Kubernetes fleet. It replaces manual cleanup and reactive autoscaling with intent-based policies that act on business state, eliminating the configuration drift and cloud waste typical of unmanaged fleets.
Kubernetes is an open-source container orchestration engine. At enterprise scale, it abstracts infrastructure to automate deployment, scaling, and networking. However, managing hundreds of clusters introduces severe Day-2 operational toil, requiring agentic control planes to enforce global governance, security policies, and cost optimizations across multi-cloud fleets.
The shift from AI copilots to autonomous agents is redefining infrastructure requirements. Discover how to build secure, stateful, and compliant Agentic AI systems using Kubernetes, sandboxing, and observability while meeting EU AI Act standards
Effective Kubernetes management in 2026 demands a shift from manual cluster building to intent-based fleet orchestration. By implementing agentic automation on standard EKS, GKE, or AKS clusters, enterprises eliminate operational weight, prevent configuration drift, and proactively control cloud spend without vendor lock-in, enabling effective scaling across massive fleets.
A Kubernetes single pane of glass is a centralized management layer that unifies visibility, access control, cost allocation, and policy enforcement across § cluster in an enterprise fleet for all cloud providers. It replaces the fragmented practice of switching between AWS, GCP, and Azure consoles to govern infrastructure, giving platform teams a single source of truth for multi-cloud Kubernetes operations.
Deploying a Docker container on Kubernetes requires building an image, authenticating with a registry, writing YAML deployment manifests, configuring services, and executing kubectl commands. While necessary to understand, executing this manual workflow across thousands of clusters causes severe configuration drift. Enterprise platform teams use agentic platforms to automate the entire deployment lifecycle.
.webp)