Who offers it

Part of Outbound network: egress, allowlists and static IP, which explains why it matters.

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

  • Agent 37Yes100 IPv4 entries

    Only the listed addresses can be reached, and name lookups are blocked too unless you list a name server.

    docs-confirmed “DNS counts as a connection. Under `deny-all` or a list, names do not resolve unless a resolver is on the list.” Source

  • boxdYes256 entries

    An allowlist is enforced outside the machine, so nothing inside can loosen it.

    docs-confirmed “An allowlist of just `none` cuts the machine off from the internet entirely.” Source

  • Cloudflare SandboxYesHosts or handler

    Only listed hosts, or what your own small program lets through, can leave the machine.

    docs-confirmed “Use enableInternet = false to block public internet access by default” Source

  • DaytonaYesDomain or address list

    A machine can be limited to a list of domains or addresses, or to an upstream gateway.

    docs-confirmed “On Tier 3 and Tier 4, setting an allow list or `networkBlockAll` at create time applies that policy for the sandbox.” Source

  • E2BYesDomain or address list

    Outbound traffic can be limited to named domains or address ranges.

    docs-confirmed “Control and restrict it with a simple on/off switch or fine-grained allow and deny lists.” Source

  • RuntimeYesAllow list

    A machine can be set to reach only the hosts on a list.

    docs-confirmed “`internet: false` refuses every outbound connection. With an `allow` list, it is allow-list only.” Source

  • SpritesYesDomain list

    A list of allowed domains is applied from outside the machine and cannot be changed from inside.

    docs-confirmed “Applying one is opt-in and done from outside the Sprite.” Source

  • TensorlakeYesDomains or addresses

    A machine can be limited to named domains, addresses or ranges, and a blocked entry always wins.

    docs-confirmed “Use `allow_out` when you want a sandbox to reach only selected destinations.” Source

  • Vercel SandboxYesDomain or address list

    A network policy can allow only listed domains or address ranges, and an empty policy blocks everything.

    docs-confirmed “a policy with no allowed domains or CIDR ranges blocks all outbound traffic, including DNS” Source

  • BlaxelWith a catchProxy filter

    The catch: The filter only sees programs that use its settings; anything else gets out unless stricter enforcement is switched on.

    docs-confirmed “Traffic from tools that ignore proxy environment variables will not be filtered unless” Source

  • BoatWith a catchFirewall inside

    The catch: The rules live inside the machine, where the agent has administrator rights and can undo them, and they are lost when the machine is restored.

    docs-confirmed “boat has no API setting for network rules.” Source

  • Note: There is no setting that limits which sites a machine may reach.

    inferred “This scopes credential use, not all sandbox network access.” Source

  • Note: There is no allowlist or outbound firewall setting; every machine can reach the whole internet.

    docs-confirmed “There is no egress allowlist, domain filter or outbound firewall setting in Sandboxer.” Source

  • LizardNot published

    No allowlist or outbound filtering is documented.

    inferred “Sandbox egress has no separate per-GB charge.” Source

  • MorphNot published

    No outbound allowlist is published.

    inferred “Typical components may include but are not limited to compute, snapshot storage, and egress.” 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.