How-To

Build a Local NVR on Ugreen NASync with Frigate

Q: Can I run Frigate on Ugreen NASync without wiping UGOS?

Yes for many DXP models: install Docker from UGOS App Center, map /dev/dri for Intel QSV, and run the official Frigate container. You trade hypervisor flexibility for faster rollback to stock firmware.

Q: Does Ugreen NASync support Intel Quick Sync for Frigate?

NASync DXP and iDX models use Intel x86 CPUs with integrated graphics suitable for Frigate preset-intel-qsv-h264 or h265 when /dev/dri is passed into Docker and the iHD driver stack is installed per Frigate docs.

Q: Is a Google Coral TPU required on NASync?

Not strictly—CPU detection works for two to three 1080p streams. For six or more cameras at five fps detect, add Coral USB or plan Hailo-8 per our accelerator benchmark guide.

Q: Proxmox or bare Debian on Ugreen hardware?

Choose Proxmox when you will colocate Home Assistant, Pi-hole, or a second VM on the same box. Choose bare Debian or Ubuntu when you want the thinnest stack dedicated to Frigate plus file storage.

Q: Will wiping UGOS break the Ugreen mobile app?

The stock app expects UGOS. After flashing Proxmox or Debian you manage the machine via SSH and the Frigate web UI—not the Ugreen consumer app—unless you restore factory images from vendor recovery media.

Q: How much storage do eight 1080p cameras need locally?

At roughly 80–120 GB per camera per month for continuous 1080p record (codec and retention dependent), plan eight to ten terabytes usable in RAID for a thirty-day window—see the retention table in this guide.

Ugreen Frigate NVR on NASync: flash Debian or Proxmox, pass through Intel QSV for decode, add a Coral TPU, and keep recordings offline—hardware guide 2026.

Privacy Smart Home Research Desk May 23, 2026

Keywords: ugreen frigate nvr, Ugreen NASync Frigate, Intel QSV Frigate, Proxmox Ugreen NAS, Coral TPU NVR, local NVR without cloud

An ugreen frigate nvr build means treating Ugreen NASync x86 hardware as a local-only video appliance: wipe or sidestep the cloud-oriented UGOS stack, run Frigate under Docker (on UGOS, Debian, or Proxmox), pass Intel Quick Sync (QSV) for camera decode, and attach a Google Coral TPU (or Hailo) so object detection never leaves your LAN. As of May 2026, that path is the standard privacy upgrade for buyers who want Ring-class alerts without Ring-class cloud retention.

Quick answer: How do you build a local Frigate NVR on Ugreen NASync?

Install Frigate in Docker with Intel QSV decode (/dev/dri) and a Coral TPU for detection. Either stay on UGOS Docker or replace UGOS with Proxmox/Debian on the factory SSD, then isolate cameras on an IoT VLAN with no WAN egress.

Source: Frigate hardware acceleration docs

Executive summary

Ugreen NASync boxes are standard x86 mini-servers with Intel iGPUs, multiple drive bays, and dual 2.5/10 GbE—attractive shells for a self-hosted NVR once you accept you are maintaining Linux, not a sealed appliance. UGOS Pro (Debian 12 underneath, per vendor and community teardowns through 2025–2026) ships Docker and a QEMU VM manager, so you can run Frigate without re-flashing—but homelabbers increasingly replace UGOS with Proxmox VE to colocate Home Assistant, Pi-hole, and ZFS or mergerfs storage on one power draw¹².

This guide is hardware-first: boot paths, QSV passthrough, Coral USB/PCIe, retention math, and a citable model matrix we compiled from Ugreen published specs and Frigate’s Intel acceleration table (accessed 23 May 2026)³⁴. For software comparisons (Ring vs Frigate, ONVIF ingress), cross-read Frigate vs Ring vs Arlo and ONVIF vs RTSP. For staying on stock UGOS with Home Assistant, see UGreen NASync private NVR overview.

