Install agent

Install the DataNivra agent in your environment

The agent is the only DataNivra component that reads your data. It runs inside your network, needs outbound HTTPS only, and opens no inbound port. You install and run it yourself from the signed release files below; the release status above names the current version.

Latest release: 0.4.4 (published 2026-10-15)

Image (pin this digest): ghcr.io/manuelbomi/datanivra-agent@sha256:cfa91b8a257e7a966fa3f5b8694bc41e7a9ce3bbb18e28c81f90689c7bd6c5d0

Download files and checksums for 0.4.4

Before you install

  1. Create an account and organization (see how to start).
  2. In the console, open Install agent to create a one-time enrollment token. It is short-lived and single-use; store it as a file or secret, never in shell history, and never share it.
  3. Allow outbound HTTPS (443) from the agent host to the control plane, your registry and your secret store. No inbound rule is needed.

Install methods

Every method runs the same signed agent image.
MethodDownloadRequirementsRunbook
Docker (one command)datanivra-agent-docker-0.4.4.tar.gzOne Linux host with Docker; outbound HTTPS (443) only.docs/runbooks/deploy-agent-docker.md
Docker Composedatanivra-agent-docker-compose-0.4.4.tar.gzOne Linux host with Docker Compose; outbound HTTPS (443) only.docs/runbooks/deploy-agent-docker.md
Kubernetes (Helm)datanivra-agent-0.4.4.tgzKubernetes >= 1.25 (chart kubeVersion); manifests validated against 1.29.docs/runbooks/deploy-agent-kubernetes.md
Kubernetes without Helm (kustomize)datanivra-agent-kubernetes-generic-0.4.4.tar.gzKubernetes >= 1.25 with kustomize.docs/runbooks/deploy-agent-kubernetes.md
Customer Azure VNet (Terraform)datanivra-agent-azure-customer-vnet-0.4.4.tar.gzYour Azure subscription and VNet; Terraform; Key Vault for secrets.docs/runbooks/deploy-agent-azure.md
Customer AWS VPC (Terraform, ECS Fargate)datanivra-agent-aws-customer-vpc-0.4.4.tar.gzYour AWS account and VPC; Terraform >= 1.6; Secrets Manager for secrets.docs/runbooks/deploy-agent-aws.md

Docker, one command

Put the enrollment token in a tmpfs secrets directory readable only by uid 10001, then start the hardened container (read-only root filesystem, no capabilities, no published port). Nothing but Docker and the public image is needed; the console's Install agent page prints the same command with your control-plane address filled in:

sudo install -d -m 0700 -o 10001 -g 10001 /run/datanivra-secrets
# Paste the one-time enrollment token at the prompt (input is hidden, nothing is saved)
read -rsp 'Enrollment token: ' DATANIVRA_ENROLLMENT_TOKEN && echo
printf %s "$DATANIVRA_ENROLLMENT_TOKEN" | sudo install -m 0600 -o 10001 -g 10001 /dev/stdin /run/datanivra-secrets/enrollment-token
unset DATANIVRA_ENROLLMENT_TOKEN
docker run -d --name datanivra-agent --restart unless-stopped \
  --read-only --tmpfs /tmp --cap-drop ALL --security-opt no-new-privileges:true \
  -e DATANIVRA_AGENT_CONTROL_PLANE_URL=https://<your-control-plane-api> \
  -e DATANIVRA_AGENT_AGENT_NAME=<agent-name> \
  -e DATANIVRA_AGENT_SECRETS_DIR=/etc/datanivra/secrets \
  -e DATANIVRA_AGENT_ENROLLMENT_TOKEN_REF=file://enrollment-token \
  -v /run/datanivra-secrets:/etc/datanivra/secrets:ro \
  -v datanivra-agent-state:/var/lib/datanivra-agent \
  ghcr.io/manuelbomi/datanivra-agent@sha256:cfa91b8a257e7a966fa3f5b8694bc41e7a9ce3bbb18e28c81f90689c7bd6c5d0

Behind a proxy set HTTPS_PROXY / NO_PROXY; with a TLS-inspecting proxy set CA_BUNDLE (Compose and Helm: DATANIVRA_AGENT_CA_BUNDLE).

Windows: the agent is a Linux container. On Windows, use Docker Desktop with the WSL 2 backend and run these commands in a WSL terminal (for example Ubuntu), not in PowerShell or the Command Prompt.

Docker Compose

Download and extract the Compose package, then follow the README.md in its directory (enrollment token file, .env from .env.example, docker compose up -d):

curl -fsSLO https://www.datanivra.com/downloads/agent/0.4.4/datanivra-agent-docker-compose-0.4.4.tar.gz
tar -xzf datanivra-agent-docker-compose-0.4.4.tar.gz
cd datanivra-agent-docker-compose-0.4.4/infra/agent-packages/docker-compose
# Now follow README.md in this directory

Kubernetes (Helm)

helm install datanivra-agent https://www.datanivra.com/downloads/agent/0.4.4/datanivra-agent-0.4.4.tgz \
  --set image.repository=ghcr.io/manuelbomi/datanivra-agent \
  --set image.digest=sha256:cfa91b8a257e7a966fa3f5b8694bc41e7a9ce3bbb18e28c81f90689c7bd6c5d0

The same chart is published as a signed OCI artifact:

helm install datanivra-agent oci://ghcr.io/manuelbomi/charts/datanivra-agent --version 0.4.4 \
  --set image.repository=ghcr.io/manuelbomi/datanivra-agent \
  --set image.digest=sha256:cfa91b8a257e7a966fa3f5b8694bc41e7a9ce3bbb18e28c81f90689c7bd6c5d0

