Blog
Platform Engineering
DevOps
Kubernetes
Product
5
minutes

Beta Announcement: Bring Your Own Kubernetes with Qovery

Today marks a significant milestone for Qovery and a highly anticipated evolution of our product, especially among Platform Engineers and DevOps professionals. We're thrilled to announce the "Bring Your Own Kubernetes" (BYOK) offer in beta access, a transformative step in our journey towards more flexible and adaptive infrastructure management. Please keep reading to understand why we extend our offer.
September 26, 2025
Romaric Philogène
CEO & Co-founder
Summary
Twitter icon
linkedin icon
Update May 2024: Documentation to install Qovery on your Kubernetes cluster

Why We Developed BYOK for Qovery

1. Enhanced Control Over Network and Security

Network and security configurations are critical aspects of infrastructure management. With our previous offerings, certain limitations existed - for instance, integrating tools like Istio or using custom ConfigMaps for security enhancements wasn't feasible. The BYOK model changes this landscape. Now, Qovery adapts to your infrastructure requirements, not vice versa. This flexibility ensures that your unique network and security needs are met seamlessly.

2. Providing Outstanding Developer Experience to Everyone

The heart of Qovery’s philosophy is the commitment to delivering an outstanding Developer Experience. We understand that many companies have already invested in Kubernetes and should not be excluded from the Qovery experience. BYOK is our response to this need. It allows companies with existing Kubernetes infrastructure to leverage the full power of Qovery's features and capabilities, enhancing productivity and efficiency without compromising on the familiar Kubernetes environment they have cultivated.

3. Uniform Experience Across Environments

Many of our customers who enjoyed Qovery on their cloud infrastructure expressed a desire to have the same experience on their on-premise setups. BYOK addresses this by offering a uniform Qovery experience across various environments.

Use Qovery with any Kubernetes regardless where your Kubernetes runs

Whether it's cloud, on-premise, or even a local setup on your laptop, BYOK ensures Qovery runs smoothly, aligning with our vision of streamlined infrastructure management.

4. Aligning with Our Vision of Streamlined Infrastructure

Our BYOK offering is a testament to our vision of simplifying and streamlining infrastructure management, regardless of the environment. It represents a significant stride in making advanced DevOps capabilities accessible to a wider range of organizations and setups, reinforcing our dedication to innovation and user empowerment.

Technical Deep-Dive

Our BYOK feature is designed with installation simplicity and technical robustness at its core. Here's a closer look at how it works and what it entails:

Easy Installation

Installing Qovery on your Kubernetes cluster is straightforward. With just a single command helm install qovery, you can run Qovery on your cluster.

$ qovery cluster install

(Check out our full documentation here)

This simplicity is a game changer for DevOps teams, significantly reducing the complexity and time usually associated with setting up such powerful tools.

How it Works

Once installed, Qovery integrates seamlessly into your existing Kubernetes infrastructure. It acts as an operator, providing an intuitive interface and a set of tools that enhance your Kubernetes experience.

Qovery binaries (written in Rust) run on your Kubernetes cluster and connect to the Qovery control plane

This integration allows for advanced management capabilities without altering the fundamental aspects of your Kubernetes setup, ensuring that your existing configurations and customizations remain intact. If you want to learn more about how it works - I recommend this article.

Kubernetes Compatibility

To ensure a smooth and reliable experience, BYOK has specific version requirements, but basically, it will always work with the 3 latest versions of Kubernetes. At the time when this article was written, Kubernetes versions 1.26, 1.27, and 1.28. This compatibility ensures that you can leverage the latest advancements in Kubernetes while maintaining a stable and efficient environment.

Kubernetes Managed By Qovery vs. BYOK

While BYOK introduces a new dimension to our offerings, it's important to highlight that our managed Kubernetes service remains a vital component of Qovery's ecosystem.

Qovery proposes 2 offers! The Managed Kubernetes offer, where Qovery manages the setup and the maintenance of Kubernetes, and the BYOK (Self-Managed)