Verdict: Elena (four Reolink PoE cams, wants rollback) should stay on UGOS + Docker + QSV + Coral USB. James (eight cams, Proxmox homelab, VLAN segmentation) should flash Proxmox, run Frigate in a privileged LXC with /dev/dri and USB passthrough, and keep recordings on a separate BTRFS/ZFS pool—not the tiny OS SSD.

Methodology: how the NASync × Frigate matrix was built

We scored seven publicly listed NASync / iDX SKUs (Ugreen product pages and press specs, May 2026) against Frigate workload needs:

QSV generation class — mapped CPU families to Frigate’s Intel preset table (gen8–12 → preset-intel-qsv-* with iHD; gen13+ / Core Ultra → QSV presets with iHD/Xe)⁴.
Sustained camera count — editorial estimate: N-series / 4-core hosts for ≤6×1080p detect @5 fps with QSV + one Coral; Core Ultra / 8+ cores for 8–12 streams when masks are tuned.
Flash risk — Low = UGOS Docker only; High = full OS replace with BIOS watchdog considerations⁵.
Street price (USD) — Ugreen MSRP and Amazon snapshots 23 May 2026 (rounded; regional VAT excluded).

Where I’m less sure — exact /dev/dri/renderD* numbering on every DXP board revision without a unit on the bench; always run vainfo and Frigate’s /api/config health after driver updates.

Anecdotally, DXP4800 Plus owners report smoother QSV in Docker on stock UGOS than early UGOS 1.0.x builds, but kernel bumps still require re-checking device nodes after updates.

Original research: NASync hardware suitability for Frigate (May 2026)

Model (2026 lineup)	CPU class	QSV / decode tier	Est. 1080p cams (QSV + 1× Coral)	Drive bays	10 GbE	OS flash risk	MSRP USD (May 2026)	Frigate fit score /10
DXP2800	Intel 12th Gen N100/N200	gen12 iHD	4–6	2	No (2.5G)	Low (UGOS Docker)	~$280–350	7
DXP4800	N100 / i3-N305	gen12 iHD	6	4	Optional	Low–Med	~$450–550	8
DXP4800 Plus	N305 + 10GbE	gen12 iHD	6–8	4	Yes	Low–Med	~$550–650	9
DXP6800 Pro	Core i5 (12th/13th mobile)	gen12–13 iHD	8–10	6	Yes	Med	~$900–1,100	9
iDX6011 / Pro AI	Core Ultra 7 255H	gen13+ QSV	10–12	6+	Dual 10G	Med–High	~$1,400–1,800	10
DH2300 (ARM)	Rockchip	No Intel QSV	CPU-only / external	2	No	Low	~$200	3 for Frigate
DIY mini-PC (ref.)	N100 barebone	gen12 iHD	6	1× M.2	Optional	High (bare)	~$180–250	8 value

Privacy note: Score reflects local decode + local inference potential—not UGOS phone-home behavior. You still must block camera WAN and disable UGOS telemetry where the vendor exposes toggles.

Stat: Frigate documents gen8–gen12 Intel iGPUs with preset-intel-qsv-h264 / h265 when the iHD stack sees the GPU—exactly the class in most NASync DXP Intel SKUs.
— Frigate video decoding docs, accessed 23 May 2026

Dataset (JSON-LD)

Choose your boot strategy before you buy drives

Three paths dominate May 2026 community reports and vendor architecture:

Path	You keep	Frigate runs in	QSV passthrough	Coral passthrough	Rollback to UGOS
A — UGOS Docker	UGOS + App Center	Docker on host	Map `/dev/dri`	USB preferred	Factory reset
B — UGOS VM	UGOS hypervisor	QEMU VM (UEFI)	vGPU/passthrough varies	USB to VM	Delete VM
C — Proxmox / Debian	Replace OS SSD	Proxmox LXC/VM or bare Docker	LXC bind-mount `renderD128`	USB or PCIe to LXC	Vendor recovery USB⁵

Quick Sync Video (QSV) is Intel’s fixed-function decode block. Frigate uses it so your CPU is free for motion masks and Coral inference, not H.264 bitstream parsing⁴.

Path A — UGOS Docker — pros

Fastest time-to-recording; no bootloader surgery.
UGOS RAID UI still manages disks.
Official Ugreen app remains for volume health (not Frigate).

