Frigate vs. Blue Iris vs. UniFi Protect: Which Local Security Camera System Fits Your Home?

If you want security cameras without turning your house into another cloud subscription, three names come up over and over: Frigate, Blue Iris and UniFi Protect.

All three record video locally. All three can add intelligence beyond basic motion detection. All three can sit at the center of a serious home-camera system. But they approach the problem very differently:

Frigate = Build. It gives you the freedom to assemble a local AI camera system around Home Assistant.

Blue Iris = Tune. It’s a mature Windows NVR with deep camera, recording, alert and AI controls.

UniFi Protect = Integrate. It’s a tightly coupled hardware-and-software system that asks you to manage less of the underlying infrastructure yourself.

The useful question isn’t which one wins. It’s which one matches the kind of system you actually want to own and operate.

Frigate vs. Blue Iris vs. UniFi Protect at a Glance

	Frigate	Blue Iris 6	UniFi Protect
Best described as	Local AI NVR	Traditional NVR with built-in local AI	Integrated camera ecosystem
Runs on	Your Linux/Docker hardware, including Unraid and supported Home Assistant setups	A Windows PC	A supported UniFi OS console or NVR
Cameras	Broad support for standard IP-camera streams	Broad support; mixed-brand setups are normal	UniFi-native plus compatible third-party ONVIF cameras with fewer features
Local AI	Object detection plus semantic search, face and license-plate recognition; you choose the hardware	Built-in object classification/tracking, face recognition and ALPR	Local AI on UniFi hardware; advanced AI for some ONVIF cameras may require additional hardware such as AI Port
Home Assistant	Deep integration and central to its design	APIs, MQTT and community integrations	Official integration
Operating model	Build	Tune	Integrate

That table gets surprisingly close to the real decision. Frigate starts with software freedom and automation. Blue Iris starts with NVR control and camera flexibility. UniFi Protect starts with integration and operational simplicity.

Why I Wanted to Compare These Three

This comparison grew directly out of two recent Home Gadget Geeks conversations.

In HGG689, Mike Wieger and I spent a good part of the show on Frigate. Mike has used several camera platforms over the years, including Blue Iris, and Frigate is now his preferred local NVR.

A week later, Gavin Campbell joined me for HGG690. Gavin has also used Frigate and Blue Iris, and his current preference is UniFi Protect.

That’s what makes it interesting. Neither of them is comparing spec sheets. Both have lived with these systems, both are more than capable of running any of them, and they landed in different places.

Their experiences are their own, not a verdict, but they raise a better question than “which has the longest feature list”:

Why would an experienced home-tech user choose one over the others?

The Three Platforms

What Is Frigate?

Frigate is an open-source NVR designed around local computer vision and smart-home integration. It runs on hardware you provide and is commonly deployed through Docker on Linux, Unraid or supported Home Assistant environments.

I covered it in depth in my complete guide to Frigate and Home Assistant, so here’s the short version.

The idea worth carrying into this comparison is that Frigate turns cameras into sensors.

Instead of only recording video, it detects people, cars and other objects, tracks them through zones and exposes that information to the rest of your smart home. For someone already building around Home Assistant, that’s a powerful model.

Frigate gives you control over nearly every layer: cameras, server, storage, decoding hardware, object-detection hardware, recording and detection streams, retention rules, zones, AI enrichments and Home Assistant automations.

Object detection and enrichments such as semantic search, face recognition and license-plate recognition are separate workloads, which is part of why you have so much freedom to reuse equipment you already own.

The tradeoff is that you are operating the infrastructure.

At some point you may need to understand Docker, RTSP, ONVIF, MQTT, hardware pass-through, codecs, storage, networking, detectors and remote access.

Frigate 0.18 made configuration considerably easier through the web interface, and Mike talked about that on HGG689, but this is still software you assemble into your own system.

For some people that’s the attraction. For others it’s exactly what they’re trying to avoid.

What Is Blue Iris?

Blue Iris is mature Windows-based video-surveillance software. Instead of buying a proprietary NVR appliance, you install it on a Windows PC and connect your cameras.

Blue Iris 6 supports up to 128 cameras and works with a broad range of network cameras, which is a big part of why it has been a DIY favorite for years.

Its strength is control.

You can tune recording, cameras, motion, triggers, alerts, schedules, storage, PTZ, users, remote viewing, encoding and AI confirmation.

If you like traditional NVR software where nearly every behavior can be adjusted, Blue Iris gives you a lot to work with.

Blue Iris 6 Changes the AI Conversation

Older comparisons, and plenty of older tutorials, assume Blue Iris needs CodeProject.AI, DeepStack or another external AI server.

