0.0.0.0, then expose its port
through Sail.
HTTP and WebSocket services
Start a server inside your Sailbox:sail.box. Sail handles TLS and forwards
requests to the service. WebSockets use the same endpoint.
You can also expose the port at creation:
Raw TCP ports
UDP ports
Inbound access control
An exposed port is public unless you restrict it. Pass an allowlist when creating or exposing a listener:
Entries are alternatives: matching any entry allows the connection. App names
from other organizations never match.
Who can operate the Sailbox
Listener allowlists control access to services. The Sailbox’svisibility
controls who can run commands, copy files, and manage its lifecycle:
- Org: anyone in your organization can operate it. This is the default.
- Private: only its creator can operate it. An org admin can override operations with a recorded reason; SSH remains creator-only.
visibility="private" in Python, visibility: "private" in TypeScript,
or --visibility private in the CLI when creating a Sailbox. Private visibility
does not make exposed ports private. See Access control
for visibility changes and SSH rules.