Open-source notification bridge for Frigate NVR, honestly reviewed. No marketing fluff — just what you get when you want your security camera to actually tell you something.

TL;DR

What it is: A lightweight MIT-licensed sidecar app that reads events from Frigate NVR and pushes rich notifications (snapshots, clips) to Discord, Telegram, Ntfy, Signal, and a dozen other platforms — standalone, no Home Assistant required [README].
Who it’s for: Self-hosters running Frigate NVR who want immediate, reliable push alerts without wiring up Home Assistant automations or paying for a cloud camera subscription. Technically comfortable users who run Docker and are comfortable editing YAML.
Cost savings: Ring/Nest subscriptions run $3–10/mo per camera (Ring Protect Plus is $10/mo for unlimited cameras) for cloud-stored clips and notifications. Frigate + Frigate-Notify on a $6/mo VPS or local NAS gives you the same notifications with local storage and no monthly ceiling.
Key strength: It does exactly one thing — gets Frigate’s event data to your phone or team chat — and does it without coupling your camera system to Home Assistant [5][README].
Key weakness: 343 GitHub stars (small project, one maintainer), minimal third-party documentation, and essentially zero public reviews. If the maintainer stops updating it, you’re on your own.

What is Frigate-Notify

Frigate-Notify is not Frigate. That distinction matters.

Frigate is the main event: an open-source NVR (network video recorder) with local AI object detection — person, car, dog — built for self-hosters who want the features of a Nest or Arlo system without the cloud subscription [1][3]. Frigate handles the cameras, the recording, the AI inference. It does not, out of the box, push a notification to your phone when someone walks up your driveway.

That gap is what Frigate-Notify fills. It connects to your Frigate instance (via MQTT or the Frigate API directly), watches for detection events, and forwards them — with snapshots and metadata — to whatever messaging platform you use. The README describes it as “a simple app designed to send notifications from Frigate NVR to your favorite platforms” and explicitly notes it’s intended for standalone Frigate setups where Home Assistant is not in the picture [README].

The project sits at 343 GitHub stars under the handle 0x2142. It is MIT licensed, deployed via Docker, configured through a single YAML file, and has no commercial entity behind it — just a developer who built the tool they needed and shared it [README].

Why People Choose It

The core friction it solves is real. Frigate by itself generates events but doesn’t have a built-in opinionated notification system. The standard workaround is Home Assistant — you set up the Frigate HA integration, then write automations that trigger on detection events and send notifications. This works, but it adds a significant dependency: now your camera alerts require HA to be running, correctly configured, and free of automation bugs.

One French home automation forum thread illustrates the problem directly [5]. A user running Frigate on a NAS, with HA on a Raspberry Pi, wanted rich Telegram messages (snapshot + video link) on person detection. After hours of debugging a popular Frigate Blueprint that didn’t work, they asked for alternatives. Another user replied with a single line: “De mon côté, je le fais via Frigate-Notify” — “I do it through Frigate-Notify” — linking to the GitHub repo. The follow-up question was “Is this a solution outside of HA?” and the answer was “Yes. It all happens via MQTT” [5].

That’s the actual use case in a nutshell: people who want notifications without the HA dependency, or who find HA automations fragile and want a purpose-built tool that just watches Frigate events and sends messages.

The Chinese NAS communities [1][2][3] covering Frigate NVR in depth don’t mention Frigate-Notify directly — their notification setups route through Home Assistant or MQTT directly. That itself is telling: Frigate-Notify has a small, English-focused user base, largely invisible outside GitHub and a few Western home automation forums.

Features

From the README, Frigate-Notify supports:

Event polling (how it reads from Frigate):

MQTT — receives events in real-time as Frigate publishes them to the broker. Preferred and lower latency [README].
Direct Frigate API polling — for installs without an MQTT broker. Works but adds polling overhead [README].

Notification destinations:

Discord
Gotify
Matrix
Mattermost
Ntfy
Pushover
Signal
SMTP (email)
Telegram
Generic Webhooks
Any platform supported by Apprise API — which covers 80+ services including Slack, PagerDuty, Rocket.Chat, and more [README].

Other:

Aliveness monitor via HTTP GET endpoint. You can point a tool like Healthchecks.io or Uptime Kuma at it to know if Frigate-Notify is still running [README].

What it sends: When a detection event fires, Frigate-Notify can include the snapshot image from Frigate and metadata about the detection (camera name, detected label, time). The exact payload depends on the notification destination.

