Self-hosting eode
Run the eode web app and MCP endpoint in your own AWS account, installed and upgraded from one template.
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 conversations stay in databases and storage in your account.
How it works
Get invited
River Logic invites your AWS account in the eode portal (portal.eode.app). That gives your account access
to eode's images and install template, and gives you your sign-in details. See Before you start.
Launch the stack
Open the Launch Stack link from the portal, 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 own company login.
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 account | From River Logic |
|---|---|
| The stack: network, Amazon EKS, PostgreSQL, Redis, file storage, secrets | The install template and every release, built and tested |
| Your hostnames and certificates | Access to eode's images, for your account only |
| Your LLM provider account and its spend limit | Upgrade steps for every release |
| Backups, monitoring, network rules | Support through the eode portal |
Azure is next. Today the one-click install is for AWS only.
Related
- Architecture: what runs where, and what the stack creates.
- Network and security: what leaves your account, and what doesn't.
- Settings: everything you can change after install.