Try Qovery on Your Laptop: Ask Your Coding Agent, Get a Running App

Key Points:

• Your coding agent can now try Qovery for you on your laptop. When your Qovery organization has no cluster, the Qovery agent skills offer to create one locally with qovery demo up, then build and deploy your project to it.
• One prompt does it: "Deploy https://github.com/traefik/whoami with Qovery on a local cluster on this machine." You sign in, pick your organization and, on macOS, type your password once.
• Measured on an Apple M3 Ultra with Claude Code: 4 min 43 s to create the local cluster, then 2 min 40 s for the agent to build the repository from GitHub and deploy it. The app answered HTTP 200.
• No cloud account and no credit card. You need Docker, a free Qovery account and a coding agent that supports Agent Skills.
• The same project goes to production unchanged when you create a cluster in your own AWS, GCP, Azure or Scaleway account.

Until today, trying Qovery meant connecting a cloud account or a Kubernetes cluster before you could deploy anything. That is a lot to ask of someone who only wants to see whether Qovery fits: cloud credentials or a running cluster, and about 30 minutes for a new cluster to come up, before the first deployment.

We already had a way around it: qovery demo up, a CLI command that creates a k3s cluster in Docker on your machine and connects it to your Qovery organization. But you had to know it existed, install its dependencies and run a handful of commands in the right order.

Now your coding agent does that for you.

What changed

The Qovery agent skills (qovery-deploy, qovery-onboard and qovery-signup) check your organization for clusters before they deploy. If there is none, and you did not say the deployment is for production, the agent offers two paths:

1. Try it now on this machine: a local cluster in Docker, free, for testing only. About 5 to 10 minutes.
2. Use your cloud or your own Kubernetes cluster: AWS, GCP, Azure, Scaleway, or a cluster you already run.

If you pick the first one, the agent checks Docker, k3d, helm, kubectl and your Qovery CLI version, tells you what is missing in one message, and runs qovery demo up. When the cluster is ready, it creates a project and an environment, adds your repository, builds it on the cluster and gives you the URL.

How to try it

Install the skills once:

curl -fsSL https://skill.qovery.com/install.sh | bash

Then open Claude Code, Cursor, OpenCode, Gemini CLI or another agent that supports Agent Skills, and paste:

Deploy https://github.com/traefik/whoami with Qovery on a local cluster on this machine.

traefik/whoami is a small public web server, a good first run. Swap the URL for any repository with a Dockerfile, or open the agent in your own project and say "Deploy my application with Qovery".

The agent hands a few steps to you, because they open a browser or need your password:

What we measured

We ran it from scratch with a fresh Claude Code session that had nothing but the Qovery skills installed, on an Apple M3 Ultra, Qovery CLI 1.181.1, on 9 November 2026:

The build runs on the local cluster itself. Your times will depend on your machine, your network and the project.

The runs were not perfect, and we fixed what we saw. In the first runs the agent passed a file path where the CLI expects stdin, tried the latest image tag that the API rejects, and read runtime logs when it wanted build logs. It recovered each time, and the skills now say all three things up front.

Why start on a laptop

A local cluster answers the first question a developer has, "does my app run on this?", in about ten minutes and without asking anyone for cloud access. It is the same Qovery: the cluster shows up in the Console next to any other, with its environments, deployment logs and variables. What you learn there, you keep when you move to production.

When you are ready, create a cluster in your own cloud account, or connect one you already run, and deploy the same project to it. Your agent can do that too: "Deploy this to production on AWS with Qovery".

What it is not

The local cluster runs only on your machine and is not for production. Apps you deploy there are reachable from your machine only.

On the Free plan, the local cluster counts as your one included cluster. To connect a cloud cluster later, remove the local one with qovery demo destroy --delete-qovery-config, or move to a paid plan to keep both.

The local cluster needs Docker with at least 4 CPUs and 8 GB of memory, on macOS, Linux or Windows with WSL.

Get started

The step-by-step guide is in the docs: Try Qovery on your laptop with a coding agent. If you prefer to run the commands yourself, without an agent, see Test & Learn Locally.