River Logiceode docs
Reference

Architecture

What runs in your account, what each part does, and how the parts talk.

eode runs as two always-on workloads, one engine per active user, and four AWS services.

How your data moves

How data moves: your data reaches eode-app by upload or data connection; eode-app stores it in PostgreSQL, loads it into your engine to solve, stores the results in PostgreSQL, and serves them to your users and MCP clients; RIA sends what it needs to your LLM providerYour AWS account12 · 435RIAYour dataExcel · CSV · connectionYour usersweb app · MCP clientseode-appreads · checks · storesPostgreSQLdata · resultsYour engineone per user · solvesYour LLM providerAnthropic
How data moves (stacked)Your AWS account152 · 43RIAYour dataExcel · CSV · connectionYour usersweb app · MCPeode-appreads · checks · storesPostgreSQLdata · resultsYour engineone per userYour LLM providerAnthropic
  1. Your data arrives. A user uploads an Excel or CSV workbook in the web app, or a data connection syncs rows from your source. Either way, eode-app reads and checks it.
  2. It's stored. The rows, and the original file, are kept in PostgreSQL as a dataset. Every later step reads from there.
  3. It's solved. When a user builds or runs a model, eode-app loads the data into that user's engine, which solves it. The data reaches the engine from eode-app.
  4. Results are stored. eode-app writes the results to PostgreSQL, one scenario at a time.
  5. You read the results in the web app, or through an MCP client, both served by your install.

RIA works across these steps in a conversation. To answer, it sends your LLM provider what it needs: your question, the text of any document you attach, a profile and a few sample rows of each sheet, and the data and results it reads while working. See Network and security.

What runs where

Self-hosted eode: users and MCP clients reach eode-app and eode-mcp through the gateway; both drive per-user engines; eode-app uses PostgreSQL and Redis, engines use EFS; outbound calls go to the LLM provider, the sign-in service and the image registryYour EKS clusterYour AWS servicesOutside your account · outbound onlyYour usersbrowserMCP clientsassistants · systemsGatewayTLS · your hostseode-appweb app + APIeode-mcpMCP endpointEnginesone per usereode-migrateeach upgradeRDS PostgreSQL+ pgvectorElastiCache RedisTLS + AUTHEFSstarter models · workSecrets Managereode/*Your LLM providerSign-in serviceeode image registry
What runs where (stacked)Your EKS clusterYour AWS servicesOutside · outbound onlyYour usersbrowserMCP clientsassistants · systemseode-migrateeach upgradeGatewayTLS · your hostseode-appweb app + APIeode-mcpMCP endpointEnginesone per userRDS PostgreSQL+ pgvectorEFSstarter models · workElastiCache RedisTLS + AUTHSecrets Managereode/*Your LLM providerSign-in serviceeode image registry

The lines show the main paths. eode-mcp also uses the database and cache, eode-migrate reaches only the database, and every workload reads its keys from Secrets Manager. Outbound calls to your LLM provider and the sign-in service come from eode-app and eode-mcp; your nodes pull images from the registry.

Workloads

All of them come from two images, eode-app and eode-engine.

WorkloadNamespacePortHealthWhat it does
eode-appeode8787GET /api/healthThe web app and its API. Signs users in, runs RIA's conversations, starts and stops engines
eode-mcpeode8848GET /healthz, MCP at /mcpThe MCP endpoint. Checks the caller's token, then works on that user's engine
Engineseode-engines50051—One per active user, created on demand, removed after 30 idle minutes
eode-migrateeode—exits 0Applies database changes before each install and upgrade. The only workload that can read the database owner login

eode-app and eode-mcp can create and delete Deployments, Services and Jobs in eode-engines, and nowhere else. Engines run only on the engine node group, sized by the model they hold (12, 24 or 48 GiB of memory by default; set by EngineMemoryClasses), and need about half a CPU each. Every engine has its own working folder on the shared EFS file system, and reads the starter model library from it; eode-app and eode-mcp see it read-only.

Where your data lives

Everything below is in your AWS account. Your users reach eode through the web app or an MCP client; both work on the same data.

StoreHolds
RDS PostgreSQLUsers and organizations, datasets (the rows and the original files), model and scenario records, solve results, conversations
EFSThe starter model library, and each user's engine working folder
The eode-app imageThe reference knowledge RIA reads about modeling and optimization. It's read-only and changes with each release
ElastiCache RedisCoordination between the web app's copies: which copy is running which conversation, and which engine is busy. Nothing here is the only copy
Secrets ManagerKeys and logins (see Secrets)

Two services outside your account see your data: your LLM provider receives what each conversation with RIA sends it, and the sign-in service receives your users' sign-in details. Every outbound connection is on Network and security.

What the stack creates

Nested stackCreates
NetworkA VPC across 2 or 3 availability zones with public and private subnets and NAT, or nothing (existing VPC). No DNS records
ClusterA new Amazon EKS cluster with a general node group and a tainted engine node group, Pod Identity, and the EFS CSI add-on
DataRDS PostgreSQL 16 (private, encrypted, automated backups), ElastiCache Redis (TLS + AUTH), EFS with an access point and automatic backups, and their security groups
SecretsThe eode/* secrets in Secrets Manager, generated where nobody needs to know them, and the IAM roles each workload uses
InstallerA CodeBuild project that installs the gateway, cert-manager and the secrets driver, prepares the database, installs eode, and checks that the web app answers

On this page