Back to SecuraCV

About

Who makes SecuraCV, and why.

SecuraCV is built by Errer Labs — an independent workshop building privacy-first video infrastructure in the open.

The thesis, in one line: most camera systems can be configured for privacy; this one lacks the code to violate it. There is no face recognition to disable, no cross-camera tracking to opt out of, and no single-user export to lock down — because none of it was ever written.

What we build

A Canary is a small, open-source camera device built around a witness kernel: it watches a scene and emits signed motion events — a tamper-evident record that something happened — instead of a raw feed anyone can quietly siphon. Footage is sealed so that no single person can open it alone. The result is a camera that can prove what it saw without becoming a surveillance tool pointed back at you.

Everything is open: every STL, OpenSCAD source, bill of materials, and the firmware itself are released under the Apache License 2.0. You can print the enclosure, flash a board from your browser, and read exactly what the device does — or doesn't do — before you trust a word of it.

Why "privacy by absence"

Every camera system on the market has a "privacy mode," and every one of them can be switched off by someone with admin access — an employer, a landlord, a platform, a government, or an attacker who gets in. A setting is a promise. Absent code is a fact. We design for the second kind: the capability to identify, track, and export a person simply isn't present in the device, so it can't be turned back on later.

Open all the way down

Hardware, enclosures, and firmware are public. Kits sell convenience, never access — you can always build one yourself.

A workshop, not a warehouse

Kits are built and tested in small batches. We're transparent about how the economics work and what's still a prototype.

No accounts, no cloud lock-in

The devices run on your hardware. There's no subscription, and no feed leaving your network for us to hold.

Honest about status

This is prototype software in active development. We say what's shipping, what's on the bench, and what's still an idea.

Why build it this way?

This wasn't an accident. Every missing feature is a deliberate design choice.

🔒 Settings can be changed

Every camera system has a "privacy mode." Every one can be turned off by someone with admin access — an employer, a landlord, a government, a hacker.

If the code exists, it can be enabled. We removed the code.

🤖 Machines are getting eyes

Robot vacuums, delivery drones, autonomous vehicles, elder care systems — they all need to see. That doesn't mean they need to identify.

Seeing and surveilling are different capabilities. We built only the first.

⚖️ Today's data is tomorrow's evidence

Video captured for "security" becomes evidence in lawsuits, divorce proceedings, immigration cases, insurance disputes. Footage intended to protect can be weaponized.

The safest data is data that doesn't exist. We output events, not footage.

🏛️ No single point of failure

When one person can export video, you have one person to bribe, coerce, or compromise. Multi-party approval means no single actor — not even the system owner — can extract footage alone.

Trust is distributed, not concentrated.

Built in the open

You don't have to take our word for any of this. The operating model, unit economics, and roadmap are published as pages you can read:

Get in touch

Questions, press, partnerships, or a bug to report?

Errer Labs

Email: errerlabs@gmail.com

Web: errerlabs.com · More ways to reach us on the Contact page.