Compatibility — Private Preview
Nexo has no published GA compatibility contract. Current evidence comes from an internal integration suite; it is not a promise that every server patch, managed service, driver, topology, command, authentication mechanism, or TLS combination is supported.
Evidence available on 2026-08-12
| Area | Verified boundary |
|---|---|
| Distribution | Licensed/approved evaluation through the authenticated Nexo console and registry |
| Nexo Edge chart interface | 0.2.0 |
| MongoDB integration fixtures | Community tags 4.2, 4.4, 5.0, 6.0, 7.0, and 8.0 |
| Integration-test Go driver | go.mongodb.org/mongo-driver 1.16.0 |
| Quickstart fixture | Standalone MongoDB Community 7.0.14, no TLS or authentication, isolated namespace |
| Protocol implementation | OP_MSG traffic; protocol presence does not imply complete command coverage |
| Redis and PostgreSQL | Planned; not implemented |
The fixture range states what the repository test matrix is configured to exercise. It does not certify every patch release or every combination in that range.
Nexo component identity
| Component surface | Current published evidence |
|---|---|
| Nexo customer release | Private Preview documentation baseline; no stable release manifest published |
| Nexo Edge chart interface | 0.2.0 |
| Nexo Manager | The chart pins tag 20260613.371-384b887; obtain the immutable digest from approved release metadata |
| Manager compatibility | The 0.2.0 heartbeat reports runtime inventory but not bundle version, supported kinds, pipeline references, or schema fingerprint |
| Operator, Proxy, and steps | Exact image tags and digests must come from the same digest-complete release bundle |
Do not combine component tags from different bundles or treat a standalone Manager chart version as proof of compatibility.
Not yet published as supported
- a GA Nexo release or public support lifecycle;
- Atlas, Cosmos DB for MongoDB, or other managed-service matrices;
- exhaustive driver and language matrices;
- sharded-cluster and replica-set discovery guarantees;
- exhaustive command, transaction, retryable-write, or change-stream guarantees;
- production TLS and authentication combination matrices;
- public air-gapped, VM, Docker Compose, or standalone binary installation paths.
Licensed customers and evaluators should obtain a release-specific compatibility statement before production planning. Treat absent combinations as unverified.