Unlimited building.

Nothing has to stay on. Nothing has to be yours.

You don't need a machine that stays awake. Close the laptop, let the battery die, get on a plane. Your agents keep running on the devbox, and the next device you pick up shows you the same session.

You don't need a machine that belongs to you either. There is nothing to install and no key to copy, so signing in on a computer you borrowed leaves nothing on it when you sign out.

Run it on localhost. Open it anywhere.

Start your app like you normally would.

npm run dev

If it runs on localhost:3000, vcloud gives it a URL:

3000--josh.vcloud.tech

Give it a name:

app--josh.vcloud.tech

Open it from another device or share it with someone else. You don't need to deploy just to see what you're working on.

Work from the terminal.

vcloud is built for terminal-first development.

Run the coding tools you already use:

claude
codex
opencode
gemini
aider

Your agents run on the devbox, not your laptop. Close the browser, switch devices, come back later. The machine and your sessions are still there.

Sign in to an agent once, ever. vcloud notices the login and carries it: your next devbox comes up with Claude Code, Codex, opencode and Gemini already signed in. No re-authenticating on every machine.

Need an editor? Real VS Code runs in the browser at vs--josh.vcloud.tech - nothing to install, works from a phone. And tode . opens terminal-code right inside the terminal, no Remote SSH.

Terminal when you want it. VS Code when you need it.

Your agent knows where it lives.

Every devbox carries instructions your agent reads on its own, and a CLI built for it. So instead of telling you “it's running on localhost:3000”, an agent here does this:

vcloud url 3000          ->  https://3000--josh.vcloud.tech
vcloud access 3000 public    anyone can open it (or: team, link, private)
vcloud rename 3000 app   ->  https://app--josh.vcloud.tech
vcloud team                  who a team-share reaches

“Here's the URL to try it” - from the agent, unprompted, and the link works on your phone. The boundary is built in too: agents can publish and share what they run, but stopping or deleting a machine is yours alone, on the dashboard. The CLI simply doesn't have those commands.

Rent a bigger computer for one command.

Your devbox never resizes under you - the work scales instead.

vcloud burst run --cpu 32 --ttl 1h -- make -j32

Your working directory ships to a temporary 32-CPU worker, the command runs there, the log streams into your terminal, the results land back on your box - and the worker destroys itself, at the finish or at its time limit, whichever comes first.

Agents use it too, inside a budget you set: a daily cap, a biggest-worker size, a longest life. Off until you turn it on. Nothing you are running is ever touched - the only thing at stake is the budget, and the budget is yours.

Your agent can see what it built.

terminal-browser is a real browser that runs in the terminal, so the page you are building sits next to the agent building it.

terminal-browser open localhost:3000
terminal-browser --split right
terminal-browser action

That last one is the agent-facing side: Claude Code or Codex can drive an open browser from the same command line, click through a checkout, and read back what happened.

It renders in the vcloud terminal too, on your laptop or your phone, so you can watch a page load on a machine you are nowhere near.

Your machine has an address.

josh.vcloud.tech/              your terminal
josh.vcloud.tech/box/worker2   another box's terminal
vs--josh.vcloud.tech           VS Code
oc--josh.vcloud.tech           opencode's web interface
app--josh.vcloud.tech          what you're building

One origin that is yours. The terminal and the editor open only for you - signing in is your email and a code, on any device. No SSH keys to copy between machines, no client to install, no remembering which laptop has the right config.

If you do want SSH, you can still use it.

Every port gets a URL.

vcloud watches the ports running on your devbox and makes them available over HTTPS.

localhost:3000  ->  3000--josh.vcloud.tech
localhost:8000  ->  8000--josh.vcloud.tech
localhost:5173  ->  5173--josh.vcloud.tech

You can rename them.

3000  ->  app--josh.vcloud.tech
8000  ->  api--josh.vcloud.tech
5173  ->  docs--josh.vcloud.tech

No tunnels to start. No proxy config to write.

Every service gets its own origin under vcloud.tech - root path, its own cookies - and nobody else's machine shares it.

Keep it private or send the link.

Each service has its own access setting.

A real Linux machine.

This isn't a browser sandbox.

Install packages. Run Docker. Start databases. Use tmux. Run agents. Leave processes running.

apt install ...
docker compose up
pnpm dev
python server.py
claude
codex

Your filesystem persists between sessions.

The small things that make it feel like a computer.

Paste images straight into the terminal. vcloud uploads what is on your clipboard and types the path back at the prompt.

Ctrl+V  ->  /home/dev/.vcloud/uploads/screenshot-2026-08-20.png

claude "fix this" /home/dev/.vcloud/uploads/screenshot-2026-08-20.png

Screenshot a bug on your phone, paste it, hand the file to an agent. No scp, no AirDrop, no file picker.

Drag a file from your desktop into the terminal and it lands in your working directory. Select text and it copies. Paths and URLs in your output are clickable, and a localhost URL an agent prints becomes the real one.

vcloud share ./output.png --expires 24h
vcloud download ./build.zip
vcloud qr app

On a phone you get a modifier bar above the keyboard: Esc, Tab, Ctrl, arrows, paste and upload.

And the disk takes care of itself: opt into daily snapshots and vcloud keeps a week of them, so yesterday's filesystem is a restore away.

Work from more than one device.

Start something on your laptop. Check it from your phone. Open the same terminal from your desktop later.

Your code and processes stay on the devbox. The device in front of you is just how you connect to it. If your battery dies, nothing on the devbox stops. If you switch computers, your environment doesn't change.

For teams

Give everyone a devbox without asking them to configure a machine first. Team members sign in with email and get access to the machines and services you've shared with them. You can share an app without sharing shell access.

org-1

  josh     Standard   4 CPU · 16 GB
  alice    Small      2 CPU · 4 GB
  maya     Large      8 CPU · 32 GB

what alice can reach

  app--josh.vcloud.tech        open
  josh's terminal             no access
  josh's filesystem           no access

One price. No surprises.

The computer is $500 a month, flat - 8 CPU, 32 GB RAM, 1 TB disk, always-on, daily snapshots. Credits on top pay for what varies: the models your agent thinks with and the bigger machines it occasionally rents for heavy jobs. Prepaid, so the most you can spend is what you loaded - with optional auto top-up when you would rather never think about it.

Your first day is free, no card. If the subscription ever lapses, your machine pauses - nothing is deleted - and resubscribing brings it back exactly as it was.

The basic idea

One machine. Open it from anywhere.

Stop setting up the same computer twice.

One computer, one price: $500/mo - 8 CPU, 32 GB, 1 TB, always-on, snapshots. Your first day is free, no card.