Path A — cons

UGOS updates may reset Docker bind mounts.
Limited VM networking vs Proxmox.
Community distrust of closed backup/telemetry policies.

Path C — Proxmox — pros

Snapshot Frigate LXC before kernel bumps.
Colocate Home Assistant VM on same iron.
Standard /dev/dri + USB passthrough docs⁶.

Path C — cons

BIOS watchdog may block custom boot until disabled⁵.
OS SSD too small for recordings—must map HDD pool.
You own ZFS/BTRFS tuning and backups.

Taken position: Path A for first-time Frigate on NASync; Path C only when you already run Proxmox elsewhere and treat the Ugreen box as replaceable homelab hardware—not a warranty-friendly appliance.

Steel-man: why keeping UGOS is rational

The strongest case against wiping UGOS is operational risk adjusted for storage:

UGOS ships a GUI-managed RAID, SMART alerting, and thermal profiles tuned for the chassis. Community installers who flash Proxmox onto the 32–64 GB OS SSD often forget that recordings belong on the HDD pool, then fill the boot device and corrupt the VM disk². UGOS Docker already exposes Debian 12 underneath—power users can apt the Intel media stack and run the official Frigate image without losing the vendor recovery partition. For four cameras or fewer, a Coral USB on UGOS frequently delivers the same privacy outcome as a bare-metal rewrite with one afternoon instead of one weekend of bootloader debugging.

Rebuttal: UGOS is still a moving target—Docker path changes, VM firmware defaults to SeaBIOS (breaking modern cloud images unless you force UEFI)⁷, and you cannot audit what the NAS phones home without packet captures. If your threat model is “no vendor daemon on the NVR VLAN”, Proxmox or Debian on the metal is the consistent answer—even if it costs a Saturday and a USB recovery stick.

Path A — Frigate on stock UGOS (Docker + QSV + Coral)

Working example: Elena, DXP4800 Plus, four PoE cams

Profile: Elena keeps UGOS 1.13+ on a DXP4800 Plus ($599 street, May 2026). Four Reolink RLC-810A cameras on VLAN 30 (no WAN). She wants Frigate + Home Assistant later but needs spouse-approved rollback.

Steps (methodology: UGOS Docker docs + Frigate Docker install, verified against Frigate 0.15 docs 23 May 2026):

App Center → Docker — enable automatic start.
SSH — install Intel VA stack: intel-media-va-driver-non-free (host) per Debian 12 norms; reboot.
Verify QSV — vainfo --display drm --device /dev/dri/renderD128 shows H264/H265 decode.
Compose — mount storage and GPU:

services:
  frigate:
    image: ghcr.io/blakeblackshear/frigate:stable
    privileged: true
    shm_size: "256mb"
    devices:
      - /dev/dri/renderD128:/dev/dri/renderD128
      - /dev/bus/usb:/dev/bus/usb
    volumes:
      - /volume1/frigate/config:/config
      - /volume1/frigate/storage:/media/frigate
      - type: tmpfs
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    ports:
      - "5000:5000"
      - "8554:8554"
      - "8555:8555/tcp"
      - "8555:8555/udp"

config.yml — global FFmpeg + Coral:

mqtt:
  host: 192.168.30.10

detectors:
  coral:
    type: edgetpu
    device: usb

ffmpeg:
  hwaccel_args: preset-intel-qsv-h264

cameras:
  front_door:
    ffmpeg:
      inputs:
        - path: rtsp://192.168.30.101/h264Preview_01_sub
          roles:
            - detect
        - path: rtsp://192.168.30.101/h264Preview_01_main
          roles:
            - record
    detect:
      width: 1280
      height: 720
      fps: 5

Firewall — deny VLAN 30 → WAN; allow NVR → cameras only.

Elena’s verdict: stay on UGOS until Proxmox skills mature; revisit wipe in Q4 2026 if she adds Pi-hole on the same box.

Path C — Flash Proxmox or Debian on NASync

Preconditions (read before USB boot)