That is no longer the whole story.

Blue Iris 6 has built-in AI for object classification and tracking, facial recognition and automatic license-plate recognition.

External AI providers are still an option, but they’re no longer the only path.

That makes today’s comparison closer than it used to be: a traditional NVR and a local-AI-first NVR can now both put serious detection behind your cameras.

The tradeoff is that Blue Iris is still a Windows application.

If you already have a capable Windows machine and are comfortable maintaining it, that fits naturally.

If your homelab revolves around Linux, Docker and Unraid, a Windows NVR can feel like a separate island.

There’s also a philosophical difference: Blue Iris is fundamentally an NVR that can participate in automation, while Frigate was designed so camera intelligence becomes part of the automation system itself.

What Is UniFi Protect?

UniFi Protect isn’t software you install on any spare server.

It runs on supported UniFi OS consoles and NVR hardware, so where Frigate and Blue Iris have you build the host, Protect has you buy into a supported platform.

The advantage is integration.

The console understands the cameras, the cameras understand Protect, and the mobile app understands the NVR.

Firmware management, playback, recording and remote access all come from one ecosystem.

That reduction in friction is a big reason Gavin prefers it.

He’s perfectly capable of running Frigate or Blue Iris; he values that Protect asks less of him.

That’s a legitimate feature, not a consolation prize.

Is UniFi Protect Really Local?

Yes.

Protect stores recordings locally on the UniFi OS console or NVR and doesn’t require a cloud-video subscription for that.

Its supported AI detection and recognition run locally too.

Remote access may use Ubiquiti’s infrastructure to help establish the connection to your local system, but that’s not the same as mandatory cloud video storage.

That’s a very different model from consumer cameras built around paid cloud storage.

Does UniFi Protect Require UniFi Cameras?

Not anymore.

Protect now supports compatible third-party ONVIF cameras, which gives people with existing cameras a real migration path.

Depending on the camera, live view, playback, motion events, PTZ and audio can work.

But third-party cameras don’t automatically get the full native Protect feature set.

Advanced AI such as people, vehicle, face and license-plate detection may require additional UniFi hardware such as the AI Port.

Protect is more open than it used to be, and it’s still the most ecosystem-oriented platform of the three.

How They Compare

Home Assistant

For TheAverageGuy.tv readers, this may be the most important category.

Frigate is deeply aligned with the Home Assistant model.

Its official integration exposes object, zone, recognition and review information, and MQTT is an important part of that setup, though not the whole story.

That makes an automation like this natural:

When a person enters the front porch zone after dark, turn on the porch light and send me a camera notification.

The camera system becomes another set of sensors for the house.

UniFi Protect has an official Home Assistant integration that goes well beyond a camera feed.

It exposes cameras along with related sensors, events, switches and other entities, and event thumbnails and clips are useful in dashboards and notifications.

Choosing Protect does not mean giving up serious Home Assistant automation.

The difference is architectural: Protect remains the camera system, and Home Assistant integrates with it.

With Frigate, camera intelligence sits more directly inside Home Assistant’s automation model.

Blue Iris can participate through APIs, MQTT and community integrations, but Home Assistant isn’t central to its architecture the way it is for Frigate.

That doesn’t make it a weaker NVR. It just starts from a different place.

Camera Choice

Frigate is built around standard IP-camera streams. If camera selection is your next decision, I also have a dedicated guide to the best cameras for Frigate.

RTSP, ONVIF and support for multiple streams — a lower-resolution stream for detection and a high-resolution stream for recording — make mixing manufacturers easy.

Blue Iris has always been strong in mixed-camera environments.

If you own cameras from several manufacturers, that flexibility matters.

UniFi Protect works most naturally with UniFi cameras.

ONVIF support gives existing-camera owners a much better on-ramp, but the deepest integration still comes from Protect-native hardware.

Local AI

All three can make a legitimate local-AI argument, and they package it differently.

Frigate treats computer vision as a defining feature: normal object detection plus semantic search, face recognition and license-plate recognition, with real flexibility in what hardware handles each workload.

Blue Iris 6 includes built-in AI for object classification, tracking, face recognition and license-plate recognition.

If your impression of Blue Iris comes from older tutorials, this is the update to understand.

UniFi Protect spreads AI across its ecosystem.

Depending on the camera and setup, processing may happen in the camera or on additional Protect AI hardware.

It’s less modular than Frigate and more integrated.

Do You Still Need a Google Coral for Frigate?

No, and for a new installation I wouldn’t start by assuming you do.

Coral was closely associated with Frigate for years because it was a practical low-power detection accelerator.

