Preview environments
Every VM is a preview: an HTTPS link for each port, shared with whoever you choose.
On homemade every VM is a preview environment: each service that listens on a port gets its own HTTPS link, so a branch, a pull request or an agent's work can be opened in a browser and shared. You choose who can open each link (anyone, your team or only you), dev servers work without host settings, and a sleeping VM can wake when someone opens its link.
The facts
What every VM comes with.
| Fact | Details |
|---|---|
| Links | One HTTPS link per service port, per VM. Vite, Next.js, Django and Rails host checks pass without setup. |
| Sharing | Per service: anyone with the link, members of your team, or only the VM's owner. |
| Wake on visit | Optional per project: opening a sleeping VM's link wakes it. |
| Machine | A Linux VM with its own kernel and disk. Sizes from 0.5 vCPU / 1 GB up to 16 vCPU / 32 GB. |
| Agents | Claude Code, Codex, OpenCode, pi, Kimi and Grok installed. Sign in once and every new VM starts signed in. |
| Sleep | Sleeps when idle and wakes where you left it, files and terminals included. |
| Access | Browser terminal (phone too), SSH, VS Code, Cursor, the CLI, an MCP server and an HTTP API. |
| Price | Hobby is free: 25 VM-hours a month, 1 VM at a time, nano or tiny. Pro is $20/mo with $20 of usage included, then from $0.012 an hour (nano) to $0.18 (large) by size. Sleeping VMs don't use hours. |
How to start
Name the ports
Mark the services that should get a link in .homemade/config.
Terminal"services": { "web": { "cmd": "pnpm dev", "port": 3000, "url": true }}Start a VM per task
Connect a GitHub repo (or start from a template). Each VM starts with the repo cloned at the branch you pick, your install commands run and your services started.
Terminalhomemade vm create --branch fix-auth --waitShare the link
Open the link from the VM's page or the API's urls field, and send it to whoever should see it.
When something else fits better
homemade isn't the right tool for everything.
Production builds per pull request
If you want a production build deployed for every pull request on your hosting provider, your host's preview deployments (Vercel, Netlify and others) do exactly that.
Questions
What is a preview environment?
A preview environment is a running copy of your app for one branch or change, on its own URL, so people can try it before it's merged.
Does my app need a production build?
No. The preview link passes each request to your app as if it came to localhost, so dev servers run as they do on your laptop, live reload included.
Can I keep a preview private?
Yes. Each service has a sharing level: public, organization (your team, after signing in) or owner only. You can change it for a single port on the VM page.
Can previews use my own domain?
On Pro, the Custom domains add-on serves your VMs on your own domains, with a certificate for each.
Read on
Try it on the free plan
Hobby is free. Connect a repo and your first VM starts from it.