DADI-OPS v0.1.0 · Prototype and pilot delivery; interface data is illustrative Delivery boundary & compliance →
Delivery & Deployment

On-premise, under your control

DADI-OPS runs on customer-owned servers. Device records, alarms, tickets and audit data stay inside your network. Three paths are supported, plus one hardened HTTPS gateway.

on-premisenon-root containerTLS 1.2 / 1.3SHA-256 packagebackup rotation
01 / Paths

Pick one runtime, then add the gateway

Do not run two operations services on one host: they compete for the port and the state file.

Container

Recommended

Alpine-based, non-root, cap_drop: ALL, read-only root with a single writable data volume and a built-in healthcheck. Role passwords are required variables; compose refuses to start without them.

docker compose -f docker-compose.ops.yml up -d --build

Bare metal + systemd

Auditable

Installed to a dedicated prefix under a dedicated system user with ProtectSystem=strict. First install generates random passwords in a 600-mode env file; re-running upgrades while keeping env and data.

sudo bash scripts/install.sh --systemd --port 8090

HTTPS gateway

Hardened

TLS 1.2/1.3, HSTS, CSP, login rate limit, API rate limit, healthcheck exemption, explicit token forwarding, and 404 fallback for source and data paths.

nginx -t && systemctl reload nginx

Co-located with the upstream: the operations service can share a host with wvp and ZLMediaKit through a combined compose file, or run on a separate reachable host using an API base URL and an explicit cross-origin allowlist.
02 / Prerequisites

Server and network

Software

Linux server; Docker Engine with Compose v2, or Node.js ≥ 18 for bare metal; Nginx for the gateway. Building the upstream on the same host also needs JDK 17 and Maven 3.

Ports

Operations service 8090; upstream HTTP 18978; SIP 8116 tcp/udp; streaming and RTP ranges as configured. Expose only 80/443 publicly; bind application ports to loopback or the private network.

Devices

Cameras and NVRs must support GB28181-2016 and be configured with the SIP server ID, domain, address, port and registration password. Public deployments require a device-reachable public IP for SIP and streaming.

Domain and certificate

Prepare a management domain and certificate. Once HTTPS is enabled, restrict OPS_ALLOWED_ORIGINS to the real front-end origin and verify the application port is not publicly reachable.

03 / Deliverables

What ships with the product

ItemContentVerification
Release packagetar.gz + SHA256SUMS + MANIFEST; runtime state, volumes and .env excludedsha256sum -c SHA256SUMS
Container imageNon-root, read-only root, dropped capabilities, healthcheck, single data volumedocker compose ps
InstallerIdempotent install, random passwords, systemd unit, dedicated usersystemctl status dadi-ops
Backupgzip + SHA256 with retention rotation; still backs up a corrupted source with an alert exit codescripts/backup.sh
Health probeNode fetch, exit code 0/1, usable by systemd, Docker or monitoringscripts/healthcheck.sh --json
Gateway templateTLS, HSTS, CSP, rate limits, token forwarding, source path fallbacknginx -t
Compliance packLicense list, MLPS gaps, personal data requirements, launch checklistDelivered with documentation
04 / Checklist

Before go-live

Identity

Deployed via installer or compose, not demo passwords; per-person accounts or SSO; authentication stays on; viewer cannot write, read audit or export.

Network

HTTPS enabled with a full HTTP redirect; TLS 1.2/1.3 only; HSTS, CSP and content-type protection active; origin allowlist restricted; app port not public; container non-root with all capabilities dropped.

Audit & data

Audit verification passes; daily head anchored to independent read-only storage; six-month retention; disk or volume encryption; scheduled backup with failure alerts; one off-site restore drill completed.

Compliance

Upstream license texts archived; ZLMediaKit marks verified; upstream attribution present in UI and docs; commercial license decided; signage and notice in video-covered areas.

Known pitfalls: the reverse proxy needs underscores_in_headers on to forward the upstream access-token; devices that fail to register usually still point at 127.0.0.1 for SIP or streaming; media hook 401 means the secret differs from the config; login 401 is usually an unconverted password (MD5). Diagnose before attempting playback.

Need a site-specific deployment plan?

Share your server, network topology and device list; we will provide port planning, integration options and acceptance steps.