Nexo Control Plane
The Nexo Control Plane is the hosted management service for Nexo. It owns identity, projects, environments, desired configuration, release metadata, deployment orchestration, licensing, and operational history. It is not in the application database traffic path; MongoDB traffic remains inside the customer environment.
Responsibilities
| Responsibility | What the Control Plane does |
|---|---|
| Identity and tenancy | Authenticates users and API keys, manages teams and members, and enforces project and environment access. |
| Project and environment management | Creates projects, registers environments, applies selectors and labels, and tracks heartbeat health. |
| Configuration lifecycle | Stores pipeline configuration, validates supported fields, previews changes, versions revisions, compares revisions, and initiates rollback. |
| Deployment orchestration | Resolves the desired release bundle and configuration into commands for the correct environment, then tracks acknowledgement and rollout status. |
| Compatibility checks | Resolves desired configuration against release metadata and the Manager signals available for the target environment. |
| Release and registry services | Publishes release metadata and issues scoped registry credentials used to install or upgrade Nexo Edge. |
| Commercial controls | Enforces licenses, tier limits, trials, billing state, and feature availability. |
| Governance and observability | Records project audit history, fleet metrics, administrative alerts, and deployment health. |
Features
Environment registration
Each environment has its own identity and connect-token lifecycle. The service tracks cluster binding, Manager heartbeat, installed component versions, capabilities, and deployment state without exposing the Manager credential in ordinary environment responses.
Configuration and revision management
The Control Plane provides a managed lifecycle rather than sending arbitrary YAML:
- Author or update a project pipeline.
- Validate configuration and preview the expected change.
- Save a versioned revision.
- Resolve the revision against the target environment and release bundle.
- Check compatibility and authorization using release metadata and available runtime signals.
- Deliver the operation to Manager and track its acknowledgement.
- Compare or roll back configuration revisions when needed.
Release-aware orchestration
Deployments are resolved against release metadata and the target environment. Current Manager heartbeats provide runtime inventory and Manager protocol capabilities, but not a complete CRD schema inventory. Full kind/reference/schema preflight remains a release contract requirement rather than a current 0.2.0 guarantee.
Security and governance
- role- and project-scoped authorization;
- rate limits and tier enforcement;
- environment-scoped registry credentials;
- audit entries for project operations;
- license heartbeat and revocation checks;
- no dependency on the hosted service for the application-to-database traffic path.
Changes
The Control Plane is an always-current hosted service, so its service changes are listed separately from the versioned Nexo Edge bundle.
Recently verified service changes
- Trial deployment authorization now activates and enforces trials from the deployment lifecycle rather than from UI state alone.
- Environment responses no longer expose Manager connect tokens; token reveal and regeneration use explicit protected operations.
- Orchestration capability payloads and persistence indexes are bounded and validated before they are used for deployment decisions.
- Configuration history supports listing versions, comparing revisions, and requesting rollback to a prior version.
Features that are only persistence foundations or internal rollout work are not treated as customer-available until they appear in What's New.