Qovery goes beyond app deployment - The Future of Qovery - Week #5
This series will reveal all the changes and features you will get in the next major release of Qovery. Let's go!
Read the previous article: The Future of Qovery - Week #4.
Build > Test > Deploy > Run: Qovery goes beyond app deployment.
Qovery does not reinvent the wheel. Tons of great products like Gitlab CI, Datadog, Grafana, or Sentry exist in the market. The goal of Qovery is to provide anyone with a deployment platform working out of the box. By plugging third-party products, you extend the capabilities of Qovery and go beyond app deployment. This is with this philosophy that we announce the development of our addons system 🥳.
App build and test
CI/CD (Continuous Integration / Continuous Deployment) is a common term to describe a product in charge of building and running your applications' tests. Qovery is a state-of-the-art CD with some CI features. Products like Gitlab CI, Circle CI, or Github Actions are mostly CI with some CD features. Our next release of Qovery will let you plug your CI to take advantage of your existing CI stack. However, no worries if you don't have a CI; Qovery has an integrated one.
App deployment
Once your app is built and tested, it's time to be deployed. Based on "deployment rules", Qovery will deploy your app on your Cloud account.
Deployment rules let you configure:
- "Auto deploy" when a git push is received.
- "Auto delete" when a git branch is deleted.
- On which cluster, cloud provider, and region your environment* must be deployed.
- When your environments need to start and stop (to reduce your Cloud cost).
All those options make Qovery the perfect choice to get started using the Cloud 👌.
*An environment is a bunch of applications running altogether.
App run
Your app has been deployed, and now it runs. Qovery ensures that your app runs and will continue to run even if something goes wrong. In the next Qovery release, we will provide you with all the required information to make sure your app is running perfectly.
This lightweight monitoring is perfect for having a big picture of what's going on in your application. If you need to go further, you will be able to plug Datadog or NewRelic in a single click 💪.
Conclusion
Qovery's DevOps automation software manages your entire deployment pipeline and beyond. From building your application to deploying it and managing it during the run. This is what we call a state-of-the-art Continuous Deployment platform. Even if all those concepts are abstracted, it's essential to know where Qovery acts and how you can combine it with your existing tech stack. My team and I are excited to release our next major version of Qovery. If you are interested in joining the beta in early June, let me know by contacting us on Discord.
--
See you next week -- same hour, same place 👋
Romaric from Qovery -- We are hiring.
.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)