Network limits control outbound internet access from sandboxes. Each sandbox runs behind a firewall that restricts which external IP addresses and domains it can reach, preventing untrusted code from exfiltrating data or contacting arbitrary hosts.
Default network policies are applied automatically based on your organization’s tier. You can also configure access per sandbox using these parameters:
networkAllowList for IPv4 CIDR ranges
domainAllowList for domains and wildcard domains
networkBlockAll to block all outbound traffic
outboundProxyUrl to route sandbox HTTP(S) traffic through an upstream proxy
Network limits are automatically applied to sandboxes based on your organization’s billing tier. This provides secure and controlled internet access for development environments:
Tier 1 & Tier 2: Network access is restricted and cannot be overridden at the sandbox level. Organization-level network restrictions take precedence over sandbox-level settings. Even with networkAllowList or domainAllowList specified when creating a sandbox, the organization’s network restrictions still apply. Essential services remain reachable.
Tier 3 & Tier 4: Full internet access is available by default, including essential services. You can set custom network settings per sandbox. A sandbox-level networkAllowList, domainAllowList, or networkBlockAll replaces the default policy for that sandbox. Enforcement is strict: only destinations you list are allowed (or none, when blocking all). Essential services do not bypass a sandbox allow list or block-all setting.
Set networkAllowList, domainAllowList, or networkBlockAll when creating a sandbox to control which external hosts the sandbox can reach. The options are mutually exclusive. Set at most one non-empty value. Sending a conflicting combination returns a 400 error. Empty-string allow lists count as unset and never conflict.
On Tier 3 and Tier 4, setting an allow list or networkBlockAll at create time applies that policy for the sandbox. Destinations not on the allow list are blocked, including essential services such as GitHub, npm, and PyPI, unless you add those domains or CIDRs yourself.
This operation requires the WRITE_SANDBOXES permission. Organizations on Tier 3 and Tier 4 can change outbound firewall policy on a running sandbox. The API applies the new rules and persists them on the sandbox. The sandbox keeps running; stop or start are not required.
Organizations on Tier 1 or Tier 2 cannot override network policy at the sandbox level, and the API returns an error in that case.
When an allow list or networkBlockAll is applied, enforcement is strict for that sandbox: essential services are not auto-allowed.
Sending networkAllowList as an empty string clears a stored CIDR allow list
Sending domainAllowList as an empty string clears a stored domain allow list
Sending networkBlockAll: true blocks all outbound traffic and clears both the stored CIDR and domain allow lists
Sending only networkBlockAll: false removes the block-all rule and clears both the stored CIDR and domain allow lists
An outbound proxy sends a sandbox’s HTTP(S) egress through a proxy you control. You can set the outboundProxyUrl parameter when creating a sandbox to specify the upstream proxy URL Daytona should chain to. Daytona routes matching traffic through its egress proxy to that upstream instead of dialing destinations directly.
Daytona stores the proxy URL on the sandbox (encrypted at rest) and sets HTTP_PROXY (and HTTPS_PROXY) inside the sandbox.
HTTP(S) clients that respect those variables send traffic through Daytona’s egress proxy, which chains to your upstream.
Clients that do not respect HTTP_PROXY are not sent to your upstream proxy by these variables. To limit the destinations they can reach, also set a domainAllowList.
Platform telemetry to the Daytona-managed collector is not routed through your outbound proxy.
The URL may use http or https and may include credentials in the userinfo, for example http://user:pass@proxy.example.com:3128. Implement domain allow listing on your own proxy to control which destinations the sandbox can reach.
Constraint
Value
Schemes
http, https
Max length
2048 characters
Host
Must not be localhost or a private, loopback, or link-local IP literal
The network allow list is a comma-separated list of IPv4 CIDR blocks. When a CIDR allow list is set, outbound traffic is limited to the listed ranges. Other destinations are blocked, including essential services whose resolved addresses are not covered by the list.
IPv4 only: hostnames, domains, and IPv6 are not supported
CIDR required: every entry must include a / prefix length integer in the range 0 to 32 (inclusive), for example: /32
CIDR format: use standard CIDR notation (A.B.C.D/N). Do not include extra / segments
Max 10 entries: the list cannot contain more than 10 comma-separated items
Whitespace is ignored: entries are trimmed, so spaces around commas are ok
The domain allow list is a comma-separated list of DNS domains. When a domain allow list is set, outbound traffic is limited to the listed domains. Other external domains are blocked, including essential services that are not on the list.
Domains only: use hostnames such as example.com or api.openai.com. Do not include protocols, paths, ports, or query strings
Wildcards supported: prefix a domain with *. to allow the base domain and its subdomains, for example *.daytona.io
Max 100 entries: the list cannot contain more than 100 comma-separated items
Whitespace is ignored: entries are trimmed, so spaces around commas are ok
Clear on update: send domainAllowList as an empty string when updating network settings to clear a stored domain allow list
No essential-services bypass: GitHub, npm, PyPI, model providers, and other essential services are not auto-allowed. Add each domain you need.
Daytona enforces the domain allow list on HTTPS traffic by the host name each request is sent to. In sandboxes created with a domain allow list, Daytona’s egress proxy terminates TLS for allowed hosts and re-encrypts the connection with a certificate issued by a Daytona certificate authority (CA).
Daytona mounts a CA bundle at /etc/daytona/netleash/ca.crt that contains the Daytona CA and the standard public root CAs. When the sandbox starts, Daytona adds the Daytona CA to the sandbox’s system CA bundle and points SSL_CERT_FILE, NODE_EXTRA_CA_CERTS, REQUESTS_CA_BUNDLE, CURL_CA_BUNDLE, GIT_SSL_CAINFO, and DENO_CERT at the mounted bundle. Clients that ship their own CA bundle or pin server certificates do not trust the Daytona CA by default. Add the Daytona CA from /etc/daytona/netleash/ca.crt to their trust store to reach allowed hosts over HTTPS.
Essential services are package registries, git hosts, model providers, and related hosts that remain reachable under the default tier-based network policy on all tiers.
They do not apply when a sandbox has a custom networkAllowList, domainAllowList, or networkBlockAll on Tier 3 or Tier 4. In those modes, only the destinations you configure are allowed (or none). To keep an essential service reachable under an allow list, include its domains or CIDRs in that list.