The chart runs a single-replica StatefulSet (one agent identity per volume) and reads secrets as mounted Kubernetes Secrets. The Kubernetes manifests without Helm and the Terraform modules for your own Azure VNet and AWS VPC are in the packages listed above; each package explains its steps in a README.md, and the documentation package holds the runbooks.

Download files

Every file of agent release 0.4.4 except the per-platform SBOM and provenance documents, which are attached to the image instead (see below). Download the files you need, then check them against the signed checksum list before you use them:

Files of agent release 0.4.4, served from this website.
FileSHA-256
datanivra-agent-0.4.4-helm-values.yaml377da7ed3eaf11e544b78022d971c33ef57b3d1b91952d19c929d9dde1fb4358
datanivra-agent-0.4.4.tgz72bc147ee6a688535977a474f3119f632f7bb3ef023e117a9a67a671a56ebbe6
datanivra-agent-aws-customer-vpc-0.4.4.tar.gz15dac94a759d220c78b0c5db16a86ca7769a9f48197d5848ef28641612ebd743
datanivra-agent-azure-customer-vnet-0.4.4.tar.gz671898ae3b4324e6f7b712b30493ce76a74b9a149a94aa796d3ea30a66b9d863
datanivra-agent-docker-0.4.4.tar.gzb753d20a718ce6b17c9cfa8f2f86d7ed18495451edde16646ca78ecbc240de1a
datanivra-agent-docker-compose-0.4.4.tar.gz65e96170b38dcc6487e96042810140d7e7582fe67a71516a289b1ac6764aa6a1
datanivra-agent-docs-0.4.4.tar.gz4eea9f0ae95f8f613a67ce137ebf51cfd0293f4915f72fdab295b69c375d6ea2
datanivra-agent-kubernetes-generic-0.4.4.tar.gzc49a5a9f959c5102a8c6c9335b2a93751f64e6b0895389c8778e618295a3cc03
RELEASE_NOTES.mddab1c6059d612e9cb0b4cf6b37bb6ebb1bbb91b731332b66209b3a10f87cddee
release-manifest.json533dce1e205d31768ae7a5318350166798af266d98273620c9da53dab7b22a94
SHA256SUMSChecksum list (verify it with the bundle below)
SHA256SUMS.cosign.bundleSigstore signature bundle of SHA256SUMS
curl -fsSLO https://www.datanivra.com/downloads/agent/0.4.4/SHA256SUMS
curl -fsSLO https://www.datanivra.com/downloads/agent/0.4.4/SHA256SUMS.cosign.bundle
curl -fsSLO https://www.datanivra.com/downloads/agent/0.4.4/datanivra-agent-docker-compose-0.4.4.tar.gz
cosign verify-blob --bundle SHA256SUMS.cosign.bundle \
  --certificate-identity 'https://github.com/manuelbomi/datanivra-platform/.github/workflows/release-agent.yml@refs/tags/agent-v0.4.4' \
  --certificate-oidc-issuer 'https://token.actions.githubusercontent.com' SHA256SUMS
sha256sum -c --ignore-missing SHA256SUMS

cosign verify-blob proves that SHA256SUMS was signed by the DataNivra release workflow for this version; sha256sum then checks every file you downloaded (--ignore-missing skips the ones you did not).

Supported platforms

Container image platforms built by the release workflow.
PlatformStatusNote
linux/amd64BuiltBuilt, signed and published by the release workflow (agent 0.4.4).
linux/arm64BuiltBuilt, signed and published by the release workflow (agent 0.4.4).

Verify before you run it

Always deploy by digest, never by tag, and verify the keyless Sigstore signature made by the DataNivra release workflow:

cosign verify ghcr.io/manuelbomi/datanivra-agent@sha256:cfa91b8a257e7a966fa3f5b8694bc41e7a9ce3bbb18e28c81f90689c7bd6c5d0 \
  --certificate-identity 'https://github.com/manuelbomi/datanivra-platform/.github/workflows/release-agent.yml@refs/tags/agent-v0.4.4' \
  --certificate-oidc-issuer 'https://token.actions.githubusercontent.com'

The image carries a BuildKit SBOM and provenance attestation. Inspect them with:

docker buildx imagetools inspect ghcr.io/manuelbomi/datanivra-agent@sha256:cfa91b8a257e7a966fa3f5b8694bc41e7a9ce3bbb18e28c81f90689c7bd6c5d0 --format '{{ json .SBOM }}'
docker buildx imagetools inspect ghcr.io/manuelbomi/datanivra-agent@sha256:cfa91b8a257e7a966fa3f5b8694bc41e7a9ce3bbb18e28c81f90689c7bd6c5d0 --format '{{ json .Provenance }}'

The checksums of the release files, including the SBOM and provenance documents, are listed in SHA256SUMS (see Download files).

In Kubernetes, enforce the same identity with an admission policy (for example Sigstore policy-controller or Kyverno image verification).

Build from source

The image is built from agent/runtime/Dockerfile at the repository root. The source repository is private today, so building from source requires repository access from DataNivra:

docker build -f agent/runtime/Dockerfile -t datanivra-agent:local .
docker run --rm \
  -e DATANIVRA_AGENT_CONTROL_PLANE_URL=https://<your-control-plane-api> \
  datanivra-agent:local check

datanivra-agent check validates configuration and prints non-secret settings. See the agent installation guide, the support center if something does not connect, and how to verify the agent's network behaviour yourself.