Yes, Triton ULTRA integrates with OpenEye Web Services (OWS), on-prem or through Triton Cloud. Depending on how your organization runs OWS, there's a path that fits your environment without forcing you to change how your security team already works.
That matters because the whole point of Triton is covering the places cameras legally and physically can't go: restrooms, locker rooms, etc. The OWS integration connects those blind-spot alerts back to the security operations picture your team already lives in, so a vape, THC, aggression, or keyword event shows up as a real alert in OWS, tied to video from the nearest camera for verification.
OpenEye Web Services (On-Prem)
The fit: This is the most direct path: your Triton sensor sends events straight to an OWS Alert Rule, and your team gets notified right inside the platform they already use to review camera footage - no Triton Cloud account required.
Alert workflow & camera association, live and after the fact: Every event that fires gets logged as a real alert in OWS's event history, so your team can verify what happened with both live and recorded video, and push notifications reach the OpenEye mobile app so your team hears about it even away from their desks. (Full setup steps are in the integration guide linked below.)
Live monitoring, without doing rounds: Because the Triton ULTRA occupancy stream can be added to OWS as its own RTSP stream, operators can pull it up anytime alongside your cameras to check on a restroom in real time instead of walking the halls to do a physical round. Add every restroom to the same view, and one operator can watch all of them at once - a real force multiplier for coverage.
Triton Cloud + OpenEye Web Services
The fit: This path is for teams who want OWS's fuller Alert Rules experience - organized by event group (Health, Safety, Vape/THC), with per-camera mapping and granular user notifications - rather than a single generic webhook. It requires a Triton Cloud account, with the connection authenticated through an API key generated in OWS.
Alert workflow & camera association, live and after the fact: Once your sensor is mapped to a camera and an Alert Rule is built around the event types you care about, every Triton event surfaces in OWS the same way any other alert would - with live and recorded video attached for verification, plus email and push notifications to whichever users or groups you assign. Note: this path doesn't currently pull footage into Triton Cloud's Evidence Room - video review happens inside OWS itself.
Live monitoring, without doing rounds: The Triton ULTRA occupancy stream can also be added to OWS as its own live feed through this path, so operators can check on a restroom in real time, alongside your cameras, without needing to walk over and look.
Frequently Asked Questions
What's the best sensor to use with OpenEye Web Services?
Triton ULTRA. OpenEye built a native Triton Sensor integration type directly into the OWS console - not a generic webhook, but a purpose-built option with sensor-to-camera mapping and Alert Rules organized by event group (Health, Safety, Vape/THC) built in. That means Triton ULTRA plugs in as a first-class citizen in OWS, covering vape, THC, aggression, gunshot, and keyword detection, plus live occupancy visualization and environmental monitoring, all verified against the same camera footage your team already reviews.
What's the difference between the on-prem and Triton Cloud paths for OpenEye Web Services?
On-prem is the fastest way to get an alert flowing - a single webhook, no Triton Cloud account needed. Through Triton Cloud, sensors connect via an API key generated in OWS, get mapped to specific cameras, and plug into OWS's native Triton Sensor integration and Alert Rules system - organized by Health, Safety, and Vape/THC event groups, with granular control over who gets notified.
Does this integration support mobile alerts?
Yes. Once configured, OWS can push notifications to your team's phones through the OpenEye mobile app, so they hear about an event even when they're away from their desks.
How does this integration improve safety response?
Every Triton event surfaces as a real alert in OWS, verified against live and recorded video from the nearest camera - and because the occupancy stream can be added to OWS alongside your cameras, one operator can monitor every restroom in real time instead of relying on scheduled walkthroughs.
What if I'm not sure which setup fits, or I'm running a mixed environment?
Contact us and we'll help you map it out.
Resources
OpenEye Web Services (OWS) – Triton ULTRA Integration Guide — full setup guide for the on-prem webhook path.
OpenEye Web Services – Triton Cloud Integration Guide — full setup guide for API key setup, sensor-to-camera mapping, and Alert Rules.
Triton Sensor Integration Instructions (OpenEye Knowledge Base) — additional reference from OpenEye, including the full event mapping table.
Contact us if you're running a mixed environment or aren't sure which path fits.
