Who offers it

Part of Reaching it: links, ports and who can open them, which explains why it matters.

Fully: Agent 37, Boat, boxd, Daytona, InstaBox, Morph, Sandboxer and Tensorlake. With a catch: Cloudflare Sandbox, E2B, Lizard, Modal, Runtime, Sprites and Vercel Sandbox. Not at all: Blaxel.

  • Agent 37YesOver one connection

    A standard ssh client works, but the connection is carried over the provider's web channel rather than a dialable port.

    docs-confirmed “`ProxyCommand` is what carries the SSH stream (there is no port to dial directly)” Source

  • BoatYesPort 22

    A standard ssh client connects to the machine on port 22 with your key.

    docs-confirmed “Run `boat ssh <id>` for a shell.” Source

  • boxdYesReal SSH

    File copy and editor remote access work too, because it is a real SSH server.

    docs-confirmed “It is real SSH” Source

  • DaytonaYesToken, 60 min

    You connect with a standard client using a short-lived token.

    docs-confirmed “SSH access tokens expire automatically after 60 minutes.” Source

  • InstaBoxYesGateway, short cert

    A standard ssh client connects through the provider's gateway with a short-lived certificate.

    docs-confirmed “The instabox gateway terminates SSH: `ssh -p <port> <machine-id>@<host>`, with a short-lived user certificate” Source

  • MorphYesBuilt in

    A standard SSH client connects to the devbox directly.

    docs-confirmed “through SSH, or puppeteered through the Devbox API” Source

  • SandboxerYessshEndpoint

    A standard ssh client connects to the machine's own SSH address.

    docs-confirmed “Through the tunnel with plain ssh” Source

  • TensorlakeYesStandard ssh

    A standard client works, including file copy, editors and port forwarding.

    docs-confirmed “Reach a running sandbox over standard SSH, or open a programmatic PTY session over WebSocket” Source

  • Cloudflare SandboxWith a catchOne provider tool

    The catch: You cannot point a normal SSH client at the machine; the only way in is a Cloudflare command-line tool.

    docs-confirmed “SSH does not expose a publicly accessible port on the Container.” Source

  • E2BWith a catchYou build the image

    The catch: SSH only works if you build a custom image with an SSH server and a relay inside it.

    docs-confirmed “Connect to your sandbox via SSH using a WebSocket proxy” Source

  • LizardWith a catchOwn client only

    The catch: Its shell command works, but it is the provider's own client rather than a standard SSH connection, so ordinary SSH tools cannot connect.

    docs-confirmed “lizard sandbox ssh” Source

  • RuntimeWith a catchThrough the CLI

    The catch: The connection goes through the provider's own command rather than a plain SSH address.

    docs-confirmed “All of it goes through Runtime's API, authenticated with your key, over one WebSocket per connection.” Source

  • SpritesWith a catchInstall a server

    The catch: You must install an SSH server inside the machine and reach it through the provider's proxy.

    docs-confirmed “Sprites don't expose SSH directly—you'll need to install an SSH server on your” Source

  • Vercel SandboxWith a catchSSH-like shell

    The catch: The command line is the provider's own tool that feels like SSH; a standard SSH client cannot connect.

    docs-confirmed “Connect to a running sandbox for interactive debugging with an SSH-like experience:” Source

  • Note: There is no SSH address or SSH server; the only shell is the provider's own terminal.

    inferred “You can explore the contents of a sandbox with an interactive terminal.” Source

Need several capabilities at once? Add more in the capability finder. Something wrong here? Use the report link at the bottom of the page.