Experience Qovery on Your Local Machine
Requirements
- Supported Operating Systems: Linux, macOS, and Windows.
- Resources: 4 CPU and 8GB of RAM for your Docker runtime
- Binaries: docker, jq, curl, sed, grep, git
- A stable Internet connection.
- A Qovery organization. If you don't have one, please sign up on our platform here.
Purpose and Limitations
It's important to note that this local setup of Qovery using the qovery demo up command is designed for demonstration and testing purposes only. It is not intended for production use. Please refer to the official installation guide for deploying Qovery in a production environment.
Installation Steps
The setup process is quick and takes less than 5 minutes. Here are the steps:
1/ Install the Qovery CLI (check out our documentation for more details on installation options)
2/ Authenticate via Qovery
3/ Install Qovery locally (this operation should take between 1 to 5 minutes)
Ensure you have Docker running and that you have installed jq, curl, sed, grep, and git.
Note that if you are on MacOS or Windows, you might be prompted for your admin password - which is necessary to properly route the traffic from your host to your k3s apps.
At the end of execution, you should see something like:
5/ You can connect to the Qovery web console and deploy your apps on your local cluster 🥳
Watch the full demo here:
Here are the different chapters:
- 00:00 - Introduction
- 01:25 - Install Qovery on my Local Machine
- 03:58 - Deploy my apps on my local machine with Qovery
- 08:40 - Clone my environment
- 12:07 - Delete my apps
For a more detailed explanation of how Qovery works, consider reading this informative blog post.
Running Qovery Anywhere
The Flexibility of Qovery CLI
One remarkable feature of Qovery is its flexibility. For instance, you can execute the "qovery demo run" command remotely via SSH on any machine, even those without a graphical user interface (GUI).
Authentication for Non-GUI Access
To use Qovery's CLI remotely, you first need to authenticate securely. The command "qovery auth --headless" is particularly useful for setups when accessing remote servers.
Practical Example
Let's consider running Qovery on a CIVO cloud instance. Once authenticated, you can deploy applications or manage your Qovery environment directly from the command line, showcasing the adaptability of Qovery for various development and operational scenarios.
Conclusion
Qovery is designed to offer a high-quality developer experience, allowing developers to focus more on coding and less on the operational overhead. By leveraging Qovery, both on local machines for testing and on remote servers for production deployments, developers can enhance their productivity and streamline their development workflows. For further details or to begin your journey with Qovery, visit our documentation.
.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)