What it doesn’t do: It doesn’t replace Frigate’s detection, doesn’t do its own AI inference, doesn’t record video, doesn’t provide a web UI. It’s a pipe, not a platform.

Pricing: SaaS vs Self-Hosted Math

Frigate-Notify itself costs $0. MIT licensed, no tiers, no usage limits [README].

The relevant comparison is the full self-hosted camera stack versus commercial alternatives:

Commercial cloud camera subscriptions:

Ring Protect Basic: $4.99/mo per camera (cloud storage + notifications)
Ring Protect Plus: $10/mo for unlimited cameras on one location
Google Nest Aware: $6/mo per camera or $12/mo for home plan
Arlo Secure: $4.99–$12.99/mo depending on cameras

Self-hosted equivalent:

Frigate NVR: $0 (open source)
Frigate-Notify: $0 (MIT)
VPS or local hardware to run them: $0 if already have a NAS, or $6–15/mo on a Hetzner or Contabo VPS

Annual math for a 4-camera home:

Ring Protect Plus: $120/yr (unlimited cameras, one location)
Nest Aware Plus: $120/yr (6h event history) to $288/yr (60-day history)
Self-hosted Frigate + Frigate-Notify on existing NAS: $0/yr ongoing after setup

The wrinkle is hardware. Frigate’s AI detection is CPU and sometimes GPU intensive — the Chinese NAS community benchmarks show that a 4-core Intel N100 running OpenVino inference handles about 8-10 cameras before hitting ceiling [3]. If you don’t already have hardware that can run Frigate, buying a capable mini-PC adds $150–300 to your upfront cost. Over 2-3 years, you still come out ahead versus Ring or Nest subscriptions at scale.

Frigate-Notify adds zero hardware cost to this equation. It runs in the same Docker environment as Frigate and uses negligible resources.

Deployment Reality Check

