All guides
OpenCode logo
OpenCode

OpenCode Hosting on a Real microVM

Run SST's OpenCode — the open-source, provider-agnostic terminal coding agent — on its own always-on Firecracker microVM. Any model, BYOK with no markup, a persistent home, real isolation. 124ms boot, 30-day money-back.

OpenCode crossed 100,000 GitHub stars and topped Hacker News because it does one thing the subscription CLIs won't: it talks to any model and never takes a cut of your tokens. Same Claude or GPT, no markup. The catch is the same as every terminal agent — it runs bash on whatever machine you put it on. Here's how to get the best of it without the risk: run OpenCode on its own always-on Firecracker microVM. Any provider you want, a persistent workspace, hardware isolation from your laptop — booting in about 124ms.

What OpenCode is

OpenCode is an open-source (MIT) coding agent for the terminal, from the team behind SST. It opens a rich TUI, connects to the provider you choose, and writes, debugs, refactors, and documents code from the command line. It's provider-agnostic by design — 75+ providers, including fully local models via Ollama — with LSP-powered, type-aware edits and parallel multi-session support.

The pitch is control: you own the model choice, you own the keys, and the core agent is free. The thing it needs is a place to run with a shell and your files — always on, holding your project.

Why a real microVM for OpenCode

A coding agent runs bash. It installs packages, edits files, and executes whatever the model decides — code no human reviewed. On your laptop that's your whole machine on the line. A shared container isn't the answer either: it shares the host kernel, with 200-plus known weaknesses in the stack.

jurniti gives OpenCode its own Firecracker microVM — its own kernel, a KVM hardware boundary, one tenant per box. The same isolation serverless platforms use. Give the agent root inside its own VM and a bad command — or a poisoned dependency, or a prompt-injection attack — stays contained to that box. Reprovision and you're clean in seconds.

BYOK is where OpenCode shines, and jurniti makes it architectural. If you already pay for Anthropic or OpenAI API credits, OpenCode with your own key is the cheapest way to a Claude- or GPT-powered terminal agent — no subscription, no markup. Run opencode auth login, point it at any provider, and the key lives only in your VM. Traffic leaves straight for the provider. jurniti is never in the path and never marks up a token.

OpenCode runs comfortably on Starter (1 vCPU / 2 GiB). And it's reversible: a 30-day money-back guarantee, workspace kept 7 days after cancellation.

Run OpenCode in 3 steps

By hand this is a VPS, the install script, provider config, a systemd unit, tmux so sessions survive a disconnect, and patching for as long as you run it. jurniti runs the box; you keep the agent.

1. Pick a plan and pay

Starter is enough for OpenCode. Check out, and the provision chain runs automatically the moment payment confirms.

2. Your microVM boots with OpenCode ready

A fresh Ubuntu microVM boots with OpenCode pre-installed and on your PATH. You get an in-browser terminal — nothing to SSH into. Configure a provider and go:

opencode auth login    # pick any provider, paste your key
opencode

3. Put it to work

Drop into a project, hand OpenCode a task, and walk away. Your config and custom agents live on the persistent home, so they survive every restart.

What people run OpenCode for

  • Model freedom. Swap between Claude, GPT, Gemini, Groq, or a local Ollama model without changing tools.
  • Cheapest Claude-in-the-terminal. BYOK against API credits you already have, no subscription on top.
  • Long, thorough runs. OpenCode trades a little speed for depth and real LSP diagnostics — let it grind on a box that's always on.
  • A pinned environment. Your config, your custom agents, your provider keys — set up once, always there.

Snapshot a dialed-in workspace into a template and fork it for the next project — your setup, never your credentials.

jurniti vs a laptop vs a DIY VPS

jurnitiYour laptopDIY VPS
Always onYesNo — it sleepsYes
Isolation for bashFirecracker microVM (KVM)Your whole machineShared kernel
Provider keysYours, never leave the VMYoursYours
Token markupNone (true BYOK)n/aNone
SetupAutomatic · 124ms bootLocal installManual
Refund30-day money-backn/aNone

Pricing

Starter is $25/mo ($250/year, two months free) and comfortably runs OpenCode. Pro is $49/mo and Max $99/mo for heavier workspaces or a custom TLS subdomain. Every plan includes the 30-day money-back guarantee, and your model spend is separate and never marked up.

Running a different agent? See the guides for Claude Code, OpenAI Codex CLI, and Goose, or compare plans on the pricing page.

Frequently asked questions

What is OpenCode?
OpenCode is an open-source (MIT), provider-agnostic coding agent for the terminal, built by the team behind SST. It opens a TUI, connects to the model provider of your choice, and writes, debugs, refactors, and documents code from the command line. It speaks to 75+ providers — Anthropic, OpenAI, Gemini, Bedrock, Groq, OpenRouter, and any local model via Ollama — so you're never locked to one vendor.
Can I run OpenCode on a server?
Yes. OpenCode is terminal-first, so an always-on box lets it keep working on long tasks and hold a persistent workspace. jurniti runs OpenCode on a dedicated Firecracker microVM with an in-browser terminal and a persistent home — hand it a task, close your laptop, come back to a finished diff.
Do I need my own API key?
Yes, and that's the point. OpenCode with BYOK is the cheapest path to a Claude- or GPT-powered terminal agent — same model, no subscription markup. Run `opencode auth login` to configure any provider. Your keys stay in your VM, traffic goes straight to the provider, and jurniti never marks up a token.
How much does it cost to host OpenCode?
Plans start at $25/mo ($250/year — two months free), and every plan has a 30-day money-back guarantee. OpenCode runs comfortably on Starter (1 vCPU / 2 GiB). Your model spend is separate and never marked up, because you bring your own key.
Will my config and custom agents survive a restart?
Yes. Your home directory is on a persistent volume, so your OpenCode config and custom agents survive restarts and reprovisions. You can also snapshot the whole setup into a forkable template — credentials are scrubbed on publish.
Is this an official OpenCode product?
No. jurniti is independent managed hosting for the open-source OpenCode agent. We install the upstream package at first boot — no fork — so you run the real OpenCode and pick your own provider and version.