Most store ops managers hear “ONVIF” for the first time from their IT team or security integrator and assume it is a camera hardware specification. It is not.
ONVIF is a software interoperability standard. It helps IP cameras and other video software communicate with one another, even when they come from different manufacturers. You do not need a special type of camera because a system uses ONVIF. In many cases, you can use the cameras already installed in your stores.
That distinction matters when you are evaluating camera analytics. The first question is usually not, “Do we need new cameras?” It is, “Can the cameras we already have provide an accessible video stream to another ONVIF-compliant software client?” Understanding the answer will make your first conversation with IT or your security integrator much more productive.
What ONVIF actually does
ONVIF stands for Open Network Video Interface Forum. It was formed in 2008 by Axis, Bosch, and Sony as a standardization body for network video products. ONVIF defines interoperability profiles for IP cameras, giving manufacturers and software providers a shared set of expectations for how devices communicate.
Think of ONVIF as a common language between a camera and a software application. Without a shared language, every camera manufacturer could require its own connection method. With ONVIF, a compatible software client can discover cameras, request video streams, and in some cases receive events or control functions through defined interfaces.
For store operations, the practical benefit is easier access to camera video without replacing an entire estate of cameras. Youtiligent connects to existing ONVIF-compliant cameras. Its ONVIF auto-discovery scans the camera network, finds connected cameras, and maps their stream URLs.
Youtiligent uses a local edge processor, such as an Intel NUC or equivalent, inside the store environment. Video is processed locally, and no video footage leaves the store network. That architecture still depends on the cameras and network allowing the required stream access, which is why compatibility needs to be checked before implementation.
Profile S and Profile T, explained plainly
ONVIF is not a single yes-or-no feature. Cameras can conform to different ONVIF profiles, and the profile tells you which capabilities have been tested and defined.
Profile S: the baseline video connection
Profile S is the baseline profile for video streaming. It defines access to an RTSP video stream, along with functions such as pan-tilt-zoom control and motion events.
For an operations manager, the most important part is the stream. A camera that has passed Profile S conformance testing can expose its video feed to an ONVIF-compliant software client. This is the basic connection needed for many video analytics use cases.
Profile S does not mean every camera behaves in exactly the same way. It means the camera has been tested against the Profile S requirements. The way the camera is configured, the way its network is protected, and the way an NVR manages access can still affect whether another application can connect.
Profile T: newer capabilities and protections
Profile T adds capabilities beyond the baseline Profile S connection. It supports H.264 and H.265 video encoding, HTTPS and TLS encryption for the video stream, and metadata streaming, including object detection events.
In practical terms, Profile T can provide higher-quality and more secure video communication, along with a broader way to share event information. If your camera estate supports Profile T, that is useful information for your IT or security team to consider.
Youtiligent supports both ONVIF Profile S and Profile T. That does not mean every store needs Profile T, or that Profile S is inadequate for every use case. It means the relevant question is which profile each camera model passed and whether its current configuration permits local stream access.
Conformance testing is the question that matters
Camera manufacturers sometimes describe products as “ONVIF-compatible.” That phrase is not as precise as it sounds. The key distinction is between marketing language and ONVIF conformance testing.
A camera that passed ONVIF conformance testing for Profile S or Profile T has been tested against the requirements of that profile. This gives other ONVIF software clients a defined basis for working with the device. “ONVIF-compatible” on its own may not tell you which profile applies, or whether the specific model was tested.
When checking your camera estate, ask about the exact model, not only the manufacturer. Cameras from commercial brands such as Axis, Hikvision, Dahua, Hanwha, Bosch, Uniview, Pelco, and Sony may support ONVIF, but support can vary by model, firmware, and configuration.
Look in the camera’s technical specifications PDF for the ONVIF certification mark. You can also ask your security integrator or camera vendor whether the cameras passed ONVIF conformance testing, and for which profile. Cameras installed after 2018 by major commercial brands almost all support at least Profile S, but confirmation is still worthwhile before a project begins.
This is not a request for an exhaustive IT audit. A camera model list and the applicable ONVIF profile are often enough to start a compatibility review.
ONVIF compatibility is necessary, but not sufficient
ONVIF gives you an important foundation, but it does not solve every connection problem. Implementation variations exist between manufacturers and models. Two cameras can both support Profile S while exposing different configuration options or requiring different permissions.
Network design can also prevent access. An RTSP stream may be available on the camera but blocked from the local software environment by firewall settings. In other installations, the network video recorder, or NVR, controls access to the cameras and may not automatically permit a third-party application to request the stream.
There may also be restrictions connected to the NVR vendor. A contract or exclusivity arrangement could limit third-party stream access. That is not an ONVIF failure. It is a commercial or configuration constraint that needs to be identified before deployment.
The useful way to frame this is simple: ONVIF compatibility is necessary, but it is not sufficient. You need both a conformance-tested camera and a network setup that allows an approved software client to reach the stream.
Three questions to ask your security integrator
Bring these questions to the first conversation. Ask for answers at the camera-model level wherever possible.
- Did these cameras pass ONVIF conformance testing, and for which profile, S or T?
Ask the integrator to distinguish a conformance-tested model from a product that is only described as “ONVIF-compatible.” If you have several camera models, request the answer for each one. - Is the RTSP stream accessible from within the local network?
Ask whether the stream can be reached by an approved software client inside the store network. Confirm that the NVR’s firewall settings, network segmentation, or account permissions do not block access. - Are there any non-disclosure or exclusivity agreements with the NVR vendor that would block third-party stream access?
This question separates technical compatibility from contractual restrictions. Your integrator should be able to tell you whether any agreement or vendor policy affects access to the camera streams.
These questions also help your teams use precise language. “The cameras are ONVIF-compatible” is a starting point, not a complete answer. “This camera model passed Profile S conformance testing, and its RTSP stream is accessible from the local network” is much more useful for planning.
A practical next step before the IT meeting
Start by collecting the camera model list for one store or a representative group of stores. Include the camera manufacturer, model, and the NVR or video management system in use. Your security integrator can then confirm the ONVIF profile and identify any stream access restrictions.
If you have a camera model list and want to know whether it qualifies before starting any conversation about the platform, send it to us. We check it and give you a straight answer. [email protected].
Back to Store Ops Insights