One week before the launch of Qovery v2 beta - What's new?
Qovery is the fastest way to deploy your apps in your AWS account
Mono repository support
The mono repository (or monorepo) support was the most common feature from our users for this release. The v2 supports it hassle-free. Here is a short video of a mono repository in action:
Faster app deployment
Our team built this release with Developer Experience obsession in mind. Our goal was to make you deploy your apps in less than 1 minute - with zero knowledge of Qovery. Here is a short video of a complete app deployment flow:
Web interface first
Our team has made a considerable investment to create a better experience using the web interface. This version fixes persistent bugs and slowness. The v2 is “web interface” first - meaning that the web interface is now the first way to interact with Qovery. It also tells that you no longer need to tweak a .qovery.yml file to configure your app - it has been removed.
Open API
Our new RESTful API has been designed to be easily usable by anyone. Automating any actions from your CI, scripts, or anything you want is now possible.
What’s next
This release is just the beginning; it put the foundation of our vision - making application deployment enjoyable and no longer a pain for any developer. Qovery is the simplest way for developers to deploy their apps in the Cloud.
Qovery v2 beta will be available to our registered users registered on the 22nd of June 2021. During the summer, our team will open the v2 to all users. You can expect a stable release in September 2021.
Next read: How Qovery billing works
.svg)
.svg)
.svg)
Suggested articles
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.
The structure, table, tool list, and code blocks are all worth keeping. The main work is fixing AI-isms in the prose, updating the case study to real metrics, correcting the FAQ format, and replacing the CTAs with the proper HTML blocks. The tool descriptions need the "Core strengths / Potential weaknesses" headers made less template-y, and the intro needs a sharper human voice.
For years, Red Hat OpenShift has been the safe choice for heavily regulated, on-premise environments. It operates as a secure fortress. But in the public cloud, that fortress acts as an expensive prison. Paying proprietary per-core licensing fees on top of your standard AWS or GCP compute bill is a redundant "middleware tax." Escaping OpenShift requires decoupling your infrastructure from your developer experience by running standard, vanilla Kubernetes paired with an agentic control plane.
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 focuses on container orchestration, but the reality on the ground is far less forgiving. Provisioning a single cluster is a trivial Day-1 exercise. The true operational nightmare begins on Day 2. Teams that treat multi-cloud fleets like isolated pets inevitably face crushing YAML configuration drift, runaway AWS bills, and severe scaling bottlenecks.
.webp)