Reference
Network
Every inbound and outbound connection, the network policies, and the ranges the install needs.
Inbound
| Hostname | Port | Routes to | Who calls it |
|---|---|---|---|
APP_HOST | 443 | eode-app :8787 | Your users' browsers |
MCP_HOST | 443 (/mcp) | eode-mcp :8848 | Your MCP clients |
One load balancer (the Gateway) serves both. It keeps a stream open for up to an hour and
keeps each browser on one eode-app copy with a cookie. Engines are never exposed.
Outbound, always
| Endpoint | From | Why |
|---|---|---|
api.anthropic.com, or your LLM gateway | eode-app, eode-mcp | Every conversation with RIA |
api.workos.com | eode-app, eode-mcp | Sign-in, organizations, MCP token checks |
| Your sign-in domain (from the eode portal) | eode-app, eode-mcp, your users' browsers | The sign-in page and its token keys |
River Logic's image registry (Amazon ECR, us-east-1) | Your nodes and the installer | Images and the install chart |
fonts.googleapis.com, fonts.gstatic.com | Your users' browsers | The web app's typeface |
| AWS APIs in your region: STS, Secrets Manager, ECR, EKS | The cluster and its secrets driver | Pod Identity, secrets, images |
Outbound, only if you turn it on
| Endpoint | When |
|---|---|
acme-v02.api.letsencrypt.org | Automatic certificates (TlsMode LetsEncrypt) |
| Your OpenTelemetry collector | TelemetryEndpoint is set |
| Any data source a user connects | A user adds a data connection |
Feedback filing, support handoff and usage telemetry to River Logic are off in a self-hosted install.
Network policies
| Namespace | Allowed in | Allowed out |
|---|---|---|
eode-engines | TCP 50051 from eode-app and eode-mcp only | DNS, and your VPC ranges (for EFS). No internet |
eode | The Gateway to 8787 and 8848, and the certificate challenge | DNS, your VPC ranges, and TCP 443 to anywhere |
To narrow eode's egress further, put an egress firewall or proxy in front and allow only the endpoints above.
Ranges
DataConnectionDenyCidrs lists every internal range a user's data connection must never reach: your VPC, peered networks, on-premises ranges. Link-local and unspecified addresses are always blocked. It defaults to the stack's VPC.