Everything between “we need test data” and a certified dataset in QA

Discover, subset, mask, certify and provision — every row-level step in your network.

A hosted control plane for people and policy; a customer-resident engine for data. Here is what each part does.

From a dataset request to a certified dataset in QAA dataset request from DataNivra Cloud is leased by the agent in your network. There the production data is discovered, subset and masked or synthesized, then certified; only a dataset that passes certification is provisioned to QA. A failed gate is never provisioned.Dataset requestmembers + claims · masked · QAleased by your agentYour networkProduction1Discoversensitive fields2Subsetkeys intact3Maskor synthesizeCertifyQAcertified datasetfailed gate: never provisioned

Capabilities

Discovery & classification

The agent reads schema metadata and profiles columns locally, then reports which columns look sensitive — names and classes only, never sample values.

Learn more about Discovery & classification

Subsetting

Entity-driven subsets with referential closure, date windows and filters, so a few thousand members bring their claims, or a few hundred customers bring their accounts.

Learn more about Subsetting

Masking & pseudonymization

Versioned masking policies with deterministic, keyed transformations so the same input masks the same way in every system. Keys stay in your secret store.

Learn more about Masking & pseudonymization

Synthetic generation

Generate records from pack templates and scenarios when you need edge cases production does not have, or when no source access is appropriate.

Learn more about Synthetic generation

Certification

Automated gates for coverage, masking, referential integrity, schema, quality and provenance. Masked is not the same as certified — failed datasets are never provisioned.

Learn more about Certification

Governance & audit

Role-based access, approvals with separation of duties, and an append-only, hash-chained audit trail. Evidence stays in your environment; we keep references.

Learn more about Governance & audit

APIs & CLI

Everything in the console is available through a versioned REST API and the datanivra CLI, so datasets can be requested from CI/CD pipelines.

Read the docs about APIs & CLI

From request to certified dataset

The DataNivra pipeline, end to endAll eight stages run inside your environment. Preparation: discover, classify, subset, mask. Proof and delivery: synthesize, validate, certify, provision. Only status, counts and evidence references are reported to the control plane.Prepare · Your environmentDiscoverClassifySubsetMaskProve & deliver · Your environmentSynthesizeValidateCertifyProvisionSame job, same environment
The DataNivra pipeline, end to end. All eight stages run inside your environment. Preparation: discover, classify, subset, mask. Proof and delivery: synthesize, validate, certify, provision. Only status, counts and evidence references are reported to the control plane.
Text description
  1. Prepare (Your environment): Discover → Classify → Subset → Mask

    Connection: Same job, same environment

  2. Prove & deliver (Your environment): Synthesize → Validate → Certify → Provision