Botperch

CapabilitiesCustom domains

Automatic HTTPS

The provider gets and renews the security certificate for your domain.

Short answer: 5 of 16 providers offer it fully: Agent 37, Blaxel, Cloudflare Sandbox, Runtime and boxd. With a catch: Lizard and Modal. Checked 29 October 2026.

5 yes2 with a catch4 no5 not publishedChecked 29 October 2026

Who offers it

Part of Custom domains, which explains why it matters.

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

  • Agent 37YesPlatform certificate

    The provider's edge serves the certificate for your domain; there is nothing to renew yourself.

    docs-confirmed “Set the nameservers” Source

  • BlaxelYesIssued per domain

    A certificate is issued for each domain, validated once when you add it.

    docs-confirmed “Blaxel issues a TLS certificate for each custom domain.” Source

  • boxdYesAutomatic

    The provider checks your records and issues the certificate without you doing anything else.

    docs-confirmed “boxd verifies your DNS and issues TLS certificates automatically.” Source

  • Cloudflare SandboxYesZone certificate

    Cloudflare already holds the certificate for your domain and renews it for you.

    inferred “A wildcard DNS record and the route `*.example-previews.com/*` send every preview hostname to your Worker.” Source

  • RuntimeYesLet's Encrypt

    A certificate is obtained for your hostname on the first visit and renewed by the provider.

    docs-confirmed “Custom domain: a sandbox's web port at your own hostname, with HTTPS.” Source

  • LizardWith a catchApps only

    The catch: Certificates are handled for deployed apps, but a sandbox preview has no domain to certify.

    inferred “a request without the sandbox's access token gets HTTP 401” Source

  • BoatNo

    Note: There is no custom domain, so there is no certificate for the provider to manage.

    docs-confirmed “boat does not support custom domains.” Source

  • DaytonaNo

    Note: You run the forwarding service, so you also get and renew the certificate.

    docs-confirmed “host your proxy under your own domain” Source

  • E2BNo

    Note: The certificate is obtained by the server you run in front of the machine, not by the provider.

    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

  • SandboxerNo

    Note: You point the name and terminate the certificate yourself.

    docs-confirmed “First-class custom domains are on the roadmap.” Source

  • InstaBoxNot published

    No custom domain is published, so there is no certificate feature to describe.

    inferred “The URL is `https://<port>-<machine id without m_>.<domain>/`.” Source

  • MorphNot published

    No custom domain is published, so there is no certificate feature to describe.

    inferred “Expose Http Service” Source

  • SpritesNot published

    No custom domain is published, so there is no certificate feature to describe.

    inferred “A Sprite URL is private by default.” Source

  • TensorlakeNot published

    No custom domain is published, so there is no certificate feature to describe.

    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 is published, so there is no certificate feature to describe.

    inferred “Run untrusted or agent-generated code in isolated Linux microVMs.” Source

Related

Other capabilities in this feature

Where it decides the choice

The feature

Words used here

  • Custom domainServing what the machine runs at your own web address, such as agent.example.com, instead of the provider's.

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