How Nexo works
Nexo sits between a database client and MongoDB:
- A client opens a connection to a Nexo endpoint.
- Nexo establishes or selects an upstream connection.
- Nexo decodes enough of the supported protocol to evaluate configured policies.
- Pipeline components run in a defined order.
- Allowed traffic continues to MongoDB; responses return through Nexo.
Configuration is managed separately from database traffic. A published configuration becomes a versioned pipeline revision. The runtime receives and activates that revision, while the console reports deployment and configuration state.
Design principles
- Explicit order: pipeline sequence affects behavior.
- Safe rollout: test changes before broad adoption.
- Observable state: distinguish desired configuration from active configuration.
- Protocol honesty: MongoDB is in licensed Private Preview. Redis and PostgreSQL are Planned and not implemented.
Nexo does not replace database authentication, authorization, backups, encryption, or operational monitoring. It adds a policy layer to the connection path.