Facility screens, on duty
Dutywall is the wall that stays useful all day and takes over when it matters: a managed signage system and a facility mass-notification endpoint, running from a box on your LAN.
Preview is invite-only. The appliance does not need a cloud account. First facilities: East Tennessee and Western North Carolina.
Same hardware. Two jobs. Everyday content until a panic, CAP, or NWS warning paints the selected zones.
lobby is a zone, not a duration.
Displays never talk to the public internet for content. They poll the local Dutywall box. If the WAN dies, last-good content and local emergencies still run.
Optional cloud sync is agent-initiated: desired state down, status up. Same reason TVs work through NAT. Privacy-sensitive sites skip the cloud entirely.
Severe-weather auto-alerts come from api.weather.gov and map onto real presets (tornado, flash flood, winter storm). A manual emergency always overrides.
Generic digital signage is crowded and priced like a poster printer. Dutywall is for plants, campuses, clinics, and municipal buildings that already think in zones, musters, and who is on the wall when the siren goes.
One box on the LAN (Linux, Pi, or Windows with Docker Desktop). Docker compose. Panel password. No cloud user. Nothing phones home except NWS. This is the air-gap / CMMC-shaped path. Setup guides.
Same box. Set a site token. The box pulls desired content and pushes inventory. Multi-site operators get a panel; the LAN stays closed.
Dutywall is being stood up from East Tennessee, with Western North Carolina next door. Mountain weather, spread-out campuses, and plants that already own TVs are the first design center, not a Times Square billboard.
Tri-Cities, Knoxville, and the plants, hospitals, and schools that sit under NWS Morristown (KMRX). Severe storms, winter, and river flooding are first-class, not a weather widget.
Asheville, Boone, and the ridge towns where a WAN blip should not blank a hallway. Standalone first; cloud only if you want it.