Log inRequest a demoStart free

Integrations · NoSQL

NoSQL test data management

Document and key-value stores hold nested, schema-flexible records: a customer document may embed addresses, devices and preferences that a relational model would split into tables.

Test data for these systems needs classification that understands nested fields and masking that keeps identifiers consistent with the relational systems around them.

What test data management needs here

  • Field-shape discovery computed inside your network from a bounded sample, reported as structure only.
  • Flattening of nested documents for classification and masking, then faithful re-nesting.
  • Identity mappings between document keys and relational keys, approved by an owner.

How DataNivra approaches it

  • NoSQL connectors are roadmap work: the design reuses the same masking domains, relationship graph and certification gates as relational sources.
  • Any matching that needs values would run in the agent, never in DataNivra Cloud.
  • Whatever the system, row-level work happens in the DataNivra agent inside your network: only metadata, aggregates and evidence reach DataNivra Cloud.

NoSQL: connector status (4)

None of these connectors can be used today. Each one below shows its honest status; the integration pages describe what you can do in the meantime. Statuses are derived from recorded conformance evidence.

Projected

MongoDB

Strategic roadmap; not shipped. No delivery date is committed.

Strategic roadmap: a read-only MongoDB connector feeding the same workflow.

Projected — details about MongoDB

Learn, try, then start

See the whole workflow — discovery, classification, masking, subsetting and certification — on synthetic data in the interactive demo, then start a free trial. The product overview explains how the customer-resident agent and DataNivra Cloud divide the work.

Other categories: Databases · Data warehouses · Lakehouses · Object storage · Files · SaaS applications · Mainframe · Streaming · APIs.