CapabilitiesCustom domains
Your own domain
Serve what the machine runs at your own web address.
Who offers it
Part of Custom domains, which explains why it matters.
Fully: Blaxel, boxd and Runtime. With a catch: Agent 37, Cloudflare Sandbox, Daytona, E2B, Lizard, Modal and Sandboxer. Not at all: Boat.
Register one domain and every name under it can point at a sandbox.
docs-confirmed “Blaxel issues a TLS certificate for each custom domain.” Source
Point one name at one machine, or delegate a whole subdomain so every machine gets its own.
docs-confirmed “boxd verifies your DNS and issues TLS certificates automatically.” Source
A machine's web port can answer at your own hostname with a certificate.
docs-confirmed “Custom domain: a sandbox's web port at your own hostname, with HTTPS.” Source
The catch: You must hand over the whole domain and the records that direct it, so it cannot also run your website or email, and it needs $100 of top-ups first.
docs-confirmed “The whole domain’s DNS is delegated to us, so it cannot carry your website, mail, or other records.” Source
The catch: You point a catch-all address at your own small program rather than at the machine, so routing is yours to run.
docs-confirmed “A wildcard DNS record and the route `*.example-previews.com/*` send every preview hostname to your Worker.” Source
The catch: You have to run your own forwarding service under your domain; the provider does not attach the domain for you.
docs-confirmed “host your proxy under your own domain” Source
The catch: You have to run a server of your own in front of the machine to use your domain.
docs-confirmed “We will set up a GCP VM running Caddy server with Docker and Cloudflare DNS to proxy the requests to the Sandboxes.” Source
The catch: Custom domains work for deployed apps, not for a sandbox's preview link.
inferred “a request without the sandbox's access token gets HTTP 401” Source
The catch: Only Team and Enterprise plans get it, and you must move the domain's name servers and ask support to finish setup.
docs-confirmed “Custom domains for Sandbox tunnels are available on the Team and Enterprise plans” Source
The catch: You point a name at the provider's address and supply the security certificate yourself; a native feature is only planned.
docs-confirmed “First-class custom domains are on the roadmap.” Source
- BoatNo
Note: Custom domains are explicitly unsupported; a redirect from your domain to the provider's name does not work either.
docs-confirmed “boat does not support custom domains.” Source
- InstaBoxNot published
No custom-domain feature is published; the public address is a fixed provider name.
inferred “The URL is `https://<port>-<machine id without m_>.<domain>/`.” Source
- MorphNot published
No custom-domain feature appears in the documentation for exposed services.
inferred “Expose Http Service” Source
- SpritesNot published
No native custom-domain support is documented; a community report says Sprites lack the feature regular Fly machines have.
inferred “A Sprite URL is private by default.” Source
- TensorlakeNot published
No custom-domain feature is published; addresses are on the provider's own name.
inferred “`https://<port>-<sandbox-id-or-name>.sandbox.tensorlake.ai` routes to a user service listening on `<port>` inside the sandbox” Source
- Vercel SandboxNot published
No way to attach your own domain to a sandbox port is published; Vercel domains apply to deployments.
inferred “Run untrusted or agent-generated code in isolated Linux microVMs.” Source
Related
Need several capabilities at once? Add more in the capability finder. Something wrong here? Use the report link at the bottom of the page.