Edge does the watching.
A Sentinel edge agent runs on-site with the cameras you already own. Local vision handles the hard look at stills when motion matters — so video stays on your LAN and alerts stay useful, not a firehose.
How Sentinel works
Four steps. No forklift. Edge watches on-site — signalbridge.tech is the front door when you’re ready.
- 1
Connect.
Sentinel connects to your existing video and access-control systems through their standard interfaces. No cameras replaced, no servers decommissioned.
- 2
Learn.
Agents observe your site and build a picture of normal — traffic patterns, schedules, which doors open when.
- 3
Watch.
From then on, agents monitor continuously, comparing what they see against what's normal for that camera, that area, that time of day.
- 4
Alert.
When something doesn't fit, the right person gets a clear, specific notification. A human decides what happens next.
Platform
Edge watches. The website configures.
Sentinel is a brownfield overlay: cameras and access stay yours. The edge agent does the watching; signalbridge.tech becomes the control plane once that edge phones home.
signalbridge.tech is the front door.
Once an edge agent phones home over an outbound tunnel, the website is where you configure standing orders, see site status, and manage the deployment — without opening inbound ports or handing out remote-desktop access.
Edge MCP for health and camera quality.
Operators and agents can query health, camera quality, and status through the edge’s MCP surface. That means troubleshooting from the tools you already use — not a VPN jump box and a wall of undocumented services.
Hybrid rollout: LAN first, then the bridge.
Pilots start on the local network: bring the edge up, point it at a camera, prove watch → alert. When you’re ready, the same stack phones home so configuration and oversight move to signalbridge.tech without rip-and-replace.
Pilot path
- LAN now. Stand up the edge on-site, connect a camera you already own, prove watch → alert on the local network.
- Website + tunnel later. When you’re ready, the edge phones home outbound. Configuration and oversight move to signalbridge.tech — still no inbound holes, still no remote desktop requirement.
- Health without hopping boxes. Edge MCP exposes health, camera quality, and status so you (and your agents) can check the site the same way you’d check any other service.
Questions we hear first
Do we have to replace our cameras?
No. That's the point. Sentinel overlays what you have.
Where does it run?
Watching happens on an edge agent at your site. Configuration and oversight move to signalbridge.tech when the edge phones home over an outbound tunnel. Pilots often start LAN-only; we expand when it earns it.
Do you need inbound ports or remote desktop?
No. The edge initiates an outbound connection when it’s time to attach to the control plane. Day-to-day health and camera status are available through the edge MCP — not by remoting into a desktop.
Does it record?
Your existing system keeps handling recording. Sentinel watches and alerts.
What happens when it flags something?
Your designated people get an alert with what was seen, where, and when. Humans stay in charge of the response.
How do we start?
A scoped pilot: small camera count, one site, agreed success criteria — usually LAN-first, then website + tunnel when you’re ready. Contact us.
Put your cameras to work.
We're running pilot deployments now. If you have an existing camera system and want it actively watched, talk to us.
Signal Bridge Technologies, LLC · Ellinwood, Kansas