Deployment

NVR is one small static binary — pick the packaging that fits your box. All variants run the same daemon and the same config.yaml.

Docker#

The image ships the daemon plus ffmpeg and nothing else. It exposes port 8085 and uses three volumes:

services:
  nvrd:
    image: ghcr.io/nvr/nvrd
    restart: unless-stopped
    ports:
      - "8085:8085"
    volumes:
      - ./config.yaml:/etc/nvrd/config.yaml:ro
      - /srv/nvr/recordings:/recordings
      - nvrd-state:/var/lib/nvrd

volumes:
  nvrd-state:

The container runs as an unprivileged nvr user — make sure the recordings mount is writable by it.

NAS and Proxmox#

Both are the Docker path above:

• NAS (Synology, TrueNAS, …) — run the container, bind-mount a recordings folder from your storage pool.
• Proxmox — an LXC or small VM with the container, or the plain Linux binary below. Give the recordings volume its own disk and pass it through.

Windows runs via Docker Desktop with the same image — there’s no native Windows build by design.

Linux, bare metal#

Download the static binary for your arch, put a config.yaml next to it, and run it under your service manager (systemd, OpenRC, …). No runtime dependencies — the binary is fully static; ffmpeg is only needed if you use the H.264 compatibility transcode.

./nvrd -config config.yaml
# UI: http://localhost:8085

macOS#

The signed .dmg from the download page installs NVR.app, which manages the daemon for you — it starts at login, keeps a menu-bar status item, and self-updates. Config lives in the app’s own location; edit it from Settings → Configuration in the web UI.

Updates#

Every build checks a signed manifest and shows an update notice in Settings — never auto-installs over you (the macOS app updates itself through Sparkle). Docker deployments update by pulling the new image tag and recreating the container. Updates are free forever, licensed or not.