Networking and ports
Gateway defaults to WebSocket port 80 and Vision HTTP port 81. TCP port 82 and HTTP/2 port 83
are disabled unless --tcpServer or --http2Server is enabled.
Deployment checklist
- Bind explicit ports in production.
- Expose only the selected runtime listener and operationally required Vision access.
- Restrict Vision to trusted networks unless public access is intended and reviewed.
- Use a WebSocket-capable proxy for
ws:///wss://; preserve upgrade headers and suitable idle timeouts. - Terminate TLS at reviewed Gateway-capable infrastructure. Gateway does not provide native certificate configuration.
- Keep stateful connections pinned to the same Gateway instance.
- Configure CORS only for browser-facing HTTP surfaces.
--corsConfigvalues can override CLI origin defaults during startup.
The generated local WebSocket host is typically copied from Vision and includes the /ws path. Do
not invent TCP or HTTP/2 connection strings; use generated configuration for the selected runtime.
Graftcode does not ship a canonical Kubernetes Service/Ingress, reverse-proxy recipe, native TLS flag, or universal idle-timeout value. Validate upgrades, frame sizes, and long-lived connections through your actual proxy.