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
At enterprise scale, managing provider-specific Kubernetes YAML across multiple clouds creates crippling configuration drift and operational toil. By adopting an agentic Kubernetes management platform, infrastructure teams abstract cloud-specific configurations (like ingress controllers and storage classes) into a single, declarative intent that automatically reconciles across 1,000+ clusters.
To stop GPU costs from destroying SaaS margins, teams must transition from static to consumption-based infrastructure by utilizing Karpenter for dynamic provisioning, maximizing hardware density with NVIDIA MIG, and leveraging Qovery to tie scaling directly to business metrics.
AI is helping developers write more code, faster than ever. But writing code is only half the story. What happens after? Building, deploying, debugging, scaling. That's where teams still lose hours.We're building Qovery for this era. Not just to deploy your code, but to make everything that comes after writing it just as fast.
By adopting GitOps and utilizing management platforms like Qovery, fintech teams can automatically generate DORA-compliant audit trails, transforming regulatory compliance from a manual, time-consuming chore into an automated, native byproduct of their infrastructure.
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.
.webp)