Amp Hosting on a Real microVM

Amp is the kind of tool you want always on — not killed when your laptop sleeps. Host Amp on a Firecracker microVM: your Amp login stays in the box, the agent keeps working, and a bad shell command can’t take down the rest of your life.

What Amp is

Amp is Sourcegraph’s frontier coding agent for the terminal and editor. Smaller mindshare than Claude Code today, but respected in serious engineering orgs. Install the CLI, sign in with your Amp account, and work against the agent from a shell.

It’s happiest on a box that’s always on: hand it a refactor, a failing suite, or a multi-file cleanup and let it grind while your laptop is elsewhere.

Why a real microVM for Amp

A coding agent runs bash. It installs packages, edits files, and executes model-chosen commands. On your laptop, that has the run of your home directory, SSH keys, and browser sessions. Containers share the host kernel. jurniti gives Amp its own Firecracker microVM — own kernel, KVM hardware boundary, one tenant per box. Hand it root there; a runaway stays contained. Something goes sideways? Reprovision in seconds.

You keep your model / product relationship. jurniti’s BYOK is architectural: credentials live only in your VM, traffic goes straight to the vendor, and we never sit as a token proxy.

Most CLI agent work runs on Starter (1 vCPU / 2 GiB). Every plan has a 30-day money-back guarantee on first purchase; workspace kept 7 days after cancellation.

Run Amp in 3 steps

1. Pick a plan and pay

Starter is enough for most Amp work. Checkout runs the auto-provision chain — no manual SSH to stand the box up.

2. Your microVM boots with Amp ready

A fresh Ubuntu microVM boots with the CLI pre-installed and on your PATH. Open the in-browser terminal:

run `amp` and complete Amp account login

3. Put it to work

Point it at a repo, hand it a task, close your laptop. Config on the persistent home survives restarts. Snapshot into a template when you want to fork the setup without leaking credentials.

Give Amp its own microVM

What people run Amp for

Always-on sessions. Long refactors and test loops that outlast a commute.
Isolation for autonomy. Give the agent a real shell without risking your primary machine.
A pinned environment. Tools and project state set up once, always there.
Parallel agents. Multiple microVMs instead of a tangle of local tabs.

Pricing and guarantee

Plans from $25/mo (annual available). First-purchase 30-day money-back. Model / product subscription is yours — no token markup. See pricing and the product page for Amp.

Frequently asked questions

Can I run Amp on a server?

Yes. Amp is a terminal coding agent — it needs a shell and your files more than a GPU. jurniti gives it a dedicated Firecracker microVM with an in-browser terminal, a persistent home, and isolation from your laptop so long jobs survive when you close the lid.

Do I need my own API key or subscription?

Yes. Sign in with your Amp account inside the VM. jurniti is BYOK/BYO-subscription — we don’t resell Amp seats or sit in the model path.

Why a microVM instead of Docker or my laptop?

Coding agents run real shell commands. On your laptop, a bad `rm` or a prompt injection has the run of your home directory. Shared containers share a kernel. jurniti gives Amp its own Firecracker microVM — own kernel, KVM boundary, one tenant per box.

How much does it cost to host Amp?

Plans start at $25/mo ($250/year — two months free), with a 30-day money-back guarantee on first purchase. Starter (1 vCPU / 2 GiB) is enough for most CLI agent work. Model spend is separate and never marked up.

Will my config survive a restart?

Yes. Your home directory is on a persistent volume, so settings, rules, and project state survive restarts and reprovisions. You can snapshot into a forkable template — credentials are scrubbed on public publish.

Is this an official Amp product?

No. jurniti is independent managed hosting for the Amp CLI. We install from Amp’s official install path; Amp remains your vendor for the product subscription.