self-host with runners
Your hardware. Our dashboard.
Install one runner on the server in your basement (or rack, or VPS) and it becomes a deploy target. You get the same push-to-deploy flow, logs, and rollbacks as Nubo Cloud, with none of the vendor lock-in.
One command. Your server is connected.
Run it on the machine you already have. The runner opens an outbound connection to Nubo and the box shows up in your dashboard as a deploy target.
Cloud convenience. Server control.
Self-host without writing a deploy pipeline from scratch. Nubo handles the workflow, your server handles the runtime.
- Anywhere with a shell · Home lab, $5 VPS, an old Mac mini, a Hetzner box. If it runs Linux, it can run a Nubo runner.
- Same dashboard, same deploys · Push code, watch the Frame come up, tail the logs. Identical workflow to our cloud.
- Pay for the hardware, not a markup · Already running a server? Bring it. Already paying for one? Use it. We don't take a cut of your VPS bill.
- Move when you want · Connect a cloud Frame today, swap it to your own runner tomorrow. Same code, different home.
Your hardware, same dashboard.
Drop one binary on a Linux or macOS box and deploy Frames straight to your own servers. Point your wildcard domain at it and get TLS through ACME. Cloud Frames and self-hosted Frames live in the same console.
- 01 Add a runner in settings and copy the token.
- 02
Run the one-line installer on your box.
$ curl -fsSL https://dl.withnubo.com/nubo-agent/install.sh | bash - 03 Pick the runner as the deploy target on any Frame.
- 04 Point your wildcard domain at it. TLS is handled through ACME.
runner live link · websocket
*.frames.example.com → your server
- · runner connected
- · task dispatched
- · logs streaming back
- · rolled out
nubo-agent
- · docker + caddy ready
- · pulling git repo
- · building image
- · serving traffic
stop reading
Go deploy something.
Free for 7 days, no card, no sales call. We will not pretend this page wasn't built to make you want to ship on a Sunday. It was.