Your machine & desktop

Your machine

When you sign in, you get one Linux computer in the cloud. It's yours. It persists, it stays on, and it comes fully loaded.

The plan

There is one plan.

Wrkr — $199/month

  • 4 dedicated CPU cores — yours, not shared out from under you
  • 16 GB RAM
  • 200 GB disk
  • Streamed desktop — a real Linux GUI, live to your Mac or browser
  • The harness stack inside — your AI coding agent and the full toolkit
  • Always-on serving — your app keeps running 24/7
  • Hourly offsite backups of your work

One plan, one price — no tiers to compare, no per-seat math. Wrkr is prepaid.

What "your VM" means

Your machine is a persistent virtual machine — a real computer, not a session and not a container that resets.

  • Always-on. It doesn't sleep when you disconnect. Close the browser, shut your laptop, come back tomorrow — your machine and everything running on it are still there.
  • Persistent. Files stay where you left them. Your projects, your shell history, your installed packages, your running services — all still there across reboots and across days.
  • Yours alone. One machine per person. The 4 cores are dedicated to you. It is not a shared box you're renting a slice of by the minute.
  • A real Linux machine. You have full admin control. Install packages, run services, configure it however you like. It's your computer.

What's already installed

You don't start from an empty box. The machine ships as a complete AI coding workstation:

Desktop & browser : A real desktop — a file browser, a terminal, a text editor, the apps you'd expect — plus Chrome (for real browsing and browser automation) and Firefox.

AI coding harnesses : Claude Code, Codex, Gemini CLI, and OpenCode — your choice. You log in with your own account for whichever you use.

App primitives (the things you'd otherwise rent) : Postgres 18 + pgvector, Redis, object storage, transactional email, public HTTPS ingress, and scheduled jobs — each one command away via the wrkr CLI.

Runtimes : Node.js, Bun, Python (with uv), and Go.

Developer toolkit : git, gh, ffmpeg, ImageMagick, and the usual command-line tools your agent reaches for.

This is a curated baseline, not a bloated one. The rule is simple: ship the irreducible primitives an app needs, and let your AI write everything else natively. Heavier or niche tools (local model serving, big-data stacks) you install yourself when you want them — it's your machine.

For the full curation philosophy, see The wrkr CLI and Working with your AI.

Always-on serving

Because your machine never sleeps, anything you run keeps running. A web server, a worker, a scheduled job, a bot — start it and it stays up, serving real traffic, whether or not you're connected.

This is the difference from a laptop (which sleeps when you close it) and from an ephemeral cloud sandbox (which is wiped when your session ends). Your machine is a server you can also see.

Put an app online with wrkr expose; to keep a process running after a crash or reboot, just ask your agent to set it up. See Your apps in production.

Backups & durability

Your work is backed up offsite, every hour — automatically, encrypted, with no setup. If your machine is ever rebuilt, your home directory comes back.

  • Your dev work (code, home directory, local databases under ~) is covered by the hourly offsite backup. Included in the plan.
  • Your app's database can be snapshotted and restored on demand with wrkr db snapshot / wrkr db restore.
  • Your app's stored files in wrkr storage are held in durable object storage that survives a machine rebuild.

The full picture — what's covered, how restore works, and what stays your responsibility — is on the Backups & restore page, and the durability promise is in Trust.

What still lives outside your machine

Wrkr replaces the rented middle of your stack, not the genuinely-irreducible edges. You'll still bring:

  • Your AI harness account and model API keys — Wrkr never custodies these.
  • A domain, if you want your app on your own name — buy it from any registrar; wrkr expose --domain serves it.
  • Payments, source hosting, and any regulated integrations — Stripe, GitHub, an SMS provider, and the like stay external because they should.

Everything in between — database, cache, storage, email, hosting, jobs — your machine and your agent handle.