Frigate-Notify is Docker-first. The install path is pulling the container image from GitHub Container Registry, mounting a config directory, and passing a YAML config file. The documentation site (https://frigate-notify.0x2142.com) covers install and config options, though the website itself just redirects to its docs — there is no marketing homepage [website scrape].

What you actually need:

A running Frigate NVR instance (which itself requires Docker, hardware for AI inference, and camera RTSP streams set up — that’s the harder dependency)
An MQTT broker (Mosquitto, for example) if you want real-time event polling — or you can skip it and use API polling
Docker on the same host or a reachable host
API credentials or connection details for your chosen notification platform (Telegram bot token, Discord webhook URL, etc.)
A YAML config file copied from the example provided in the repo

What can go sideways:

The project has one maintainer. If they stop pushing updates, you’re maintaining a fork or switching tools. There’s no company behind this.
MQTT setup adds another service to keep running. If your broker goes down, Frigate-Notify goes silent — no events fire. The aliveness monitor endpoint exists precisely for this reason, but you have to set up Healthchecks.io or similar to use it [README].
The website and docs are minimal. If you hit an edge case not covered in the config documentation, you’re reading source code or filing a GitHub issue.
There are no public Trustpilot reviews, no G2 ratings, no meaningful review corpus. This article is working from one forum mention [5] and the README. For a small utility tool that’s normal — it’s not a product people write hot takes about — but it means you’re buying on trust.

Realistic setup time for someone who already has Frigate running: 15–30 minutes to get a working config. The harder work is already done if Frigate is up.

Pros and Cons

Pros

Does one thing, does it well. Exactly scoped to the problem: read Frigate events, push to messaging platforms. No scope creep, no UI to maintain [README].
MIT licensed. Fork it, modify it, embed it. No license compliance headaches [README].
Wide notification coverage. Between the native integrations and Apprise API support, you can reach essentially any modern messaging platform [README].
No Home Assistant dependency. For people who don’t run HA, or who want camera notifications to work even when HA is down, this is the right architectural choice [5][README].
MQTT-first. Real-time event delivery without polling overhead when an MQTT broker is in the stack [README].
Aliveness monitoring. The built-in HTTP healthcheck endpoint is a thoughtful addition — it means you can know if notifications silently stopped working [README].
Zero cost. No tiers, no usage caps, no phone-home telemetry.

Cons

343 stars, one maintainer. This is a bus-factor-one project. It’s not a community; it’s a tool someone wrote and shared. Long-term maintenance is an unknown [README].
Minimal ecosystem and documentation. The official docs are functional but thin. Third-party tutorials are almost nonexistent in English. If something breaks in an unusual way, you’re largely on your own.
MQTT adds complexity. The recommended polling method requires a separate broker. Newcomers who’ve never run Mosquitto will need to learn it [README][5].
No web UI. Config is YAML-only. Changes require editing a file and restarting the container. Fine for technical users, a barrier for everyone else.
Not a drop-in for non-technical founders. The profile on this site says Frigate-Notify targets a self-hosted audience. It’s genuinely for people comfortable in a terminal. If you need a ClickOps setup, this isn’t it.
Zero reviews to validate reliability. We can’t say “X% of users report false negatives” or “the Telegram integration is flaky” because the public review corpus doesn’t exist for this tool. You’re going in with limited data.

Who Should Use This / Who Shouldn’t

Use Frigate-Notify if:

You already run Frigate NVR and you’re tired of cobbling together Home Assistant automations to get notifications.
You want Telegram, Discord, or Ntfy alerts with snapshots from your cameras and you don’t need a polished setup wizard.
You run a headless server and are comfortable editing YAML and restarting Docker containers.
You specifically want to keep your camera notification system independent of Home Assistant so it survives HA downtime.

Skip it if:

You don’t already run Frigate NVR. Frigate-Notify is a companion to Frigate, not an independent product. If you’re shopping for a camera system, start with evaluating Frigate first [1][3].
You need push notifications to a phone without any server setup. In that case, a managed service like Ntfy.sh’s hosted tier or Home Assistant Cloud is less friction.
You’re a non-technical founder who needs a working camera notification system but can’t maintain a Docker stack. Buy a Ring subscription and spend the time on your business.
You need guaranteed support SLAs. There are none here.

Alternatives Worth Considering

For Frigate notifications without this tool:

Home Assistant + Frigate integration — the dominant approach in the self-hosted community [2][3][5]. Richer automation logic (conditional alerts, time-of-day rules, cross-device triggers) but couples your camera alerts to HA uptime.
Custom MQTT consumer — write your own small script that subscribes to Frigate’s MQTT topics and calls a notification API. More work upfront, total control.
Frigate’s native webhooks (if/when added) — Frigate’s roadmap includes more native notification options as the project matures [3].

For the whole camera stack:

Frigate NVR — the foundation Frigate-Notify is built for. If you’re not running Frigate, look here first [1][2][3].
Scrypted — a newer home video platform with better HomeKit integration if you’re in the Apple ecosystem.
Shinobi — older open-source NVR, more mature web UI, less AI-native than Frigate.
Ring / Nest / Arlo — if self-hosting the camera stack is not the goal, managed cloud NVRs with mobile apps and professional monitoring exist and cost $5–15/mo.

Bottom Line

Frigate-Notify solves a real and specific problem: getting Frigate NVR events to your phone or team chat without writing Home Assistant automations. It does this cleanly, for free, under the MIT license, with a sensible set of notification targets. If you’re already running Frigate and frustrated by the notification gap, it’s worth a 20-minute test deployment.

The honest caveat is the project’s scale. At 343 stars and one maintainer, this isn’t a tool backed by a company or a large open-source community — it’s a utility that someone built and you’re welcome to use. For a home surveillance notification relay, that’s probably fine. For a business-critical alerting pipeline, you’d want something with more maintainership behind it. Within its intended scope — self-hosted homelab, technically capable operator, Frigate already running — it’s exactly what it needs to be.

Sources

阿皮啊 — “让NAS变身监控录像机！Docker部署人工智能监控方案frigate” — zhihu.com. https://www.zhihu.com/tardis/zm/art/815850428
guitengyue — “Frigate + Qwen3-VL + MQTT + Home Assistant 从零搭建完整手册” — bbs.hassbian.com. https://bbs.hassbian.com/thread-31663-1-1.html
gasment — “【更新0.16.1正式版】万字经验，一文带你入门frigate AI监控” — bbs.hassbian.com. https://bbs.hassbian.com/forum.php?mod=viewthread&action=printable&tid=29310
gasment — “frigate 0.17 beta 版新增了一个非常实用的AI分类功能” — bbs.hassbian.com. https://bbs.hassbian.com/thread-30931-1-1.html
mattx38 / jyvern — “Frigate - Message Telegram riche (snapshot + vidéo)” — forum.hacf.fr. https://forum.hacf.fr/t/frigate-message-telegram-riche-snapshot-video/74639