For Home Assistant and Frigate

Keep Frigate. Add proof.

SecuraCV is the verified witness log for Frigate and Home Assistant. Frigate keeps the video; SecuraCV keeps the proof. Each person, car, dog or cat event Frigate reports is sealed into a signed, hash-chained log as a coarse claim — which camera, which ten-minute window, what kind of thing — and never a face, a plate, a name or a frame.

Each button opens your own Home Assistant with the repository filled in; you approve every step. All three ways in ↓

$0 · it adds to the stack you already run No account · no telemetry · no subscription planned Honest by construction — every step here is read from the project’s own setup guide

What changes in your dashboard

One new device, named SecuraCV, and one line at the top of its dashboard that tells you whether the record is intact — in words, not a color.

Chain verified ✓ 12 min ago · 1,204 entries · key pinned
  • Verifying… — a check is running
  • Not verified yet — sealed, no check has covered it
  • Verification failed at entry #1,190 — and where
  • Witness key changed — confirm it in Settings → Repairs

The status line in its own words, with example numbers — text quoted from the integration, not a screenshot. Below it the dashboard builds itself from your cameras: Today, Cameras, Last 24 hours, Health.

A witness event for every camera

Each camera gets one event entity, named after it. It fires once per sealed claim and carries the verdict, so an automation can trigger on what was sealed instead of on raw detections.

A notification with the proof attached

Frigate raises an alert; the automation waits for the seal, then sends one push with Open Frigate and Export evidence on it.

Front door · Person — 14:03 · Sealed ✓ into the witness log (entry #1,204, window 14:00–14:10)

A morning digest that always sends

A quiet night still gets a line — with the state of the chain on it — so silence means a quiet night and not a stalled pipeline.

7 events: front door 4, driveway 3 · morning 2, evening 5 · chain verified ✓ at 03:00 · 1,204 entries.

One tap to a pack someone else can check

Export evidence writes a single zip: the signed bundle, your witness key’s fingerprint, a plain-language statement of what the record shows and what it does not, and the checker itself — one HTML file that works offline. Whoever receives it installs nothing and needs no account.

Think of Frigate as the camera roll and SecuraCV as the notebook beside it: a short, signed line for each thing that happened, written so that tearing out or rewriting a page shows.

Sealed first. Verified when your own Home Assistant has checked.

“Verified” is a reserved word here: an Ed25519 signature checked against a pinned key, nothing looser. So an event earns its badges in order, and the kernel vouching for itself never counts.

Sealed ✓

The witness kernel signed the event into its chain — within a minute of Frigate’s detection. Home Assistant has not walked the chain past it yet.

Verified ✓

The integration fetched the sealed log, recomputed every hash link and checked every signature against the key it pinned when you connected. It runs that walk every 15 minutes, a minute after events go quiet, and whenever you press Verify now.

Failed ⚠

The last walk rejected the chain. Every row reads Failed until a walk passes again, and the dashboard says at which entry. Export then: the entries before the break still check out in the offline viewer.

For makers: what the walk reads, and what a key change does

The walk is GET /api/sealed-log?from_seq=…, incremental from the newest entry it has already checked, and it is the same routine behind the securacv.verify action. Chain state lives in binary_sensor.securacv_chain_valid (on means the chain verified). A key other than the pinned one is never shown as Failed: Settings → Repairs raises The witness kernel’s key changed, shows both fingerprints, and waits for you to compare before it moves the pin. The kernel’s own hourly self-check appears only as an attribute, never as Verified.

Three ways in, one product at the end

Pick the row that matches how you run Home Assistant. All three finish at the same dashboard.

Home Assistant 2026.5.0 or newerHome Assistant OS for the app; Container for the sidecar.
Frigate 0.14 or newerWith MQTT enabled. Frigate reads your RTSP cameras, as it does now.
An MQTT brokerThe one Home Assistant and Frigate already share — Mosquitto on Home Assistant OS.
Home Assistant OS

The SecuraCV app

  1. Add the repository, then install SecuraCV from the App Store.
  2. Start it and open its Web UI. The wizard finds Mosquitto and Frigate, reads Frigate’s cameras and takes the broker’s credentials from the Supervisor. It shows the device signing key once: save it somewhere safe.
  3. Press Install the integration and restart Home Assistant.
  4. Press Configure on the SecuraCV discovered card. The form has no fields.
Add the app repository

What you type: nothing

Home Assistant with HACS

HACS first

  1. Add the integration’s repository to HACS as a custom repository, install SecuraCV, restart.
  2. Settings → Devices & Services → Add Integration → SecuraCV, and keep Automatic.
  3. It finds the app or a sidecar by itself. With neither running yet it sets up for Canary devices alone and connects when a kernel appears.
Add the HACS integration

What you type: nothing with the app, one 6-digit code with a sidecar

Home Assistant Container

The Docker sidecar, beside Frigate

  1. Fetch quickstart.compose.yml, edit the broker’s address and login, and start it. No broker yet? Use the with-broker variant.
  2. Install the integration from HACS, as in the card beside this one.
  3. Run docker exec securacv pair. It prints a 6-digit code and the kernel’s key fingerprint.
  4. The SecuraCV sidecar card in Home Assistant shows the same fingerprint. Compare, then enter the code.

What you type: one 6-digit code, valid ten minutes

Starting from a bare Home Assistant OS? One command installs the whole stack

From the Terminal & SSH app. It installs and starts Mosquitto, Frigate and the SecuraCV app, installs the integration, and places the blueprints and dashboards, narrating each step. Running it again never repeats a finished step.

curl -fsSL https://raw.githubusercontent.com/kmay89/securaCV/main/scripts/install.sh | bash

Two things stay yours afterwards: point Frigate at your cameras’ RTSP addresses, and point any Canaries at the broker.

No Frigate — only Canary devices?

The integration also works over MQTT alone. Each Canary publishes its own signed events and Home Assistant checks every one against that device’s pinned key. Start at the Canary walkthrough, or build a Canary first.

What it will not do, and what is not finished

The limits are part of the product, so they are on the page that asks you to install it.

  • One claim per camera, kind of thing and ten-minute window. Three people at the door inside ten minutes are one claim. The coarsening is the privacy guarantee, not a bug.
  • No identity, anywhere. There is no face, plate, name or clip in any entity, attribute, notification, export or diagnostics dump.
  • Your video stays Frigate’s. SecuraCV records none; how long clips stay is Frigate’s own retention setting. The signed log keeps 7 days by default, and the wizard also offers 30 days or 1 year.
  • The log keeps a window, not an archive. An event older than the window you chose survives only in an evidence pack you exported, so export — and send or save the zip — the day it matters.
  • The sidecar’s API is plain HTTP for now. Its pairing token crosses your LAN unencrypted, so keep port 8799 on your own network and never forward it. The app has no such exposure.
  • HACS lists it as a custom repository, not in the default store yet. The app installs the same integration on a click instead.
  • This is release-candidate software. The Frigate-to-Home-Assistant pipeline is tested end to end in CI; version 1.0 is held until the Canary firmware finishes validation on real boards.
  • Two records, two keys. The kernel’s log covers what Frigate reports. Each Canary keeps its own signed chain, checked against its own pinned key, and is not re-sealed into the kernel’s log.