Log inRequest a demoStart free

Documentation

Getting started

The moving parts of DataNivra, what runs where, and the order in which to set things up.

The two planes

DataNivra has a control plane that we host (console, REST API, metadata store, audit trail) and a data plane that runs inside your network (the agent, the TDM engine and the industry packs). Everything that touches a row runs in the data plane. See Customer-resident architecture for the full picture.

Set-up order

  1. Start free. Sign up in the console with your work email (see Start free). After you verify the address, name your organisation: DataNivra suggests a unique tenant slug, which you can edit before confirming, and creates the organisation, you as its owner and a time-limited free trial in one step. There is nothing to request from us. (Contract customers whose organisation an operator creates with the bootstrap-tenant command get the same result.) Invite administrators under Users & Roles; roles and separation of duties are enforced server-side.
  2. Try the hosted sandbox — a synthetic estate and a sandbox agent that DataNivra runs, so the whole workflow works before you install anything. It opens in the console Playground; until the operator has deployed the sandbox runner, the page says the sandbox is not available yet.
  3. Install an agent inside the network that can reach your sources and target environments. Create a one-time enrollment token in the console, run the generated command, and check the host with datanivra-agent doctor. See Agent installation and Downloads.
  4. Register data sources by secret reference — for example k8s://tdm/reader-credentials or env://TDM_READER_PASSWORD. The credential itself is resolved by the agent and never sent to DataNivra. Only connectors listed as available on Integrations ship today.
  5. Run discovery, review sensitive-field findings, and approve classification and masking policies.
  6. Request a dataset from the console, the REST API or the CLI. It is certified in your network before it can be provisioned.
  7. Upgrade when useful in Billing & Plan, or take the enterprise contract path (Enterprise).

Where to go next

← All documentation