detachbox

Open what the agent built on any screen

Every server the agent starts already has its own HTTPS link. Check the layout on your phone, send a client the demo, hand over a report by link. Until you make the port public, only you can open it. From $39 a month.

From $39 a month · Docker and sudo included · Cancel from the dashboard any time

Files and previews of one terminal on shipyard. Ports 3000 and 8080 have their own HTTPS addresses on detachbox.dev, port 3000 public. A coverage report is shared by link, opened 3 times, with Revoke.

How it plays out

The previews of one terminal: ports 3000 and 8080 at their own HTTPS addresses with the process behind each, port 3000 public, and a coverage report shared by link.

Every dev server, one link away

  • Skip the tunnel

    Bind the dev server to 0.0.0.0 and its address already works, HTTPS included.

  • Private until you say so

    Only you, signed in, can open a preview. Make a single port public when a client or a friend needs the link.

  • Hot reload across the internet

    Websockets, server-sent events and streaming pass straight through. Vite, Next.js, Rails and Django need no host config.

  • The mobile layout on a real phone

    Open the same URL on your phone and check the layout with your thumb.

The details

Address
https://<port>-<terminal-id>.detachbox.dev
Ports
1024 to 65535, anything listening on 0.0.0.0
Access
Owner only by default; up to 20 public ports
Passes through
Websockets, hot reload, server-sent events, streaming; uploads up to 100 MB
Search engines
Every preview answers with noindex
Files
https://files-<terminal-id>.detachbox.dev

Questions about this

Why a separate domain?

Previews run your code, so they live on detachbox.dev, apart from detachbox.com, and dashboard cookies never reach them. Private previews also refuse cross-site requests and framing, and the files host never serves .env, .git or .detachbox.

Why does the preview say nothing is listening?

Bind the server to 0.0.0.0 instead of localhost: npm run dev -- --host 0.0.0.0, next dev -H 0.0.0.0 or rails s -b 0.0.0.0.

What happens to a public port when its terminal ends?

It closes with the terminal. Previews and shared file links belong to the terminal that served them and stop answering the moment it ends.

Open what the agent built on any screen

Pick a size, hand the agent the job and close the tab. Come back to finished work.

Get my Compute

Your first overnight run works, or your money back · Cancel from the dashboard; it runs to the end of the paid month