Kaniworks product

PyroWatch

Every alarm. One glance.

Most buildings have fire panels from different manufacturers — a Notifier panel here, a Simplex there — and each speaks its own language on its own screen. Nobody can watch all of them at once. PyroWatch fixes exactly that: every panel, every site, one live dashboard.

And one promise above all: PyroWatch can see everything and touch nothing. It is read-only by architecture — physically unable to send commands to your life-safety hardware. Monitoring software should never be able to silence an alarm, and ours cannot.

In production · serving real operations today

Miniature factory on a floor panel with smoking chimney and live sensors

PyroWatch · All sites

NORMAL
Z1
Z2
Z3
Z4
Z5
Z6
Z7
Z8
Z9
Z10
Z11
Z12
12:01Heartbeat · all panels OK
12:03Plant 2 · routine poll

All sites normal — 18 zones monitored live

Built for

Facility & building teamsFacilities-management companiesFire-safety contractors offering monitoring AMCsMulti-site operators

What it does for you.

Four vendors, one view

Honeywell Notifier, Simplex, Edwards EST, and Morley-IAS panels — normalized into one consistent live picture.

Alarms in under a second

Events stream over WebSockets and appear on every operator's screen in real time. When one operator acknowledges, everyone sees it instantly.

Read-only by architecture

There is no code path from PyroWatch back to a panel. It cannot silence, reset, or trigger anything — by design, not by policy.

No holes in your firewall

Site gateways connect outward over encrypted connections. Your sites never open an inbound port to the internet.

Compliance reports

Printable event and test records, ready for audits and authorities — generated from the data, not typed up afterwards.

Everything on the record

Every alarm, acknowledgement, and restoral is logged with who, what, and when. The audit trail writes itself.

Why read-only matters

Life-safety systems must never take instructions from monitoring software — a bug or a breach could otherwise silence a real alarm. PyroWatch is built so this is impossible: the architecture has no write path to your panels. Your fire system keeps working exactly as certified, whether our software is connected or not.

How it works.

1

Connect

An edge gateway at your site talks to the panels in their own protocols (BACnet/IP, Modbus TCP).

2

Stream out

Events flow outbound over encrypted connections — no inbound firewall ports.

3

Normalize

The cloud turns every vendor's format into one consistent event stream.

4

Watch & respond

Operators see, acknowledge, and record — across every site, in one place.

Under the hoodTimescaleDBSocket.ioBACnet/IPModbus TCPEdge gatewaysTLS outbound-only

Questions, answered.

Can PyroWatch silence or reset a panel?

No — and this is deliberate. There is no command path from the software to the panels. It monitors, alerts, and records. Nothing more.

Do we need to change our firewall?

No. The site gateway only makes outbound encrypted connections. You never open an inbound port.

What happens if the internet at a site goes down?

Your fire panels keep operating exactly as before — they never depend on PyroWatch. Monitoring resumes automatically when the connection returns.

Which panels are supported?

Honeywell Notifier, Simplex, Edwards EST, and Morley-IAS today, via BACnet/IP and Modbus TCP gateways. Additional vendors are added through the same normalization engine.

Curious how PyroWatch would fit your operation?

We’d be happy to walk you through the live system — twenty relaxed minutes, your questions, honest answers. We always reply within a day.