Backup every volume; assume UGOS app pairing is lost after wipe.
OS SSD vs HDD pool — install Proxmox to the factory SSD; pass HDDs as data disks only (ZFS or ext4 pool for /media/frigate).
BIOS watchdog — multiple 2025–2026 teardowns note a hardware watchdog that reboots if the boot chain is not UGOS; disabling it is often required for non-vendor OS installs⁵. Document the vendor recovery image location before toggling.
HDMI — community installs use the chassis HDMI port to complete Proxmox first boot².

Proxmox install sketch

Write Proxmox VE 8.4+ ISO to USB (Debian 12 bookworm base as of May 2026).
Boot Ugreen unit → Install Proxmox to SSD; set static IP on mgmt VLAN.
Create privileged LXC (Debian 12 template) — not unprivileged if you need /dev/dri without nested hacks.
On the host, confirm GPU: ls -l /dev/dri/.
In LXC config (/etc/pve/lxc/<id>.conf):

lxc.cgroup2.devices.allow: c 226:0 rwm
lxc.cgroup2.devices.allow: c 226:128 rwm
lxc.mount.entry: /dev/dri/renderD128 dev/dri/renderD128 none bind,optional,create=file
lxc.mount.entry: /dev/bus/usb dev/bus/usb none bind,optional,create=dir

Inside LXC: install Docker, deploy the same Frigate compose as Path A.
Recordings path — bind-mount mp0: /mnt/nvr,mp=/media/frigate to the ZFS dataset on HDDs.

Automated alternatives: community scripts such as RiceMunk/frigate-proxmox-script target Intel N100 mini-PCs but illustrate the LXC + Docker + QSV pattern you can adapt for NASync⁶.

Bare Debian

Choose Debian 12 netinst if you refuse Proxmox overhead. Follow Debian wiki — InstallingDebianOn/Ugreen for community boot notes (access attempted 23 May 2026). Install Coral rules, Docker, intel-media-va-driver-non-free, then Frigate—same compose as above.

Intel QSV tuning on NASync (gen12 vs Core Ultra)

For a QuickSync-only walkthrough (device passthrough, vainfo, and preset matrix), see Configure Intel QuickSync for Frigate on Ugreen NASync. Frigate’s May 2026 Intel table recommends iHD with preset-intel-qsv-h264 for H.264 substreams and preset-intel-qsv-h265 for H.265 main streams⁴. N100/N305 DXP units are gen12; Core Ultra 7 255H iDX units are gen13+—use QSV presets, not legacy i965.

Symptom	Likely cause	Fix
CPU at 100%, GPU idle	`/dev/dri` not in container	Add `devices:` + `privileged: true`
`vainfo` fails	Missing non-free driver	Install `intel-media-va-driver-non-free`
H.265 main stream errors	Wrong preset	Switch to `preset-intel-qsv-h265`
Alder Lake-N quirks	Old i965 default	Set `LIBVA_DRIVER_NAME=iHD` in compose⁸

# Per-camera override example (H.265 main + H.264 sub)
cameras:
  driveway:
    ffmpeg:
      inputs:
        - path: rtsp://192.168.30.102/sub
          hwaccel_args: preset-intel-qsv-h264
          roles: [detect]
        - path: rtsp://192.168.30.102/main
          hwaccel_args: preset-intel-qsv-h265
          roles: [record]

On Alder Lake-N homelab hosts, forcing the iHD driver in Docker fixed “GPU present but unused” Frigate logs—same lesson applies to NASync N-series silicon.
— Roger Frost, Alder Lake-N QSV + Proxmox Frigate notes, Jan 2026

Coral TPU and detector headroom

For ugreen frigate nvr workloads at six to eight cameras, plan one Google Coral USB ($60–80 street, 23 May 2026) before upgrading the NAS chassis. Map device: usb in config.yml; confirm with lsusb | grep -i coral.

Detector	When on NASync	Caveat
Coral USB	Default recommendation	Reserve rear USB port; avoid hubs
Coral M.2	Compact chassis	Needs gasket driver on bare Linux⁹
Hailo-8	New builds	See Hailo vs Coral benchmarks
CPU only	≤3 cams	High false-skip risk under motion

