Skip to main content
Version: Next (Private Preview)

Pipeline component catalog

Nexo components inspect, enforce, transform, route, or observe MongoDB traffic. A pipeline orders them by phase:

  • Connection establishes the client-to-Proxy session.
  • Request runs before an operation reaches MongoDB.
  • Router chooses an upstream target.
  • Response runs before a reply returns to the client.

:::caution Availability is release-specific

A component appearing in the dashboard, a schema, or source code does not by itself mean that an installed Nexo bundle executes it. Select the documentation version matching your installed bundle and check the availability column before deployment.

:::

Availability summary

The minimum tiers below follow the canonical Nexo pricing entitlement list. Growth has the same component set as Pro with higher limits and additional sub-features. Query Size Limit is a selectable compatibility alias of Query Guard and does not count as a separate commercial component.

ComponentPhaseMinimum tierNext documentation0.2.0 bundle
Connection PipelineConnectionFreeUnavailable at runtimeSchema installed and recorded, but settings are not delivered to the runtime
LoggingRequest + responseFreeCatalogReconciled and executable
MetricsRequest + responseFreeCatalogReconciled and executable
Index AdvisorRequest + responseFreeCatalogSchema only
X-RayRequest + responseFreeBackend capability; not catalog-selectableNo dedicated CRD; not deployable
Access Control (Filter)RequestFreeIneffective contractCRD/runtime fields differ; do not rely on access enforcement
Query GuardRequestFreeCatalogSchema only
Query Size LimitRequestFreeCatalog alias of Query GuardReconciled and executable
Version CompatibilityRequest + responseFreeCatalogReconciled and executable
Rate LimitingRequestProCatalogReconciled and executable
Query RewriteRequestProCatalogReconciled and executable
MongoDB CacheRequest + responseProCatalogReconciled and executable
Read/Write SplitterRouterProCatalogSchema only; router phase is not executed
Traffic SplitRouterProCatalogReconciled, but the pinned Proxy does not execute the router phase
Shadow TrafficRequest + responseProCatalogReconciled and executable
PII MaskingResponseProIneffective contractInstalled CRD has no masking fields; do not rely on data redaction
Audit LogRequest + responseProUnavailable end to endCRD/runtime fields differ; no supported audit evidence
Tenant IsolationRouterBusinessCatalogReconciled, but the pinned Proxy does not execute the router phase
Field EncryptionRequest + responseEnterpriseEnterprise implementation; confirm bundle publicationSchema only
Change Stream FanoutResponseNo canonical entitlementDashboard manifest onlyUnsupported
Geo-RoutingRouterNo canonical entitlementDashboard manifest onlyUnsupported
Cross-Cluster FederationRouter + responseNo canonical entitlementDashboard manifest onlyUnsupported
Query ReplayRequest + responseNo canonical entitlementDashboard manifest onlyUnsupported
Intelligent FailoverRouter + responseNo canonical entitlementDashboard manifest onlyUnsupported

:::warning 0.2.0 reconciliation requirement

The pinned Proxy controller does not watch NexoTrafficSplit, NexoTenantIsolation, NexoQuerySizeLimit, or NexoVersionCompat. After editing any of those resources, trigger reconciliation of the owning NexoProxy through the approved deployment workflow and verify the active graph revision.

:::

:::note Known dashboard tier-label mismatch

The canonical entitlement list above is authoritative. The current dashboard manifests still display Version Compatibility as Pro and Index Advisor, Cache, and Audit as Business, although their canonical minimum tiers are Free, Free, Pro, and Pro. Until the dashboard labels are corrected, an incorrect badge must not override the licensed entitlement decision.

:::

Dashboard-manifest-only concepts

The following built-in manifests can appear in legacy or secondary dashboard catalog surfaces, but they are absent from the canonical tier entitlement list and do not have a supported deployment contract. A visible card is not permission to deploy them.

Change Stream Fanout

Describes multiplexing one MongoDB change stream to multiple consumers with buffering, delivery guarantees, filtering, and resume-token storage. No supported Nexo bundle currently publishes it as an entitled component.

Geo-Routing

Describes selecting a MongoDB target from region, database, client, header, or user metadata for residency-aware routing. It has no canonical entitlement or supported runtime contract.

Cross-Cluster Federation

Describes presenting databases or collections across multiple MongoDB clusters as a logical federation, with optional cross-cluster aggregation and failover. It is not a published Nexo component.

Query Replay

Describes recording sampled production traffic and replaying or comparing it against a test target for migration validation. Recording may contain sensitive customer data; no supported bundle publishes this component.

Intelligent Failover

Describes health-scored multi-cluster traffic shifting and failback. It has no canonical entitlement, and no released runtime contract should be inferred from the dashboard manifest.

Marketplace entries

The dashboard code contains sample marketplace cards for community plugins. Private Preview does not publish a supported live plugin marketplace or guarantee those sample artifacts. Treat only bundle-pinned, signed, approved plugins as deployable components.

Sample cardIntended conceptPrivate Preview status
Field TrimmerRemove configured response fieldsSample only
Timestamp InjectorAdd request/response timestampsSample only
Mock ResponsesReturn synthetic responses for testingSample only
Chaos MonkeyInject latency and faultsSample only
Slack AlertSend query or policy alerts to SlackSample only
S3 Query ArchiveArchive sampled query payloadsSample only
PagerDuty IncidentEscalate policy or deployment failuresSample only
Elasticsearch SyncStream query events to ElasticsearchSample only

Search Nexo documentation

Type to search titles, headings, and page content.