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; the sign-in service's webhooks (/api/auth/webhooks/workos) |
MCP_HOST | 443 (/mcp) | eode-mcp :8848 | Your MCP clients. Hosted assistants call from their vendor's cloud |
| Both | 80 | The gateway | Redirect to HTTPS, and the Let's Encrypt HTTP challenge |
One internet-facing Network 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 | eode-app, eode-mcp | Every conversation with RIA |
api.workos.com | eode-app | Sign-in and organizations |
| Your sign-in domain | eode-app, eode-mcp, your users' browsers | The sign-in page, and the keys MCP checks tokens against |
River Logic's image registry (Amazon ECR, us-east-1) | Your nodes | eode's images, at install, at upgrade, and when a new engine starts on a node without the image |
River Logic's template storage (Amazon S3, us-east-1) | The installer | The release's templates and starter models |
fonts.googleapis.com, fonts.gstatic.com, api.fontshare.com and its font CDN | Your users' browsers | The web app's typefaces |
| AWS APIs in your region: STS, Secrets Manager, ECR, EKS, S3, CloudWatch Logs, RDS, KMS | The cluster, the secrets driver, the installer | Pod Identity, secrets, images, logs |
dl.k8s.io, get.helm.sh, charts.jetstack.io, kubernetes-sigs.github.io, aws.github.io, Docker Hub, Amazon Linux package mirrors | The installer, on every run | Its tools and the add-on charts |
Docker Hub, quay.io, registry.k8s.io, public.ecr.aws | Your nodes | The add-ons' images (gateway, certificates, secrets driver) |
Outbound, only if you turn it on
| Endpoint | When |
|---|---|
acme-v02.api.letsencrypt.org | Automatic certificates (TlsMode LetsEncrypt) |
| Any data source a user connects | A user adds a data connection. Only TCP 443 is allowed outside your VPC, so a database on another port can't be reached |
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. 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 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.
With the defaults, a data connection can reach a source outside your VPC on port 443 only. A database inside your
network, or on another port, needs a change to DataConnectionDenyCidrs and to the eode network policy; ask us
before you make one.