This service is designed for those who prefer a hands-off approach, where we handle the intricacies of Kubernetes management. It's about offering choices - while BYOK serves those seeking control and customization, our managed service caters to those who value convenience and simplicity. This dual approach ensures that Qovery meets the diverse needs of our clientele today and in the future.

Comparison Table

To help you better understand the differences between BYOK and our managed Kubernetes service, we've prepared a detailed comparison table, outlining key features and use cases for each.

Q-MARKDOWN
| Feature/Aspect | Qovery Managed Kubernetes | Qovery BYOK (Bring Your Own Kubernetes) |
|---------------------------------|---------------------------|----------------------------------------|
| **Installation** | Fully managed by Qovery | User-installed with `helm install qovery` |
| **Kubernetes Version Support** | Managed and updated by Qovery | Compatible with the 3 latest Kubernetes versions |
| **Infrastructure Management** | Handled entirely by Qovery | User-managed infrastructure |
| **Customization and Control** | Standardized setup | High customization and control over cluster configuration |
| **Security and Compliance** | Qovery’s security standards | User-defined security and compliance settings |
| **Network Configuration** | Managed by Qovery | Fully customizable by the user |
| **Ease of Use** | Simplified, minimal user intervention | Requires Kubernetes knowledge for setup and management |
| **Target Audience** | Companies preferring hands-off approach | Organizations seeking control and customization |
| **Integration with Tools** | Pre-integrated tools by Qovery | User-defined tool integrations |
| **Cost and Resource Management**| Managed by Qovery | Managed by the user, allowing for tailored cost optimization |
| **Support and Maintenance** | Provided by Qovery | Self-managed, with community and Qovery support available |

FAQ

We understand you might have questions about BYOK. That's why we've created a thread on our forum where you can ask all your questions 🤗

Conclusion

The introduction of BYOK is more than just a product update; it's a reflection of our commitment to evolving with our users' needs, providing flexibility, control, and a seamless experience across various infrastructures. Whether you choose BYOK or our managed Kubernetes service, Qovery remains dedicated to simplifying your DevOps and platform experience to align with our vision of streamlined and accessible infrastructure management for all.

Get Access to BYOK here
Share on :
Twitter icon
linkedin icon
Tired of fighting your Kubernetes platform?
Qovery provides a unified Kubernetes control plane for cluster provisioning, security, and deployments - giving you an enterprise-grade platform without the DIY overhead.
See it in action

Suggested articles

Kubernetes
 minutes
How to automate environment sleeping and stop paying for idle Kubernetes resources

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.

Mélanie Dallé
Senior Marketing Manager
Kubernetes
DevOps
6
 minutes
10 best Kubernetes management tools for enterprise fleets in 2026

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.

Mélanie Dallé
Senior Marketing Manager
DevOps
Kubernetes
Platform Engineering
6
 minutes
10 best Red Hat OpenShift alternatives to reduce licensing costs

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.

Morgan Perry
Co-founder
AI
Product
3
 minutes
Qovery Skill for AI Agents: Deploy Apps in One Prompt

Use Qovery from Claude Code, OpenCode, Codex, and 20+ AI Coding agents

Romaric Philogène
CEO & Co-founder
Kubernetes
 minutes
Stopping Kubernetes cloud waste: agentic automation for enterprise fleets

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.

Mélanie Dallé
Senior Marketing Manager
Platform Engineering
Kubernetes
DevOps
10
 minutes
What is Kubernetes? The reality of Day-2 enterprise fleet orchestration

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.

Morgan Perry
Co-founder
Kubernetes
DevOps
5
 minutes
Top 10 Rancher alternatives in 2026: beyond cluster management

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.

Morgan Perry
Co-founder
AI
Compliance
Healthtech
 minutes
Agentic AI infrastructure: moving beyond Copilots to autonomous operations

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

Mélanie Dallé
Senior Marketing Manager

It’s time to change
the way you manage K8s

Turn Kubernetes into your strategic advantage with Qovery, automating the heavy lifting while you stay in control.