Reach a port. No public URL.

See the app or API your agent started inside a sandbox, from your own machine, through a tunnel that only you can open.

Sandboxes › Authenticated tunnels

Authenticated tunnels

See the app or API your agent started inside a sandbox, from your own machine, through a tunnel that only you can open.

Terminalsbx_9a20
01$ sandscale tunnel sbx_9a20 3000
02localhost:3000 → sbx_9a20:3000
03authenticated tunnel · no public URL
04open http://localhost:3000 in your browser
Exposure
No public URLs, ever
Who
Only the signed-in person who opened it
Network
Outbound network stays off unless your allowlist opens it
Audit
Opening and closing a tunnel is recorded

How it works

Three steps, the same from the API, the CLI or your agent over MCP.

01Start it

Name the sandbox and the port your agent’s app listens on.

02Sign in

The tunnel is opened as you, with your Sandscale sign-in.

03Use it

The port appears on your own machine; nothing is exposed to the internet.

Which plans

Tunnels work on every plan.

See pricing →

Give every agent
a box of its own

Start free with 100 vCPU-hours a month. Upgrade when your agents need more.

A Firecracker microVM for every runNo network by defaultPause and resume with state keptVault keeps secrets out of promptsSSO, roles and audit logBring your own cloudWorks over MCP and the CLI