Working example: James, iDX6011 Pro, eight cams, Proxmox

Profile: James wipes UGOS on an iDX6011 Pro (~$1,599 MSRP, May 2026), installs Proxmox 8.4, and runs Frigate in LXC 201 with QSV + dual Coral USB (front porch + backyard glare). Ten TB usable on ZFS, 30-day retention target.

Retention math (declared): Main stream 4 Mbit/s average × 8 cams ≈ 32 Mbit/s ≈ ~350 GB/day raw; with H.265 + motion-only record in Frigate, plan ~100–120 GB/day observed on comparable homelabs—~3.6 TB/month. James allocates 8 TB active + snapshots to cold storage.

James decision: Proxmox + ZFS snapshots weekly; no UGOS; manage via Frigate UI + Grafana; cameras on VLAN 40 with OPNsense egress rules blocking vendor P2P.

Network privacy checklist (non-optional)

Frigate being local does not stop cameras from calling China-region CDNs if you allow WAN.

Checklist

Dedicated IoT VLAN for cameras; no inbound from internet.
Frigate host DNS → local Pi-hole; block vendor telemetry domains.
Disable UPnP on router; no port-forward 5000 to WAN.
Use substream (720p) for detect; 4K main for record only.
MFA on Proxmox/UGOS admin; separate admin VLAN.
Test WAN egress with ntopng or firewall logs after install.

Pair with how to block smart devices from the internet when you need deny-by-default patterns.

Decision flow (UGOS vs flash vs buy mini-PC)

Start: You own Ugreen NASync + PoE cams
  │
  ├─ Need vendor RAID UI + < 6 cams?
  │     └─ YES → Path A UGOS Docker + QSV + Coral USB
  │
  ├─ Already run Proxmox cluster?
  │     └─ YES → Path C LXC; do NOT record to OS SSD
  │
  ├─ ARM DH2300 only?
  │     └─ YES → Do not use Intel QSV; pick x86 DXP or mini-PC
  │
  ├─ Must keep Ugreen mobile app?
  │     └─ YES → Path A only
  │
  └─ Want zero UGOS daemons?
        └─ Path C + VLAN hardening + recovery USB imaged

Hardware workflow diagram for building a local Frigate NVR on Ugreen NASync with Proxmox or Debian, Intel Quick Sync video decode passthrough, and Google Coral TPU object detection without mandatory cloud video storage. — Treat NASync as x86 homelab iron: QSV for decode, Coral for detect, HDD pool for retention.

Verdict

For privacy-first ugreen frigate nvr builds in May 2026, start on UGOS Docker with Intel QSV and a Coral USB unless you already live in Proxmox. Flash Proxmox or Debian when you need VM snapshots, multi-service colocation, or zero vendor OS agents—and only after you imaged vendor recovery media and planned HDD-side storage.

Elena should not wipe on day one. James should not keep UGOS if he runs eight streams and ZFS snapshots matter more than the green mobile app. Either way, local inference + local disks beats cloud NVR subscriptions within 12–18 months on hardware cost alone—detailed in Frigate vs Ring.

FAQ

Frequently Asked Questions

Can I run Frigate on Ugreen NASync without wiping UGOS?

Yes—Docker on UGOS with /dev/dri and Coral USB is the lowest-risk path. Verify QSV after every UGOS update.

Does Ugreen NASync support Intel Quick Sync for Frigate?

Intel-based DXP and iDX models do, using Frigate’s QSV presets and iHD drivers. ARM DH2300 does not.

Is a Google Coral TPU required on NASync?

Not for tiny installs; plan Coral or Hailo for six-plus cameras at five fps detect.

Proxmox or bare Debian on Ugreen hardware?

Proxmox if you want VMs and snapshots; bare Debian if you want minimal services on one box.

Will wiping UGOS break the Ugreen mobile app?

Yes for management—the stock app expects UGOS. Frigate’s UI becomes your control plane.

How much storage do eight 1080p cameras need locally?

Plan roughly 3–4 TB per month for continuous main-stream recording; less with motion-only and H.265.

Primary sources

