# Paperclip Hosting on a Real microVM

> Run Paperclip — the open-source app for managing a team of AI agents at work — on its own always-on Firecracker microVM. Its own dashboard at your TLS subdomain, persistent org chart and budgets, real isolation. BYOK, 30-day money-back.

- Published: 2026-06-07 · Updated: 2026-06-07 · jurniti
- Canonical: https://www.jurniti.com/blog/paperclip-hosting

You opened twenty Claude Code terminals to move faster, and now you can't remember which one is fixing the bug and which one is halfway through deleting a table. That's the wall every multi-agent setup hits — most developers tap out at three to five sessions before the context-switching eats the gains. [Paperclip](/paperclip) is the answer the community reached for: an app that manages a *team* of agents like an org chart instead of a wall of tabs. It launched in March 2026 and crossed 35,000 GitHub stars in its first month. Here's how to run it the way it's meant to run — always on, on its own Firecracker microVM, with its dashboard at your own subdomain.

## What Paperclip is

Paperclip is an open-source app for managing AI agents at work. Under the task-manager surface it's a real orchestration engine: **org charts, budgets, governance, goal alignment, and agent coordination.** Its creator frames it simply — *if OpenClaw is an employee, Paperclip is the company.*

You define a goal ("ship the v2 launch"), assign a team of agents to it, set budgets, and watch the work from one dashboard. Paperclip drives **OpenClaw, Claude Code, Codex, Cursor, Bash scripts, and anything reachable over HTTP** — "if it can receive a heartbeat, it's hired." It's a Node.js server plus a React UI, and it ships with an embedded Postgres, so the whole thing runs as one long-lived service.

The point is to **manage business goals, not pull requests.** That only works if it's always on.

## Why a real microVM for Paperclip

Paperclip's whole job is to keep a fleet of agents running 24/7, each executing real commands and spending real money. You can't do that on a laptop you close — and you really don't want a swarm of autonomous agents sharing your personal machine, your SSH keys, and your browser sessions. A shared container isn't the boundary either: it shares the host kernel, with 200-plus known weaknesses in the stack.

**jurniti gives Paperclip its own Firecracker microVM** — its own kernel, a KVM hardware boundary, one tenant per box. The same isolation serverless platforms use. Paperclip and the agents it coordinates live inside that VM, always on, contained. A runaway agent stays inside the box, and you can rebuild it in seconds.

**Your dashboard gets a real home.** On Pro and up, the Paperclip web UI is auto-served at your own TLS subdomain — `https://<you>.jurniti.com` — so you can run your agent company from anywhere, including your phone. Your org chart, budgets, and history sit on a persistent workspace and survive every restart.

**BYOK is architectural.** Configure every provider inside the dashboard; the keys live only in your VM, traffic goes straight to each provider, and jurniti never sees a key or marks up a token. And it's reversible: a **30-day money-back guarantee**, workspace kept 7 days after cancellation.

## Run Paperclip in 3 steps

By hand this is a VPS, Node, the install, a database, a reverse proxy with TLS for the dashboard, a systemd unit, and patching for as long as you run it. jurniti runs the box; you run the company.

### 1. Pick a plan and pay

[Pro](/pricing) is the natural starting point — it serves the dashboard at your own subdomain. Check out, and the provision chain runs automatically the moment payment confirms.

### 2. Your microVM boots with Paperclip ready

A fresh Ubuntu microVM boots with Paperclip and its embedded database pre-installed, and the dashboard served at your TLS subdomain. Open it, add your providers, and start hiring agents — no SSH, no setup tax.

### 3. Build your team

Define a goal, assign agents, set budgets, hit go. Monitor everything from the dashboard while the team works around the clock.

## What people run Paperclip for

- **Taming the tab swarm.** Replace twenty unmanaged terminals with one org chart you can actually read.
- **Autonomous AI companies.** Point a team of agents at a business goal and let them run 24/7.
- **Cost control.** Set budgets and watch spend across every agent and provider from one place.
- **Run it from your phone.** The dashboard lives at your subdomain — check in and chime in from anywhere.

Snapshot a configured Paperclip org into a [template](/templates) and fork it to spin up a new agent company — your setup, never your credentials.

## jurniti vs a laptop vs a DIY VPS

| | jurniti | Your laptop | DIY VPS |
|---|---|---|---|
| Always on | Yes | No — it sleeps | Yes |
| Isolation for an agent fleet | Firecracker microVM (KVM) | Your whole machine | Shared kernel |
| Dashboard at your subdomain | Built in (Pro+) | n/a | You configure TLS |
| Provider keys | Yours, never leave the VM | Yours | Yours |
| Setup | Automatic · 124ms boot | Local install | Manual |
| Refund | 30-day money-back | n/a | None |

## Pricing

Because Paperclip is dashboard-first, **Pro ($49/mo, $490/year)** is the natural starting point — that's the plan that auto-serves the dashboard at your own TLS subdomain. Busy agent teams may want **Max ($99/mo, $990/year)**. Starter ($25/mo) runs Paperclip too, but the dashboard is far easier to reach on Pro's subdomain. Every plan includes the 30-day money-back guarantee, and your model spend is separate and never marked up.

Running the agents Paperclip coordinates? See the guides for [OpenClaw](/blog/openclaw-hosting), [Claude Code](/blog/claude-code-hosting), and [OpenAI Codex CLI](/blog/codex-cli-hosting), or compare plans on the [pricing page](/pricing).

## Frequently asked questions

### What is Paperclip?

Paperclip is an open-source app for managing a team of AI agents at work. It's a Node.js server and React dashboard that orchestrates many agents toward business goals — org charts, budgets, governance, and goal alignment. The line its creator uses: if OpenClaw is an employee, Paperclip is the company. It coordinates OpenClaw, Claude Code, Codex, Cursor, Bash scripts, and anything reachable over HTTP.

### Can I run Paperclip on a server?

Yes — and it's meant to. Paperclip is a long-running orchestrator with a web dashboard; it wants to be always on so your agents keep working while you sleep. jurniti runs Paperclip on a dedicated Firecracker microVM with its dashboard served at your own TLS subdomain and a persistent workspace, so your org chart, budgets, and history are always there.

### Do I need my own API keys for Paperclip?

Yes. jurniti is bring-your-own-key. You configure every model provider inside the Paperclip dashboard, and the keys live only in your VM. jurniti never sees your keys and never marks up token spend — you pay each provider directly.

### Why run Paperclip on a microVM instead of my laptop?

Because Paperclip coordinates many agents that each run real commands, 24/7. You can't do that on a laptop you close — and you don't want a fleet of autonomous agents loose on your personal machine. On jurniti, Paperclip and its agents live inside their own Firecracker microVM with its own kernel and a KVM boundary, always on and contained.

### How much does it cost to host Paperclip?

Plans start at $25/mo ($250/year — two months free), and every plan has a 30-day money-back guarantee. Because Paperclip serves a web dashboard at a custom TLS subdomain, the Pro plan ($49/mo) is the natural starting point; busy agent teams may want Max ($99/mo). Your model spend is separate and never marked up, because you bring your own key.

### Is this an official Paperclip product?

No. jurniti is independent managed hosting for the open-source Paperclip app. We install the upstream package and its embedded database at first boot — no fork — so you run the real Paperclip and connect your own agents and providers.