It’s still supported and can make sense in some low-power or compatibility situations, but Frigate’s current hardware guidance doesn’t treat it as the default recommendation for new installs.

I’d start with the hardware I already own and the current recommendations before buying anything.

Storage

All three keep recordings locally.

They differ in who designs the storage architecture.

Frigate lets you choose: direct-attached disks, surveillance HDDs, an Unraid server, mounted network storage or another Linux storage path.

Retention can be tuned separately for different kinds of recorded activity, which Mike talked about when describing how he manages roughly ten 4K cameras.

Blue Iris manages recordings through the Windows host, with detailed control over where clips live, when they move and how long they’re kept.

A dedicated Windows NVR with multiple storage volumes is a classic Blue Iris architecture.

UniFi Protect manages storage through the console or NVR.

You get less freedom to build an arbitrary storage system and less work to integrate one.

That’s the pattern in a sentence:

Frigate and Blue Iris let you construct more of the system yourself; Protect integrates more of it for you.

Remote Access

This is where operational differences become obvious.

Frigate leaves remote-access architecture largely to you.

I’d normally put it behind Tailscale or another VPN, Home Assistant, or a properly configured reverse proxy.

You get control, and another system to maintain.

Blue Iris includes remote-access tools, mobile apps and its own web server, and newer Blue Iris 6 releases include built-in HTTPS support.

You still operate and secure the underlying Windows machine.

UniFi Protect makes remote access part of the platform.

The mobile and browser experience are designed around connecting back to your local Protect system, and that convenience is part of what you’re buying.

Cost

It’s tempting to boil this down to “Frigate is free, Blue Iris has a license, Protect has no per-camera software fee.”

But software price isn’t system cost.

Frigate: you may need a host, cameras, storage, PoE networking, an optional accelerator and your time. If you already own homelab hardware, it can be extremely inexpensive.

Blue Iris: you need the license, a Windows PC, storage, cameras and networking. The full version is currently listed at $99.95 and includes one year of Basic maintenance. Continued updates and support are optional after that through Blue Iris maintenance plans. If you already have a Windows machine for the job, the license may be a small slice of the total system cost.

UniFi Protect: there’s no traditional per-camera software license for normal use, but you need supported UniFi OS hardware. A complete system can include a console or NVR, storage, cameras, PoE networking and optional AI hardware. The integrated experience carries a hardware cost.

Don’t Forget 24/7 Power

Because an NVR runs around the clock, electricity belongs in the total cost calculation too.

But the software platform alone doesn’t determine that number.

A compact Frigate host can consume far less electricity than a large Windows NVR. A multi-drive Protect NVR can consume considerably more than a small UniFi console. Storage, GPU use, CPU load and the number of drives all matter.

I wouldn’t assume a fixed wattage for Frigate, Blue Iris or Protect.

I’d compare the actual hardware configuration I expect to leave running 24/7.

What I’d Buy First

The first purchase looks different for each platform, and it says a lot about how each one is best evaluated.

Frigate: nothing.

I’d install it on hardware I already own and connect one compatible camera.

Can I get the stream working? Detect a person? Create a useful zone? Find the footage afterward? Turn that event into a Home Assistant automation?

If yes, then I’d decide whether I need a dedicated Intel host, more PoE cameras, additional storage or an accelerator.

Frigate lets me test the architecture before committing much money to it.

Blue Iris: the software.

With a suitable Windows machine and a compatible camera, the license is enough for a meaningful test of recording, alerts, storage, remote access, AI detection and camera compatibility before deciding whether a dedicated Windows NVR makes sense.

UniFi Protect: the ecosystem decision.

The first question isn’t which camera to buy but what size Protect system I’m building.

Before buying anything I’d sort out whether I already have a Protect-capable console, how many cameras I expect, how much retention I need, whether I need a dedicated NVR and whether third-party ONVIF cameras are part of the plan.

This isn’t a ranking.

It’s a reminder that each platform asks you to make a different first commitment.

Which One Fits Which User?

This is more useful than declaring a winner.

Frigate makes sense if you already use Home Assistant, already run Docker or Unraid, want local AI, want broad camera choice, enjoy controlling your own architecture, want detections deeply involved in automation, or want to reuse existing compute hardware.

Frigate rewards people who want to build.

Blue Iris makes sense if you prefer Windows, already have a Windows NVR machine, use many camera brands, want extensive recording and alert controls, like deeply configurable NVR software, or want built-in local AI without changing platforms.

Blue Iris rewards people who want to tune.

