Reddwatch Documentation
Reddwatch is a critical-device monitoring platform built by Redd Ash Technologies for the people who keep physical-security networks alive: city surveillance systems, industrial sites, campuses — cameras, radios, switches, servers, and access control, watched around the clock.
The per-client operations dashboard: device fleet, live problems, RF link
health, and camera frame verification in one place.
Where to go
| You are… | Start here |
|---|---|
| Evaluating Reddwatch | Product overview · Why Reddwatch |
| An integrator running client sites | Integrator guide |
| An operator watching the board | Operator guide |
| Building or installing a site node | Factory provisioning · On-site provisioning |
| Handling plans and invoicing | Finance & billing |
| Curious how it all fits together | High-level architecture · The node appliance |
| Redd Ash engineering (sign-in required) | Low-level architecture · Cloud engineer guide · Roadmap |
What Reddwatch does
- Watches every device on a site — IP cameras, point-to-point radios, switches, servers, access control — and understands how they depend on each other, so one failed radio doesn't page you 40 times for the cameras behind it.
- Sees what the camera sees. Scheduled frame captures compare every camera against a reference image and flag blur, tampering, repositioning, or a dead feed — problems a ping can never catch.
- Measures the radio links themselves. Live RF quality and signal telemetry from 60 GHz backhaul radios, so marginal links surface weeks before they fail in a storm.
- Ships as an appliance. A pre-baked site node auto-registers, discovers the site, and updates itself over the air with signed releases and automatic rollback.
- Serves integrators, not just sites. Multi-tenant by design: each integrator sees exactly their clients, operators see exactly their scope, and site reports generate as branded PDFs on demand.