Reference
Release and endpoint compatibility
This reference describes the implementation at the 1.82.1 source baseline; the documentation patch is 1.82.2. Redis qualification evidence was reviewed on 2026-10-26 UTC. Match the running image digest, enabled features and endpoint capabilities before using an example. Source support, a recognized endpoint kind and successful qualification are separate facts.
Product profiles
| Surface | Availability / boundary |
|---|---|
| Single-node embedded service | One active process with Turso/DuckDB persistent state |
| HA service | External PostgreSQL/ClickHouse and independent replica state; production chart admits 3–7 replicas |
| HA Redis migration participants | 3, 5 or 7 configured participants; every participant confirms forward stage state |
| OpenAPI discovery | Requires an openapi-enabled build; embedded/external assemblers differ |
| DBOS workflows | Require configured PostgreSQL; not provided by embedded Turso alone |
| SQL Server | Excluded from published product image profiles; a development all-features build is not production support evidence |
| CloudWatch telemetry | AWS-enabled query backend; external ingestion required, no Eden trace API data |
| ShardTelemetry | Requires the matching build overlay and configured provider contract |
Use the installation guide, configuration reference and live OpenAPI for the selected image. Native wire protocols have additional command/session restrictions beyond REST route availability.
Migration data families
| Family | Executable scope | Limit |
|---|---|---|
| Redis / Valkey | Same-family key movement and Redis-compatible live routes | Backend command/version, topology, TTL and session restrictions apply; see Redis support |
| PostgreSQL | Same-kind table mover; selected heterogeneous mappings | A PostgreSQL endpoint does not automatically enable provider-neutral pgvector migration |
| MongoDB | Same-kind document mover; selected heterogeneous mappings | Atlas vector-index behavior is separate from ordinary document movement |
| PostgreSQL / MongoDB / MySQL | Registry-selected heterogeneous routes | Schema/request mappings and execution preflight must pass for the exact direction |
| Qdrant | Same-provider historical-copy preview | Source quiescence, Replace conflict rule and matching schema; live replay/cutover unavailable |
| Elasticsearch / OpenSearch | Historical search/document-copy preview | Source quiescence and supported schema; live capture/replay unavailable |
| Other cataloged vector providers | Configuration/catalog recognition | Catalog membership does not authorize a migration worker |
| Kafka-compatible | Homogeneous non-transactional migration under its protocol contract | Classic groups; compacted topics, transactional/exactly-once migration and multi-producer-gateway HA are blocked |
The runtime capability registry and preflight decide whether an exact route can execute. Do not generalize one provider's historical-copy result into live cutover support or all-provider compatibility. Consult endpoint coverage and heterogeneous planning.
Redis versions and provider capabilities
Eden recognizes Redis and Redis-wire-compatible Valkey endpoints. Server version metadata gates newer commands. Redis 5.x, Redis 7.x and Valkey 7.2 fixtures appear in the retained migration/command checks; they do not establish every minor, module, managed-provider or topology combination as qualified.
Managed endpoints report supported, unsupported, permission_denied, unknown or provider_owned for optional probes. Elasticache marks provider ownership; a Valkey banner alone does not. Unknown capacity/topology is not a successful readiness result. Validate exact ACL, TLS, cluster topology and data types with the customer's selected source and target versions.
For each deployment record the server build/version and modules, image digests, topology and failover mode, client RESP version, command mix, connection modes, key sizes/TTLs, ACL/TLS requirements and the successful preflight/validation results. Use the command catalog to inventory recognized commands, then apply its linked execution restrictions.