A short note on a practice we have opened formally: conformance engineering, third-party device validation and protocol-level diagnosis, aimed at the manufacturers and platforms carrying a dated Profile S problem.
This is a short announcement rather than an article, so it will not take long.
DevSpark is now taking on ONVIF conformance and interoperability work as a formal practice: preparing a product line for conformance, validating third-party devices against a platform, and diagnosing faults at the protocol level when a device and a VMS will not agree.
It is not a new capability. It is the work we were already being pulled into from the embedded and video side, now stated plainly so that the people who need it can find it.
Why now
There is a date driving this, and it is not ours.
ONVIF withdraws Profile S conformance on 31 March 2027. Profile T is the successor. For a manufacturer whose product line declares Profile S and nothing else, that is a fixed deadline attached to a specific piece of engineering — and the size of that engineering is usually decided by whether the device implements the Media 2 service, which is not a configuration change.
The second reason is quieter. Procurement documents increasingly name the profile explicitly rather than assuming ONVIF support. That shifts a question that used to be answered with a datasheet into one that has to be answered with evidence.
What we actually do
| Conformance audit | Fixed-price assessment of one product line: current status, gaps against Profile T, and a prioritised engineering plan. Delivered as a document your engineers can act on, typically in about two weeks. |
| Client-side conformance | The other half of the problem, and the half with less written about it. Making a VMS consume conformant devices correctly, including the ones that interpret the specification loosely. |
| Third-party device validation | Testing vendor devices against your platform and documenting exactly where they diverge. The evidence integrators ask for and rarely receive. |
| Protocol-level diagnosis | Streams that drop, events that never arrive, PTZ that behaves differently through the VMS than on the device's own web page. Diagnosed at the wire, not by substitution. |
A free tool, before you talk to anyone
We have published a Profile T readiness check: ten questions an engineering manager can answer without looking anything up, with the assessment on screen. Nothing is gated, and nothing you enter leaves your browser.
Its question set is validated against ONVIF Profile T Specification v1.0, and it distinguishes carefully between what the profile actually mandates and what merely matters commercially. One example of why that distinction is worth the effort: H.264 and H.265 encoding are conditionally required for a device, so a camera encoding only H.264 is conformant — but both H.264 and H.265 decoding are mandatory for a client, so a VMS that decodes only H.264 is not. Tools that blur those two send people looking for problems they do not have.
If it is useful
The usual first piece of work is a fixed-price audit of one product line, scoped so that the decision about anything larger is made with evidence rather than optimism.
If you are carrying a Profile S product line into 2027, or you have an integration that has stalled between two suppliers who each say it is not their scope, that is the conversation to have. A short call costs nothing and you will speak to one of our consultants.
Sources:
ONVIF, Profile T
ONVIF, Specifications (the Core and Profile specifications are free public downloads)
More from Info
Related reading
30 Aug 2026
Build vs Buy: What It Really Takes to Build a Cloud CCTV and AI-Video Platform
A cloud video platform looks like a web project and isn't. Where the real engineering lives, what to build versus buy at…
26 Aug 2026
Automating EV Battery Disassembly: The Missing Link in the UK's Battery Circular Economy
EV battery packs are still taken apart by hand. Disassembly — dangerous, high-mix and unautomated — is becoming the bott…
20 Aug 2026
How EU Cleantech Companies Can Enter the UK Market with Government Co-Funding: A Guide to DRIVE35 Partnership Structures
The UK's £2.5bn DRIVE35 programme co-funds up to 50% of industrialising zero-emission vehicle technology in the UK — and…
Bring us the challenge
The one that has been handed back, sits between two suppliers, or nobody can say is possible yet. A short call costs you nothing and you will speak to one of our consultants.
Engineer to engineer. No handoffs.