Installation and deployment modes
Nexo does not currently publish a self-service installer, public Helm repository, Docker Compose distribution, or standalone binary. Licensed customers and approved evaluators use the Nexo console to create an environment, mint an expiring registry token, and obtain an authenticated, version-pinned Helm command.
Deployment modes
Customer-managed Kubernetes — Private Preview
Run the Nexo data plane in a Kubernetes cluster you operate. You manage cluster capacity, networking, availability, upgrades, and access to the MongoDB upstream.
Isolated evaluation deployment — Private Preview
Use an isolated, non-production deployment to validate connectivity and pipeline behavior. Do not treat an evaluation topology as production-ready without completing the production checklist.
Managed service, public marketplace, Docker Compose, VM/bare-metal, and public air-gapped paths are Planned or undefined, not available installation choices.
Network requirements
Allow:
- database clients to reach the Nexo listener;
- Nexo to reach MongoDB;
- Nexo management components to reach documented service endpoints;
- DNS and certificate validation required by your configuration.
Do not expose database listeners publicly unless your architecture explicitly requires it and compensating controls are in place.