Compare MongoDB environments

Environment Compare finds structural drift between two MongoDB deployments. The destination always connects in read-only mode, even when the main workspace allows writes.

Compare one collection

1. Open Compare and choose Collection.
2. Select the source database and collection.
3. Enter the destination connection string and connect.
4. Select the destination database and collection.
5. Choose Compare environments.

The comparison reads bounded field inference, collection validation, and index definitions. It does not return documents. Review differences by category, then export the result as JSON or a mongosh migration artifact.

Generated migration output never drops databases or collections. Review every command against the intended direction before running it.

Compare a deployment

Choose Deployment to inventory user databases and collections on both sides. The result reports:

• databases or collections missing from either environment;
• collection-kind differences;
• validator and validation-setting drift;
• index definition and visibility drift;
• bounded sampled schema differences;
• incomplete coverage and authorization limits.

Exact namespace matches map automatically. Add an explicit override when a collection was renamed between environments. Inventory and comparison reads can be canceled at the driver boundary.

Save a recurring review

A deployment review profile stores the cluster pair, namespace overrides, sample size, comparison limit, and local run history. Select one complete known-good run as the baseline. Later runs classify new, changed, resolved, and unchanged drift against that explicit baseline.

Profiles and baselines remain local. They are bound to verified deployment identities, not host labels alone. If local persistence cannot be read back exactly, mongoui marks the change session-only.

Export a CI policy

Export a saved review profile for the native mongoui-drift executable. The policy can include the explicit bounded baseline, but excludes connection strings, credentials, documents, validator bodies, and migration commands.

The CLI receives source and destination URIs at runtime through environment variables. See Deployment drift CLI for commands, exit codes, and download verification.