Seamless Cloud account management đ - The Future of Qovery - Week #8
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 easiest way to deploy your database - The Future of Qovery - Week #7
Seamless Cloud account management đ
You may be familiar with the AWS web console and how complex it is to have a complete overview of what's going on. You may wonder:
- How many services are running?
- How much is it going to cost?
- How to optimize my resource consumption?
Those questions are legitimate. And even if they are not directly linked to Qovery, we want to help you better clarify what happens on your Cloud account. That's why we worked on a brand new Cloud account management console with our product team. In the next version of Qovery, you will gain visibility on your infrastructure. Helping you to optimize your resource consumption and better use the Cloud.
Simplicity
Using Qovery on your Cloud account is as simple as creating a Cluster and binding your Cloud Service Provider through the settings.
Today we support AWS and Digital Ocean (beta). And we plan to add Scaleway for Q3 2021 and Google Cloud Platform for Q4 2021.
Invite your teammates đ«
Qovery empowers developer collaboration. You will have the ability to give access to your teammates with appropriate roles: admin, developer, and viewer. Once again, if you are familiar with IAM from AWS, you see how easy it is to onboard your team. You no longer need to slam your head against the IAM wall. Life is more straightforward, and you can go back to work.
Manage multiple Cloud accounts đ
Wow, this is the most fantastic feature ever, right? đ. But this is not exactly what you think. At Qovery, we provide pragmatic multi-cloud. Meaning, you can add clusters to different Cloud Service Providers to reduce your Cloud cost based on the reliability needed for your workload.
The most pragmatic choice that you can make is:
- Keep your production workload on a reliable Cloud provider.
- Put your development workload on the cheapest Cloud provider.
Doing this way makes you able to reduce your Cloud cost per four đ”!! Which is a considerable cost saving without any downside because you keep the same great Qovery experience. This is 100% transparent for you. There is no magic. This is just how Qovery works by design.
Clarity on Cluster auto-scaling đ
Cluster auto-scaling is a vast topic. You may have heard about vertical auto-scaling, horizontal auto-scaling, and even multidimensional autoscaling đš - this is super complex... That's why we decided to simplify all of that and make it evident for you.
What our customers want is to pay only what they use, and that's it. That's the promise of the Cloud. So with Qovery, you choose the number of nodes you want and the CPU and the RAM per node of your cluster. That's it. Qovery takes care of scaling up or down your nodes based on your actual workload. Magic? Once again, it is not. We are just working hard to make it works.
Transparent pricing đ°
To build a product that you love, we need to hire the best engineers out there. And to have the best, we need to give them reasonable compensation. Our business model is based on the number of apps Qovery manages for you and not based on what you consume on your Cloud account. Providing you with transparent pricing is critical. From the web console, you know how much Qovery costs for you in real-time.
Conclusion
Getting started to deploy your apps on your Cloud account should not be more complicated than the experience provided by Qovery. In 15 minutes, you can access the deployment stack that you would build for your company. 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 on Discord.
--
See you next week -- same hour, same place đ
Romaric from Qovery -- We are hiring.
.svg)
.svg)
.svg)
Suggested articles
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.
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.
.webp)