Products Overview
Eden is the product family built around Eve, the gateway runtime and unified API documented in this repository. The products share the same organization model, endpoint registry, authentication, RBAC, telemetry, and audit trail, but they solve different customer problems.
Use this section when you need to understand what each product does before you configure endpoints, call APIs, or run a migration.
Product Map
| Product | Primary job | Typical users | Main docs |
|---|---|---|---|
| Eve | Govern access to models, tools, APIs, and databases through one gateway path. | Platform engineers, security teams, application teams | Eve Gateway |
| Adam | Let people and agents use Eve-connected systems through chat, tools, and governed workflows. | Application teams, operators, analysts, agent builders | Adam |
| Exodus | Move live database workloads between source and target systems with validation and rollback. | Infrastructure teams, database owners, migration operators | Exodus Migrations |
Each product has its own documentation section in the sidebar. Start with the product overview, then use the section pages for operating model, access boundaries, lifecycle, and telemetry details.
How The Products Fit Together
Eve is the control plane and request path. It stores organizations, users, endpoints, templates, workflows, permissions, and credentials. It also exposes the REST API and gateway services that applications and operators use.
Adam is the AI-facing product experience. Adam uses Eve for authentication, endpoint access, tool discovery, tool execution, telemetry, and policy. If a user does not have access to an endpoint through Eve, Adam should not expose that endpoint or use its tools on the user's behalf.
Exodus is the migration product. It uses Eve endpoints and interlays to observe traffic, validate targets, move historical data, coordinate live traffic, and keep rollback available until the operator commits the migration.
Shared Concepts
The products share these concepts:
| Concept | Why it matters |
|---|---|
| Organization | Tenant boundary for users, robots, endpoints, workflows, templates, and migrations. |
| User or robot identity | The subject that authenticates and receives permissions. |
| Endpoint | A named connection to a database, model provider, API, tool, or service. |
| RBAC grants | Control-plane and data-plane permissions that determine what a subject can configure or use. |
| Interlay | A protocol listener that applications connect to when Eve needs to sit directly in the traffic path. |
| Template | Reusable endpoint or workflow configuration. |
| Telemetry | Metrics, logs, traces, migration events, and request records produced from the gateway path. |
Which Product Should I Start With?
Start with Eve when you need a governed path to production systems. Eve is the right starting point for endpoint onboarding, RBAC, connection pooling, request routing, command policy, observability, and REST API usage.
Start with Adam when the user experience is conversational or agentic. Adam is the right starting point when people or AI agents need to ask questions, discover tools, invoke endpoint operations, or work through governed workflows.
Start with Exodus when the business goal is a live database migration. Exodus is the right starting point when the source and target must run in parallel, traffic must be observed or mirrored, rollback must stay available, and operators need a staged migration runbook.
Common Deployment Shape
A typical deployment has:
- Eve running as the API and gateway runtime.
- A backing control-plane store for organization, user, endpoint, and workflow state.
- One or more endpoint connections for databases, model providers, APIs, or tools.
- Optional interlays for protocol-level traffic such as Redis, PostgreSQL, MongoDB, or migration workflows.
- Observability export to the customer's metrics, logs, traces, or dashboard stack.