Engineering problem

Self-Hosted Security Cameras and Frigate Recording

Pilot a private NVR on your own cameras using representative footage, short retention and a measured storage and recovery budget.

Editorial update

Decision in brief

Pilot a local NVR such as Frigate when you control your cameras, can use local streams and want to administer footage and access yourself. Start with a single camera in an area you control with everyone informed. Keep a simpler recorder if the only requirement is a brief local history and richer detection creates work without improving your test outcomes.

Pilot one camera: Use your own area. Inform everyone. Test local playback.
Compare a local recorder with an NVR on a camera and area you control. Review who can see or retain the footage.

Decide what footage you need before buying hardware

Frigate can record a compatible camera stream locally and supports different policies for continuous, motion and event retention. A smaller detect stream can reduce decoding work when the camera offers separate streams. For continuous recording, a steady 4 Mbps stream implies roughly 43 GB per 24 hours before extra storage and variation. Measure your own camera over a full day before scaling.

Point cameras only at the area you intend to record, review what is actually visible, and leave audio disabled when it serves no purpose. Isolate camera access and keep playback available only to designated accounts. Check deletion for both normal recordings and manually exported clips, which Frigate stores separately from its recording retention.

NeedStart withAcceptance evidence
Short history for your own equipmentOne local stream and explicitly configured recording retentionTen staged events play back with usable timestamps and the constrained window deletes old footage.
Event alerts with storage constraintsA small set of planned test events and monitored event-only recordingMeasure missed events and irrelevant alerts before reducing continuous retention.
Remote review by one authorized household memberPrivate access path to the recorder with a dedicated accountPlayback succeeds for the approved account and fails through the unapproved path.
Sensitive surroundings or poorly scoped fields of viewReposition the camera or omit the locationThe recorded view covers only the agreed area before activation.

What two HN builders wanted from a recorder

spupuz announced VibeNVR as a locally run recorder with an API and a Homepage widget. If one screen will display recorder status, trial a simple uptime indicator before giving the dashboard any access to footage.

bolt012 described using Frigate for their own pets and wanting verifiable context in place of a flood of motion alerts. Choose a few useful event types and score alerts against staged scenes before paying the compute and maintenance cost of extra processing.

Run a one-camera private pilot

  1. Mount one owned camera facing a controlled test area and confirm who knows about the recording. Specify a 24-hour sample window, authorized viewer, deletion schedule and disk limit.
  2. Record ten planned scenes with an informed participant or a test object. Measure playback success on your device, false alerts, disk growth and CPU use.
  3. Check that approved local playback still works during a planned WAN outage. Restore configuration to a spare host and verify that a test clip and its timestamps are usable. Let the retention window expire and check that exports follow a separate deletion procedure.
  4. Proceed if all required scenes are recoverable, no excluded area appears, only the approved viewer can play footage and usage stays within budget. Stop if you cannot narrow the field of view or reliably enforce access and deletion.

Related articles