Discover 8 New Major Features on Qovery - May 2024 Edition
Watch the complete Qovery Demo Day May 2024 here.
1. Qovery on Your Local Machine
Now, you can try Qovery on your local machine with just one command: qovery demo up. The only requirements are Docker running and 2 vCPU with 4GB RAM available. This feature allows you to explore Qovery without any restrictions or time limits, completely free of charge.
Check out the announcement.
2. Bring Your Own Kubernetes with Qovery
Installing Qovery on your Kubernetes cluster is now straightforward with the command qovery cluster install. This command initiates a simple wizard that generates a Helm chart for you to review and apply. This feature is fully accessible without any restrictions or time limits, and it is free.
Check out the documentation.
3. Manage Kubernetes Annotations
Qovery now allows you to manage your Kubernetes annotations with an intuitive and powerful interface, giving you greater control over your Kubernetes deployments.
Check out the announcement.
4. Karpenter Integration
We have rolled out Karpenter, a highly cost-efficient Kubernetes node autoscaler, in public beta. Karpenter supports spot instances and GPUs, enabling significant cost savings on AWS. Learn more about Karpenter and how it can reduce your AWS costs by up to 60% here. Check out this article for deploying AI applications with GPUs on AWS EKS and Karpenter.
Click here to join the beta
5. Helm Deployment Improvement
We have simplified Helm deployments by eliminating the need to add Qovery macros into your Helm values file. Qovery now automatically injects them via a Kubernetes Admission Controller, making the deployment process smoother.
6. Qovery Cloudshell
Access your applications and databases with Qovery's remote shell access directly from your web browser. With one click, you're connected to your apps, providing a seamless remote access experience.
7. New Service List
We are continually working to simplify the deployment of any type of application within Qovery. Our new service list is designed to make this process more intuitive, ensuring quick and easy application deployment.
8. Contextual Helper
We have introduced a consistent way to offer assistance within Qovery at any point in your journey. The contextual helper provides comprehensive help from our documentation, forum, and, if needed, our support engineering team.
Bonus: Qovery Portal
Watch the end of our demo day to discover the Qovery Portal and get a sneak peek at what we are preparing for Qovery V4.
It's a wrap
Our commitment at Qovery is to make the most enjoyable Internal Developer Platform for Platform Engineers and Developers. We aim to continuously innovate and improve, ensuring that our platform remains intuitive, powerful, and developer-friendly. Stay tuned for more exciting updates and features as we strive to enhance your development experience.
.svg)
.svg)
.svg)
Suggested articles
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 biggest mistake enterprises make when evaluating Kubernetes management platforms is confusing infrastructure provisioning with Day-2 operations. Tools like Terraform or kOps are excellent for spinning up the underlying EC2 instances and networking, but they do absolutely nothing to prevent configuration drift, automate certificate rotation, or right-size your idle workloads once the cluster is actually running.
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.
Rancher solved the Day-1 problem of launching clusters across disparate bare-metal environments. But in 2026, launching clusters is no longer the bottleneck. The real failure point is Day-2: managing the operational chaos, security patching, and configuration drift on top of them. Rancher is a heavy, ops-focused fleet manager that completely ignores the application developer. If your goal is developer velocity and automated FinOps, you must graduate from basic fleet management to an intent-based Kubernetes Management Platform like Qovery.
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
.webp)