#	Source	URL
1	Frigate — Video decoding / Intel QSV	https://docs.frigate.video/configuration/hardware_acceleration_video/
2	Frigate — Installation (Docker)	https://docs.frigate.video/frigate/installation
3	Frigate — Recommended hardware (detectors)	https://docs.frigate.video/frigate/hardware
4	UGOS on Debian — community analysis	https://id10t.online/2025/12/23/cybersecurity-architecture-and-threat-landscape-analysis-ugreen-nasync-dxp-series-and-the-emerging-open-nas-ecosystem/
5	How-To Geek — UGOS is Debian; recovery patterns	https://www.howtogeek.com/one-stray-character-killed-my-nas-heres-how-i-brought-it-back-without-reinstalling/
6	XDA — Proxmox on Ugreen NAS hardware	https://www.xda-developers.com/turned-ugreen-nas-opnsense-router-home/
7	JAKSecurity — Ubuntu VM on UGOS (UEFI)	https://github.com/JAKSecurity/ubuntu-on-ugreen-nas
8	Roger Frost — Alder Lake-N QSV + Proxmox Frigate	https://www.rogerfrost.com/alder-lake-n-gpu-proxmox-docker-frigate/
9	RiceMunk — Frigate Proxmox LXC script	https://github.com/RiceMunk/frigate-proxmox-script
10	Privacy Smart Home — Hailo vs Coral	/guides/hailo-8-vs-google-coral-frigate-benchmarks-2026/

Privacy Smart Home — UGreen NASync private NVR overview. /guides/ugreen-nasync-private-nvr-frigate-home-assistant-2026/ ↩
XDA Developers — Proxmox on Ugreen NAS hardware, 2025–2026 community install narrative. https://www.xda-developers.com/turned-ugreen-nas-opnsense-router-home/ ↩ ↩² ↩³
Ugreen NASync product specifications (DXP / iDX lines), accessed 23 May 2026 via vendor listings. ↩
Frigate — Intel-based CPUs hardware acceleration, accessed 23 May 2026. https://docs.frigate.video/configuration/hardware_acceleration_video/ ↩ ↩² ↩³ ↩⁴
ID 10 T — UGREEN NASync DXP bootloader/watchdog analysis, Dec 2025. https://id10t.online/2025/12/23/cybersecurity-architecture-and-threat-landscape-analysis-ugreen-nasync-dxp-series-and-the-emerging-open-nas-ecosystem/ ↩ ↩² ↩³ ↩⁴
RiceMunk/frigate-proxmox-script — Proxmox LXC Frigate automation. https://github.com/RiceMunk/frigate-proxmox-script ↩ ↩²
JAKSecurity/ubuntu-on-ugreen-nas — UGOS VM UEFI vs BIOS for cloud images. https://github.com/JAKSecurity/ubuntu-on-ugreen-nas ↩
Roger Frost — iHD driver note for Alder Lake-N Frigate Docker. https://www.rogerfrost.com/alder-lake-n-gpu-proxmox-docker-frigate/ ↩
gasket-builder — Coral M.2 on Linux. https://github.com/jnicolson/gasket-builder ↩

Quick answer: How do you build a local Frigate NVR on Ugreen NASync?

Executive summary

Methodology: how the NASync × Frigate matrix was built

Original research: NASync hardware suitability for Frigate (May 2026)

Dataset (JSON-LD)

Choose your boot strategy before you buy drives

Steel-man: why keeping UGOS is rational

Path A — Frigate on stock UGOS (Docker + QSV + Coral)

Working example: Elena, DXP4800 Plus, four PoE cams

Path C — Flash Proxmox or Debian on NASync

Preconditions (read before USB boot)

Proxmox install sketch

Bare Debian

Intel QSV tuning on NASync (gen12 vs Core Ultra)

Coral TPU and detector headroom

Working example: James, iDX6011 Pro, eight cams, Proxmox

Network privacy checklist (non-optional)

Checklist

Decision flow (UGOS vs flash vs buy mini-PC)

Verdict

FAQ

Frequently Asked Questions

Primary sources

Footnotes

Related guides