Your security data is your most sensitive data
Schedules, locations, floor plans, footage. Put it in the wrong hands and it is a map of how to get past you.
SELF-HOSTED SECURITY COMMAND
An unsafe world needs security you control.
Huntress brings your sensors, alarm panels, cameras, people and devices into one live picture, understands what they report, and responds. It is one self-contained solution on hardware you own, from a Raspberry Pi at a single site to a data centre serving hundreds, and your data stays in your control the whole way.
- Your data stays on your hardware
- Zero dependencies, no cloud account
- Runs without internet
- One site to hundreds
-
Person at gate after hoursIncident · confidence C3 Probable · 3 sourcesHigh
-
Gate cameraperson 94% · region GateDetected
-
Panel 4F2A · zone 3 Dock doorBurglary verified → C5Verified
-
Siren · sounding for 5 minCommand sent by rule · confirmedConfirmed
-
Anna B. · PulseOnline · last contact 12 s agoActive
- 116sensor types in 13 categories
- 27rule conditions, plus sequences and sustained logic
- 250+SIA alarm codes understood
- 230+Contact ID codes understood
- 13kinds of output you can operate
THE PREMISE
We live in an unsafe world.
Doors get forced, networks get probed, and the systems meant to keep watch fail at the worst moment. What your security knows is exactly what an adversary wants to know: which door opens when, who is where, what the cameras see.
Someone else's cloud is someone else's risk
Their outage is your blind spot. Their breach is your exposure. Their terms, prices and future are not yours to decide.
Every dependency is a way in
A database server, a message broker, a runtime: each one is something more to patch, to misconfigure and to fail on its own schedule.
So the answer is not more services. It is fewer, and all of them yours.
YOUR DATA, YOUR CONTROL
Your data must stay in your control.
That is the whole idea behind Huntress. Everything it learns about your sites and your people stays on a machine you chose, and nothing about the way it works needs anyone else's permission or uptime.
It lives on your hardware
Events, pictures, video clips and locations sit in a database on the machine you picked: a server, a mini PC, a Raspberry Pi, a virtual machine in your own cloud account. There is no copy anywhere else.
Self-contained, with nothing to depend on
Everything it needs comes inside it, from the database to the video tools to the object detection. There is nothing to install beside it and nothing to keep alive around it, so there is nothing outside it that can take it down.
It keeps watching when the world does not
No cloud account, no subscription and no vendor to call home. The internet can drop and a supplier can disappear, and your doors, cameras and people are still covered.
- No extra servers to run
- No software to patch beside it
- No cloud account
- No subscription
- No telemetry
The few things that may reach outwards (updates, outgoing e-mail, map tiles) are optional, and the complete list of what connects out is published.
SCALE
Start with a Raspberry Pi. Grow to hundreds of sites.
The same solution runs at every size, so you grow by adding hardware, not by changing products. Your data stays in your control at the first site and at the hundredth.
ONE SITE
A small business and a Raspberry Pi
A shop, a workshop, a small office, a home. A Raspberry Pi-class computer is enough to run it, with your sensors, cameras and alarm panel on the same network.
- Linux on arm64 or x64, or Windows
- Fully offline if you want it
A FEW SITES
One server, an edge at every site
A server or mini PC at the centre. A small Huntress Edge at each other location reaches its cameras, Zigbee dongles and devices, and dials out to you. Nothing is opened inbound.
- Outbound connections only
- Detection and video clips can run on the edge
HUNDREDS OF SITES
A data centre, or your own cloud
A central server in your data centre or in your own cloud account, an edge at every site and one address for every operator. Each customer gets an isolated organisation of their own.
- Roles, isolation and API keys per organisation
- A provisioning API for repeatable onboarding
- Signed updates you approve
- Automatic rollback if an update fails
- Backups and retention you control
- Fits the monitoring you already run
CAPABILITIES
From signal to action, in one system.
1
Connect
- HTTP, MQTT and e-mail in, with no SDK
- Alarm panels over SIA DC-09 and Contact ID
- RTSP cameras and Zigbee devices
- 116 sensor types in 13 categories
- Edges for sites behind NAT
2
Understand
- One event vocabulary across 12 domains
- Limits on any measurement, without flapping alarms
- Object detection in regions you draw
- Live charts, zone maps and camera timelines
- Source address recorded for every event
3
Decide
- 27 conditions, schedules and sequences
- A Test tab that replays real events
- Cooldowns and limits, so alerts never become noise
- Confidence from C1 to C5, raised by corroboration
- Verified alarm codes escalate by themselves
4
Act
- Incidents with timeline, notes and bulk resolve
- E-mail and webhooks with templates
- Lights, locks and sirens over MQTT, Zigbee or HTTP
- Every command confirmed, audited and revertible
- 12 kinds of rule action
IN DEPTH
What it is like to work with.
Rules that read like sentences
A rule is WHEN something happens, IF conditions hold, THEN actions run, OTHERWISE others do. Define business hours or a maintenance window once as a schedule and use it everywhere, or start a rule when it switches on or off. Daylight saving is handled for you.
- Nested logic, counting, sequences and “sustained for”
- A plain-English summary of every rule
- Test against the last hour to seven days before saving
Cameras that understand what they see
Watch any RTSP camera live in the browser with nothing to install, and keep a timeline of pictures. Switch on object detection and Huntress recognises people, vehicles and animals, counts only those inside the regions you draw, and keeps a short video clip around each one.
- Analysed on your server or on the camera's edge
- No faces, no biometrics, nothing sent elsewhere
- Detections feed rules, incidents and device commands
Alarm panels beside everything else
Huntress listens to intruder and fire panels over IP, with AES-encrypted SIA DC-09 and Contact ID, and normalises every code into the same events as your other sensors. It complements your alarm receiving centre rather than replacing it.
- Zones linked to sensors share one history
- Verified alarms raise the incident to C5 on their own
- Supervised links and replay protection
People, not just places
Pulse turns a phone into a tracker with nothing to install: a heartbeat with location, and a panic button you hold for three seconds. Huntress watches for silence, so a person who stops reporting becomes an incident even when they cannot say a word.
- Pair by scanning a QR code
- Geofences, a map per person, “not moving” and “not reporting” rules
- Your own app can report through the same API
Close the loop
Huntress does not only listen. Operators and rules switch lights, release door strikes, sound sirens and open gates through MQTT, Zigbee or HTTP, including Shelly, Tasmota and ESPHome. Every command is checked, recorded and followed until the device confirms it.
- Locks, strikes and sirens need an Owner or Admin by hand
- “For five minutes”, then the previous state returns
- All on / All off for a whole zone, each one audited
WHO IT'S FOR
For people who cannot afford to guess.
SECURITY COMPANIES & MSSPS
Many sites, one console
Give each customer their own isolated organisation, bring their sites in through edges, and sit beside the alarm receiving centre you already run.
- Isolated organisations, roles and API keys
- Provisioning API for repeatable onboarding
- Panels can report to Huntress and the ARC
HIGH-VALUE INDIVIDUALS
Discreet and private
Residences, vehicles and the people in them, on a platform that no cloud provider holds. Your data sits on hardware you control, not in someone else's data centre.
- Pulse panic button and tracking, geofences
- Two-factor sign-in and passkeys
- No third-party telemetry
GOVERNMENT & FIELD AGENCIES
Deployable anywhere
A forward site, a disconnected network, an air-gapped facility. Commodity hardware, no external dependencies, and updates you can carry in on a signed bundle.
- Runs fully offline on Linux or Windows
- Offline, signature-verified updates
- Every connection out is documented
ENTERPRISE & FACILITY OPERATORS
Sites that must run themselves
Warehouses, plants, campuses and data rooms. Connect what you already have, define hours once, and let rules, incidents and device control handle the routine.
- Schedules for hours, shutdowns and holidays
- Webhooks and e-mail into your ticketing and paging
- Limits on temperature, power, gas and more
INTEGRATIONS
Any device. Any format. Any protocol.
Huntress speaks the language of your hardware, not the other way round. If a device can make a web request, publish to MQTT or send an e-mail, it can report. No driver, no SDK, no custom firmware.
HTTP
Any device that can POST. JSON, a bare number, a form or a raw JPEG.
MQTT
A broker is built in. Devices publish to it, and it carries commands back to your outputs.
SMTP
Cameras and recorders that can only send e-mail can still report.
SIA DC-09
Alarm panels over IP, with AES encryption, supervision and replay protection.
Contact ID
The long-established panel format, with verified alarms raised to the highest confidence.
RTSP cameras
Live view, snapshots, detection and clips from any RTSP camera.
Zigbee
A coordinator dongle on the server or an edge: sensors, lights, locks.
HTTP outputs
Presets for Shelly, Tasmota and ESPHome, or any web endpoint, via an edge on the LAN.
Webhooks & e-mail
Rule actions with templates, to anything with a URL or a mailbox.
Provisioning API
Create places, sensors, people and panels from scripts, safely and repeatably.
A sensor is live in one line
curl -X POST https://<your-host>/hunt/<sensor-token> \
-H "Content-Type: application/json" -d '{"value": 1}'
→ {"sensorId":12,"sensorName":"Front door","value":1,"timestamp":"2026-10-12T09:14:03Z"}SECURITY & PRIVACY
Security you can check.
In an unsafe world, a promise is not enough. What protects Huntress, what does not and everything it connects to is written down, so you can verify instead of trusting.
Strong sign-in
Two-factor sign-in, passkeys, account lockout and a sign-in history for every account.
Roles and isolation
Owners, Admins and Viewers see and change only what their role allows. Organisations are isolated from each other.
Access that ends with the person
API keys are shown once, kept only in protected form, and stop working the moment their owner loses access.
Private by design
No telemetry and no analytics. Object detection recognises people, vehicles and animals and never identifies anyone.
A real audit trail
Where every event came from, who or what sent each device command, and a full timeline of every incident.
Straight about limits
What is encrypted, what is not and what is not recorded are stated plainly, not left for you to discover.
GET STARTED
Keep your security, and your data, in your own hands.
Create an account, add a place and a sensor, and watch your first reading arrive live. The quick start takes about fifteen minutes.
Already have an account? Sign in.
Sign-up needs an invitation key from whoever runs your server.