JURNITI°docs

Quickstart

First jurniti agent in about five minutes — from the web dashboard or the CLI. Log in, put a card on file, provision, connect.

Your first agent

Budget about five minutes. Provisioning itself is ~3 minutes after payment clears.

Pick Dashboard or CLI. Same account. Same microVM. Same bill.

Path A — Dashboard (browser)

Best if you want a live terminal and agent UI without installing anything.

Create your account

Open app.jurniti.com/login. Enter your email and click the magic link in your inbox. No password to invent or reset.

After login you land on Agents (/dashboard/vms).

Add a card (at checkout)

Click Add agent. Pick a harness and a plan (Starter / Pro / Max, monthly or annual). Stripe Checkout collects the card — fields are Stripe's, not jurniti's. After payment, the platform auto-provisions the VM.

Wait for running

The new agent appears on Agents. Status moves to running when the microVM is up (typically ~3 minutes). You never SSH into a host.

Connect

Open the agent. Use the browser terminal, or open the harness portal when one is available.

Full walkthrough: Dashboard.

Path B — CLI (terminal)

Best if you live in a shell, CI, or you want the same verbs as MCP tools later.

Install and log in

curl -fsSL https://jurniti.com/install.sh | sh   # macOS / Linux
jurniti login

Windows: see Installation.

jurniti login prints a device code and opens a browser to confirm. After that, jurniti whoami, jurniti vms ls, and jurniti usage work immediately — you only need a card to provision.

Add a card

jurniti billing add-card

Card entry is web-only

jurniti billing add-card opens your browser. You type the card into Stripe Elements — never into the terminal. The CLI and jurniti's servers never see the number. When the browser flow finishes, return to the terminal.

Check it landed:

jurniti billing status

Bring a VM up

jurniti up --harness hermes --plan pro --cycle monthly

Not sure which harness? jurniti harnesses lists them and each one's auth requirement.

Connect

jurniti vms ls           # find your new VM
jurniti vms get <id>     # state, subdomain, readiness
jurniti usage            # live VM counts + monthly spend

Each Pro/Max VM gets its own TLS subdomain. Open it in a browser, or drop straight into a terminal without leaving your shell:

jurniti shell <id>    # interactive terminal inside your agent

Press Ctrl-] to leave — the agent keeps running.

Sign the agent in

A booted box still needs credentials before it can answer anything. jurniti auth <id> tells you which of the two it takes.

Bring your own API key — written straight into the box:

jurniti auth <id> --set OPENROUTER_API_KEY=sk-...

Use a subscription you already pay for (e.g. Claude Code) — sign in interactively. This opens a terminal on the VM, runs the agent's own login command, and opens the URL in your local browser; you paste the code back:

jurniti auth <id> --login

Your subscription credential never leaves the VM

The sign-in happens inside your agent — it mints and stores its own credential there. jurniti relays keystrokes and keeps nothing: no token is written to your laptop, and none is stored on our side.

Already been running this agent locally? One command moves your sessions, memory, and config into the VM — credentials are scrubbed before anything leaves your machine:

jurniti transfer --vm <id>

--dry-run previews the manifest first. What travels, per agent: Claude Code · OpenClaw. Full flags: CLI reference.

The money gate (both paths)

No free tier — a card is required to provision

There is no free trial and no free tier. A VM is a real Firecracker microVM on paid capacity. What de-risks the first buy is the 30-day money-back guarantee on your first subscription: cancel within 30 days for a full refund, no questions asked.

Same card gate as up. List public templates, inspect one, then fork:

jurniti templates ls --q founder
jurniti templates get <tpl-id-or-slug>
jurniti fork <tpl-id-or-slug>            # charges; no free fork
jurniti wait <vm-id> --ready

Full command detail: CLI reference. Agent path: MCP (templates_list → template_get → template_fork → vm_get).

What next?

Dashboard

Day-to-day browser ops — terminal, plan, credits, templates.

Templates gallery

Browse public agent templates and fork from the web.

Usage tiers

Hourly prepaid On-Demand or Spot instead of a flat plan.

Token usage

See estimated BYOK model spend — dashboard, CLI, or MCP.

Swarm

Many agents at once on Spot (CLI-first today).

MCP

Hand the same verbs to your own coding agent.

Introduction

jurniti runs your agent in a real Firecracker microVM with your own model keys. Drive it from the web dashboard, the CLI, or your own agent over MCP.

Dashboard

Run jurniti from the browser — magic-link login, Add agent, live terminal, templates, plan & billing. No CLI required.

On this page

Your first agentPath A — Dashboard (browser)Create your accountAdd a card (at checkout)Wait for runningConnectPath B — CLI (terminal)Install and log inAdd a cardBring a VM upConnectSign the agent inThe money gate (both paths)Fork a gallery template instead of a blank box (CLI)What next?