UniFi Protect makes sense if you value reliability and integration, already own UniFi infrastructure, prefer appliance-like management, want strong mobile and remote access, want Home Assistant integration without making Home Assistant responsible for the camera infrastructure, or would rather buy a supported NVR platform than assemble one.

Protect rewards people who want the pieces designed to work together.

What Mike and Gavin Taught Me

Neither Mike nor Gavin chose a platform because the others were beyond him.

Mike has run multiple NVR systems and chose Frigate, valuing the flexibility and local intelligence, plus the fact that he can reuse older hardware.

Gavin has run multiple NVR systems and chose UniFi Protect, valuing the integration and reliability.

That tells me something important:

Once you’re technically capable of running any of these, operational preference matters almost as much as feature count.

Someone else could just as reasonably choose Blue Iris for its camera compatibility and mature Windows controls.

Those are all legitimate reasons.

Frequently Asked Questions

Is Frigate Better Than Blue Iris?

Neither is better across the board.

They optimize for different architectures.

Frigate emphasizes local computer vision, Docker and Home Assistant automation.

Blue Iris is a mature Windows NVR with extensive camera, recording and alert controls and, as of version 6, built-in AI.

Both are capable, so the real question is which one you want to operate.

Is Frigate Better Than UniFi Protect?

It depends on what you want to own.

Frigate gives you more freedom to choose cameras, host hardware, AI hardware and storage.

UniFi Protect gives you a more integrated camera, NVR and remote-access system.

Both store video locally, and both can integrate deeply with Home Assistant.

Can UniFi Protect Use Non-UniFi Cameras?

Yes.

Protect supports compatible third-party ONVIF cameras.

The deepest integration remains with UniFi hardware, and some advanced AI functionality for third-party cameras may require additional Protect AI hardware.

Does Blue Iris Have Built-in AI?

Yes.

Blue Iris 6 includes built-in object classification and tracking, facial recognition and license-plate recognition.

Older guides that say Blue Iris always requires an external AI server are outdated, though external providers can still be used.

Does Frigate Need a Google Coral?

No.

Coral is still supported, but it isn’t the default recommendation for new Frigate installations.

Check the current Frigate hardware guidance and the hardware you already own first.

Do Frigate, Blue Iris or UniFi Protect Require a Subscription?

None requires a monthly subscription for basic local recording.

Frigate is open source, with optional paid services such as Frigate+ available separately.

Blue Iris uses a software license, with optional ongoing update and support plans.

UniFi Protect has no normal per-camera software license for local recording but requires supported UniFi hardware.

Can I Use Cameras I Already Own?

Often, yes.

Frigate and Blue Iris are naturally suited to mixed-camera environments as long as the cameras provide compatible streams.

UniFi Protect now supports third-party ONVIF cameras, although those cameras don’t automatically get every native Protect feature.

Do These Systems Require Cloud Storage?

No.

All three can record locally.

Frigate and Blue Iris run on hardware you control, and UniFi Protect stores recordings on its local console or NVR rather than requiring cloud video storage.

Which Has the Strongest Home Assistant Integration?

Frigate and UniFi Protect both have substantial integrations.

Frigate is architecturally centered on exposing camera intelligence for automation.

Protect remains a separate camera platform but exposes a large set of devices, events and media through its official integration.

Blue Iris connects through APIs, MQTT and community integrations.

Which Is Easiest to Maintain?

They require different kinds of maintenance.

Frigate asks you to maintain a host, containers and supporting infrastructure.

Blue Iris asks you to maintain a Windows NVR.

Protect asks you to maintain a UniFi appliance ecosystem, which can reduce the amount of underlying infrastructure you have to manage yourself.

The best model is usually the one that matches infrastructure you already know and actually want to own.

Can I Run More Than One of These at the Same Time?

Yes, and it’s a good way to evaluate them.

Because Frigate and Blue Iris work with standard camera streams, you can point a test camera at more than one system before committing.

The exact behavior depends on the camera and how many simultaneous streams it supports, so I would test with one camera before assuming every model will behave the same way.

Where I’d Start

If I were evaluating these for my own house, I’d begin with the infrastructure already running there.

If Home Assistant, Docker and a homelab are central, I’d test Frigate.

If I had a capable Windows machine dedicated to video and a collection of mixed cameras, I’d put Blue Iris on the list.

If I already had UniFi networking and wanted cameras to feel like another integrated appliance, I’d look closely at Protect.

And I’d test before replacing everything.

Start with one camera.

Live with the alerts.

Look at storage.

Try remote access.

Connect it to Home Assistant.

Then decide whether you want to build the rest of the camera system around it.

Because the best camera platform isn’t necessarily the one with the longest feature list.

It’s the one you’re willing to keep running for the next five years.