What's New

:::caution Draft — not a GA release announcement

No production or GA Nexo release notes have been published here. The only executable onboarding path in these docs is the licensed Private Preview workflow.

:::

Next (Private Preview)

• Added full documentation version selection with immutable 0.2.0 snapshots.
• Search, page status, navigation, compatibility, and release guidance follow the selected documentation version.
• Expanded product documentation with Manager and Control Plane responsibilities, nexoctl command/how-to references, and the complete Operator CRD catalog.

Product changes

Product	Recently verified change
Nexo Manager	Hardened managed-resource ownership and uninstall lifecycle; added Manager protocol capability advertisement.
Nexo Control Plane	Hardened trial deployment authorization and Manager-token handling; bounded orchestration capability data; retained configuration compare and rollback workflows.
nexoctl	No CLI release newer than 0.2.0 is documented. The reference now distinguishes implemented commands from currently supported workflows.
Nexo Operator	Current documentation records all 24 installed CRDs and identifies the six schemas not reconciled by the chart-pinned Operator.

Private Preview documentation baseline — 2026-08-12

• MongoDB evaluation is available only to licensed customers and approved evaluators.
• The Nexo Edge chart interface verified by these docs is 0.2.0.
• The quickstart uses a disposable MongoDB Community 7.0.14 fixture.
• Redis and PostgreSQL are planned and are not implemented.
• Initial architecture, operations, security, troubleshooting, compatibility, and demo content is available for review.
• The editable architecture source is published with the site.

This baseline describes Preview documentation, not a production release, support commitment, SLA, or compatibility guarantee.

Nexo Manager

• Manager participates in the Nexo release-bundle contract.
• The 0.2.0 chart pins Manager tag 20260613.371-384b887; an immutable public digest is not published in these docs.
• The 0.2.0 heartbeat reports runtime inventory but not bundle version, supported kinds, pipeline reference kinds, or CRD schema fingerprint.
• The Next source line adds Manager protocol capability advertisement and ownership safeguards, but this is not a new customer release by itself.

See Nexo Manager versions. Before changing a deployed bundle, review Upgrade and rollback.

nexoctl

• Version 0.2.0 implements login, status, upgrade, diagnostics, support-bundle, and plugin development commands.
• Support bundles can be generated, inspected, and redacted.
• Login, status, and upgrade are not end-to-end compatible with the current Control Plane; use the console for those workflows.
• API-key input, support-bundle redaction, and plugin publishing have documented security limitations.

See the nexoctl command reference.

Nexo Operator

• The 0.2.0 bundle installs 24 namespaced nexo.io CRDs but its pinned Operator reconciles 18 of them.
• Every current CRD serves and stores v1alpha1.
• Six are schema-only: NexoConnectionPipeline, NexoEchoUntrusted, NexoFieldEncryption, NexoIndexAdvisor, NexoQueryGuard, and NexoReadWriteSplit.
• CRDs are retained after Helm uninstall and require an explicit cluster-administrator decision before deletion.

See the Operator CRD catalog.

Product release entry template

Release <version> — <date>

Maturity: <stable | beta | preview>

Highlights

• <Customer-visible capability and why it matters.>
• <Operational or usability improvement.>

MongoDB compatibility

<State tested additions, changes, or no change.>

Upgrade notes

<State supported source versions and required actions.>

Component changes

Component	Version or digest	Customer-visible changes	Compatibility notes
Manager	<tag and sha256 digest>	<Capabilities, fixes, or no change>	<Supported bundles, CRDs, and rollback constraints>
Operator	<tag and sha256 digest>	<Changes>	<Compatibility>
Proxy	<tag and sha256 digest>	<Changes>	<Compatibility>

Known issues

• <Issue, impact, and workaround.>

Not included

Redis and PostgreSQL remain planned and are not implemented unless a future verified release explicitly states otherwise.