River Logiceode docs
Reference

Network

Every inbound and outbound connection, the network policies, and the ranges the install needs.

Inbound

HostnamePortRoutes toWho calls it
APP_HOST443eode-app :8787Your users' browsers; the sign-in service's webhooks (/api/auth/webhooks/workos)
MCP_HOST443 (/mcp)eode-mcp :8848Your MCP clients. Hosted assistants call from their vendor's cloud
Both80The gatewayRedirect 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

EndpointFromWhy
api.anthropic.comeode-app, eode-mcpEvery conversation with RIA
api.workos.comeode-appSign-in and organizations
Your sign-in domaineode-app, eode-mcp, your users' browsersThe sign-in page, and the keys MCP checks tokens against
River Logic's image registry (Amazon ECR, us-east-1)Your nodeseode'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 installerThe release's templates and starter models
fonts.googleapis.com, fonts.gstatic.com, api.fontshare.com and its font CDNYour users' browsersThe web app's typefaces
AWS APIs in your region: STS, Secrets Manager, ECR, EKS, S3, CloudWatch Logs, RDS, KMSThe cluster, the secrets driver, the installerPod 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 mirrorsThe installer, on every runIts tools and the add-on charts
Docker Hub, quay.io, registry.k8s.io, public.ecr.awsYour nodesThe add-ons' images (gateway, certificates, secrets driver)

Outbound, only if you turn it on

EndpointWhen
acme-v02.api.letsencrypt.orgAutomatic certificates (TlsMode LetsEncrypt)
Any data source a user connectsA 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

NamespaceAllowed inAllowed out
eode-enginesTCP 50051 from eode-app and eode-mcp onlyDNS, and your VPC ranges. No internet
eodeThe Gateway to 8787 and 8848, and the certificate challengeDNS, 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.

On this page