Home / DevSpark VMS
White-label video management software
DevSpark VMS, under your brand. Connect ONVIF and RTSP cameras, keep recordings on the customer site and manage the estate from a browser. Built for security installers and integrators who want to offer their own video platform.
Your logo, colours and domain · No per-camera software fee · UK-built
One platform, your customer experience
Your brand. Your customers. Your video service.
Offer DevSpark VMS under your own name, with the platform and engineering support behind you.
01
Your brand throughout
Your logo, colours, domain and company name on the interface. Branding is configured within the platform.
02
Your customer relationship
You set your customer pricing, hold the agreement and provide their first point of support. DevSpark supports your team.
03
A platform for multiple sites
Organise customer sites, cameras and access in a multi-tenant interface, with recording and detection on each site gateway.
A white-label licence covers use of the DevSpark platform. Custom development and project IP ownership are agreed separately.
Inside the platform
What your operators actually see
Screens from the running platform rather than a rendering. Every one of these is a working part of the product today.
Detection is the point, not the pixel count
A camera records everything. The question an operator has is narrower: which of last night’s alerts mattered, and where is the clip. Detection runs at the edge, on the gateway in the building, so classification does not depend on the line to the internet staying up.
Every event carries its object class, a confidence figure, the camera and the moment, and the version of the model that produced it. That last field is what lets you answer, months later, why the system called something a vehicle — and it is written into the same append-only ledger as every operator action.
Alerts are raised and acknowledged in the control centre. Email, webhook and push delivery are in development, so an unattended site should still be reviewed by someone today.
The shape of it
On-site video, cloud-connected management
| Where | What runs there |
|---|---|
| On site | One small gateway on the same network as the cameras. It pulls RTSP, serves WebRTC, runs object detection, drives PTZ, and holds every credential. |
| The link | A single outbound, authenticated tunnel. Nothing inbound, nothing exposed, nothing for a firewall change request. |
| In the cloud | The web interface, the event index, the recording index and the audit ledger. Multi-tenant, so one deployment serves many customers and each is isolated from the others. |
| In the browser | Live wall, timeline, synchronised review, search and exports. Nothing to install, no plug-in, no client application. |
Video goes straight from the gateway to the browser. It does not pass through our cloud. Appliance capacity, storage and network requirements still depend on the camera workload and how the system is used.
- Recordings are written and retained on the appliance, on the customer’s own network. They are not uploaded to us.
- Live viewing streams peer-to-peer from the appliance to the authorised operator’s browser. Nothing is stored in transit, but the stream does leave the site when someone remote opens it.
- Event metadata, alerts and appliance health are sent to our cloud service — what was detected, when, on which camera, and whether the system is healthy. Not the video itself.
- Exports leave the site when an operator exports them. Every export is an audited action.
So the accurate summary is: footage stays on site, metadata syncs. The hosting region for the cloud components is confirmed in writing at deployment.
In production
What the platform does today
Every row below is built, running on real hardware, and measured against live camera firmware rather than a datasheet. See planned features separately.
| Capability | Detail |
|---|---|
| Live view | Sub-second WebRTC, pulled direct from site. Grid of 1, 4 or 9, spotlight, fullscreen, and automatic paging when there are more cameras than tiles. |
| Codecs | H.264, H.265 and AV1 ingested and decoded at full sensor resolution against live firmware — including 2592×1944 at 30fps and 3840×2160 at 25fps. |
| ONVIF discovery | Scans the gateway’s own network and onboards what it finds, so a camera is added by selecting it rather than by typing an RTSP URL. Credentials are written to the gateway and never leave the customer’s building. |
| PTZ | Pan, tilt and zoom over ONVIF and vendor APIs, with the camera’s own telemetry read back as confirmation. Check the compatibility matrix for the tested model and firmware. |
| Object detection | People, vehicles and objects classified at the edge, with confidence recorded against every detection and the model version stamped on the event. |
| Thermal and bispectral | Devices exposing two image sources are ingested as two independent streams, because a thermal sensor and a visual sensor differ in resolution and an operator wants either on the wall alone. |
| Audio | Listen on one camera at a time, transcoded on demand where a camera publishes a codec the browser cannot carry. |
| Review | Scrubbable timeline with alert markers, playback at 0.5× to 2×, and synchronised multi-camera review locked to a single clock so you can follow someone across a site. |
| Search | Find footage by object class, camera, time window and confidence, then jump straight to that moment in the timeline. |
| Site map | Every camera plotted on a schematic plan of its site, coloured by live health, with field of view and a jump straight to that camera on the wall or in playback. |
| Evidence export | Clip download, or a bundle carrying SHA-256 hashes, the detections inside that window and model provenance. |
| Retention | Per-camera retention in days with an automatic sweep, and a ledger entry recording that footage existed and was deleted on policy rather than simply being unavailable. |
| Access control | Viewer, operator and admin, enforced server-side rather than hidden in the interface, with every privileged action written to an append-only audit ledger. |
| White-label | Your logo, colours, domain and company name throughout, applied as a configuration record rather than a forked build. |
What is coming
The capability landing next
These items are planned or in development, and are not included as currently available capabilities. Confirm required features and release scope with us before a rollout.
| Capability | Where it stands | Stage |
|---|---|---|
| Scheduled 24/7 recording | Operator-initiated recording and per-camera retention run today. Round-the-clock segmented capture on a schedule is the next release. | Next release |
| Outbound alerting | Alerts are raised, classified and queued for acknowledgement in the control centre today. Email, webhook and push delivery extends that off-screen. | In development |
| Analytics rules on live streams | Intrusion zones, line crossing and loitering run across recorded review today. The same rules applied continuously to live feeds is the next step. | In development |
| ANPR and face recognition | Object detection is built and running — people, vehicles and object classes, with a confidence figure and the model version stamped on every event. Plate and face recognition extend that same edge pipeline rather than replacing it. | Roadmap |
| Native mobile applications | The interface runs in any modern phone browser today, with no plug-in. Native iOS and Android clients add push and background alerting. | Roadmap |
| Redaction and subject access export | Evidence bundles and the audit ledger are built. Automated blurring and a one-click subject access request bundle build on top of them. | Roadmap |
Camera compatibility
A compatibility matrix that includes the failures
We keep a record of the models tested with DevSpark VMS, with the measurements taken against live firmware: negotiated resolution and frame rate, codecs ingested, PTZ angles commanded and the position the camera reported back afterwards.
It also records what is not proven on each device and any limitations found. Share the model numbers and firmware versions from your estate so we can identify what has been tested and what needs a compatibility check.
Commercial model
No per-camera software licence
License DevSpark VMS per site and per appliance, and offer it under your own brand.
Software and your customer offer
The licence covers use of the DevSpark platform. You hold the end-customer agreement, set your own pricing and provide their first point of support. DevSpark retains the platform IP and supports your team.
Adding a camera does not add a per-camera software fee. We agree the number of sites and appliances, branding and support scope before deployment.
Plan for the whole deployment
Gateway hardware, recording storage, connectivity, commissioning and support still need to be budgeted. Camera resolution, frame rate, retention and analytics affect the capacity required.
More cameras may need more storage or an additional appliance. We quote against your estate rather than assuming one configuration fits every site.
When you need a commissioned platform
Custom development with ownership agreed from the start
For requirements beyond the licensed product, commission a separate engineering engagement.
Scope can cover an edge gateway, multi-tenant cloud video management, analytics, integrations and web or mobile applications. Each deliverable is agreed and validated for your project; these are development work packages, not additional features included in the current VMS licence.
01
Scope and prove
Define the customer workflow, camera compatibility and security requirements. Use a scoped discovery and working proof to establish the build plan.
02
Deliver in stages
Agree milestones, acceptance criteria and demonstrations for the gateway, cloud services and applications. Validate against the devices and deployment conditions you need.
03
Agree the handover
Define project-specific source ownership, repositories, cloud accounts, documentation and ongoing support in the development agreement. Identify existing components and third-party licences explicitly.
Licensing DevSpark VMS does not transfer ownership of its source code. A custom build has a separate scope, delivery budget and IP agreement.
Getting started
Four steps, and you can stop after any of them
01
Twenty minutes
We show it running on real cameras rather than slides, and you tell us where it would fail on the estates you actually look after.
02
Pick one site
One client, one gateway, cameras they already have — running alongside whatever is there now.
03
We commission it free
No cost to you or to them, done with your engineer so your team learns it on a live system instead of a manual.
04
Decide in the open
If it is not right it comes out and nothing is owed. If it is, we agree commercial terms and you keep the client.
Questions we get asked
Straight answers, including the awkward ones
What is a VMS, and how is DevSpark VMS different?
A video management system connects camera streams, recording, live viewing, review and evidence export. DevSpark VMS offers these workflows under your brand, with recording and detection on a customer-site appliance and a cloud-delivered interface. Software licensing is per site and per appliance, rather than per camera.
What does DevSpark VMS cost?
Software is licensed per site and per appliance, with no per-camera software fee. We quote against your sites, appliances, camera workload, storage, retention and support requirements. Adding cameras may require more hardware or storage even though there is no additional per-camera software licence.
What should we include in the deployment budget?
Include the software licence, gateway appliances, recording storage, connectivity, commissioning and support. The required capacity depends on camera resolution, frame rate, retention and analytics workload. We review these with you before agreeing a rollout; there is no assumed saving or one-size-fits-all estate price.
Which cameras does it work with?
The platform integrates ONVIF Profile S and T cameras and reachable RTSP streams. Model, firmware, codec, audio and PTZ differences still matter. Ask for the written compatibility matrix to see the devices tested, the results and anything not yet proven before specifying a rollout.
Can it replace our existing NVR or DVR?
It runs alongside one first, which is the point of a free first site — nothing is removed to evaluate it. The gateway reads the same cameras your recorder is reading, so both can run on the same estate while you compare them. Where an estate then decides to retire the recorder, recording continues on the gateway appliance and the cameras are untouched, because they were never bound to the recorder in the first place.
Can it carry our brand instead of yours?
Yes. Your logo, your colours, your domain and your company on the login screen and in front of your client. Branding is a configuration record rather than a forked build, so your instance is never a stale copy waiting on us to merge something. Your client need not know we exist, and we will not approach them.
Who supports the end customer?
You hold the end-customer relationship and provide their first point of support. DevSpark supports your team and the platform. We agree support responsibilities and escalation arrangements as part of the commercial scope.
What analytics run on the video?
Object detection, running at the edge on the gateway in the building rather than in a data centre: people, vehicles and object classes, with a confidence figure and the version of the model stamped on every event, and intrusion zones, line crossing and loitering across recorded review. Number plate and face recognition are on the roadmap and extend the same pipeline. Ask us where a specific analytic stands before you write it into a specification and we will tell you in writing — that answer is worth more to both of us than a brochure claim.
Is DevSpark VMS ONVIF conformant?
DevSpark Ltd is an ONVIF member, and the platform interoperates with cameras that are themselves ONVIF conformant, using the published specifications for discovery, streaming and PTZ. The platform itself has not been through ONVIF conformance testing and carries no Profile claim of its own, so if a specification demands a conformance-tested VMS we would tell you before you wrote us into a bid.
Does a white-label licence transfer ownership of the software?
No. A white-label licence lets you operate DevSpark VMS under your brand; DevSpark retains the platform IP. If you need a separately commissioned platform, project-specific source ownership, repositories, cloud accounts and third-party dependencies are defined in the development agreement. Custom development starts with a scoped discovery engagement.
Where does the data live?
Recording stays on the appliance on the customer network. The cloud layer provides the interface, identity and an index of what exists, and never receives camera credentials. DevSpark Ltd is UK-owned, and the platform is designed, built and supported from Manchester.
Put it on one site and judge it against what you use now
We commission the first one free, alongside whatever is already there, branded however you want it. If it is not right you take it out and nothing is owed.
Engineer to engineer. No handoffs.