River Logiceode docs

Self-hosting eode

Run the eode web app and MCP endpoint in your own AWS account, installed and upgraded from one template.

Self-hosting is available by invitation.

Self-hosting runs eode inside your own AWS account: the web app your users sign in to and the MCP endpoint your AI assistants call. Your models, data and conversation history are stored in your account. RIA, eode's assistant, sends each conversation to your LLM provider to answer it.

How it works

Get invited

Your River Logic contact invites your AWS account. That gives your account access to eode's images and install template, and you receive your sign-in details. See Before you start.

Launch the stack

Open the Launch Stack link you were sent, fill in one form, and AWS CloudFormation builds everything. See Install on AWS.

Point your DNS and sign in

Create two DNS records from the stack's outputs, then sign in with your company login through the sign-in service (Sign-in and access).

Upgrade with one update

When a new release is out, update the stack with that release's template and version. See Upgrades.

What you run, what River Logic provides

In your AWS accountFrom River Logic
The stack: network, Amazon EKS, PostgreSQL, Redis, file storage, secretsThe install template and every release, built and tested
Your hostnames and certificatesAccess to eode's images, for your account only
Your LLM provider account and its spend limitUpgrade steps for every release
Backups, monitoring, network rulesThe sign-in service, and support through your River Logic contact

The one-click install is for AWS only. The LLM provider is Anthropic, with your own API key.

Release status

The one-click stack into a new VPC, upgrades and rollback are tested on every release. These options exist but haven't yet been run in a customer install, so the first one is done together with us: installing into an existing VPC, your own ACM certificate, your own KMS key, and Install with Helm on a cluster you already run.

To install into an EKS cluster you already run, use the same Helm chart the stack uses: Install with Helm.

  • Architecture: what runs where, where your data lives, and what the stack creates.
  • Images: the languages and packages in each image.
  • Network and security: what leaves your account, and what doesn't.
  • Settings: everything you can change after install.

On this page