Data
Data in Motion
Eden's Data in Motion category connects applications and AI to databases, caches, vector systems, object stores, APIs, workflows, and pipelines through governed endpoints.
The data can remain in its existing environment. Eden applies identity, credentials, policy, routing, transformation, telemetry, and audit at the access path.
Capabilities
| Capability | What it covers | Start here |
|---|---|---|
| Multi-gateway | Put a governed, protocol-aware path in front of databases, APIs, models, and services. | Endpoints |
| Auto caching | Place reusable reads near eligible workloads with freshness, policy, and tenant boundaries. | Cache and locality |
| Traffic replication | Mirror and compare traffic while the source remains authoritative. | Traffic Mirroring |
| APIs & integrations | Publish approved interfaces across REST, GraphQL, functions, SaaS, and developer tools. | Published APIs |
| Workflows | Define versioned plans, triggers, templates, and operational evidence. | Workflows |
| Transactions & composition | Compose typed, conditional, cross-system operations with controlled access. | Transactions |
Data Gateway
The Data in Motion layer applies Eden's organization, identity, credential, policy, routing, telemetry, and evidence model to every supported data endpoint. It does not require copying all data into a new central store before applications or AI can use it.
Cache and locality
Eden can place reusable state near eligible workloads while retaining tenant, project, identity, data-source, runtime, and compatibility boundaries. Locality is an execution decision, not a change in ownership or access policy.
Supported data surfaces
The endpoint catalog includes relational, document, key-value, wide-column, analytical, vector, object, HTTP, and managed platform connections. See Databases and Servers, Storage, And APIs.
How Eden implements data
- Gateway supplies endpoint access, protocol handling, permissions, queries,
templates, APIs, workflows, and request evidence.
- Live Migrations supplies movement, replication, validation, and recovery.
- Runtime and Fleet supplies workload and state locality where distributed execution
is enabled.