Platform

Your repo, running in a browser workspace.

A real terminal over WebSocket, a live preview pane for every service, and a git diff inspector, backed by a VM that boots from your repo's latest commit.

A real IDE, running against a real VM

Open a VM and you're already in it: a full terminal, a live preview of whatever's running, and a read-only view into what changed, all in one non-modal panel, no client install.

  • xterm.js terminal, tabbed, over WebSocket
  • Live preview iframe for every declared service
  • Git diff & file inspector, side by side with the terminal
TerminalPreviewChanges

$ git status

On branch hm-142-fix-auth

M src/routes/auth.ts

?? src/routes/auth.test.ts

$ pnpm test

✓ 12 passed

hm-142-fix-auth-3000.onhomemade.com

Agents ready on boot

No login prompt, no shared bot account. Every VM you create boots with Claude Code and Codex already signed in as you, using your own subscription, and every MCP server you've connected already wired in.

  • Claude Code & Codex CLI signed in with your own subscription
  • Your personal MCP server catalog injected at boot
  • AI traffic goes straight from the VM to the provider: we never proxy or see your prompts
agent boot
✓ claude code — signed in as you✓ codex cli — signed in as you✓ mcp servers — linear, github, 1 customagent runs as the VM's creatorsignals attention_required when it needs you

Every PR and every ticket, a live URL

Reviewers click a live link, not a diff. Ticket VMs give an agent (or you) a running environment the moment a Linear issue is ready to work.

  • pull_request webhook creates and tears down preview VMs automatically
  • Preview URLs commented back on the PR
  • A Linear trigger label boots a VM on the issue's branch

PR #142 opened → main

✓ preview VM created

↳ pr-142.onhomemade.com commented on the PR

HM-142 · trigger label added

✓ vm running on hm-142-fix-auth

↳ commented back on the issue

Shared projects, shared context

Projects, env vars, and members live at the org level. Invite your team and everyone works against the same configuration, not their own copy of it.

  • Shared projects and environment variables per org
  • Member roles, invites gated by your plan's seat count
  • One workspace, the same VMs, for the whole team
acme / storefront: members

Built to be trusted

The decisions that make a disposable VM safe to hand real work to.

A real machine, not a container
Every workspace is a hardware-isolated Firecracker microVM with its own kernel and its own network, not a shared container.
Boots in about a second
Median ~1 second from click to running VM, snapshot restore. Coder's own prebuilds benchmark lands around 30 seconds.
Hibernation, not deletion
Step away and your VM hibernates instead of disappearing. It comes back exactly as you left it when you wake it.

Get started

Your next VM is one command away.

Connect a repo, and get a full-stack dev environment with Claude Code and Codex already running, before your coffee's done.