VMS Vendor Landscape 2026: Who Leads and How to Read It

Updated October 2026: 2026 market-share data (Omdia, Novaira), ONVIF Profile V for cloud VMS, the FCC’s October 2025 Covered List rules and the EU AI Act’s new December 2027 high-risk date.

Why this matters

If you are choosing a VMS for a camera estate or scoping a surveillance product, the vendor decision looks like a shootout between famous names, and that framing quietly leads you wrong. The market is consolidating fast — Motorola absorbed Avigilon, Canon owns Milestone, and in December 2025 Eagle Eye Networks and Brivo merged into a single cloud-native company — so a shortlist built on today's logos can be out of date within a quarter. What does not expire is the structure: the four families and the four axes below behave the same way no matter who owns whom. Learn to read the market by structure and you can evaluate a vendor in an afternoon, defend the choice to a CFO, and avoid the trap of buying a famous name that fits someone else's problem.

The VMS vendor landscape in 2026: the short answer

The VMS vendor landscape is the market for video management system software: the platforms that record, manage and analyse many security cameras at once. (It is not the vendor management system market from staffing and procurement, which shares the acronym.) In October 2026 it splits into four families — enterprise on-prem, cloud-native video surveillance as a service (VSaaS), open hybrid and custom-built — and the family decides your cost shape, lock-in and who owns the AI before any brand does.

The largest VMS vendors are Genetec, ranked the global VMS leader by both Omdia and Novaira Insights in August 2026, and Milestone Systems (Canon Group), which reported EUR 298 million in 2025 net revenue, up 10%. Behind them sit Motorola Solutions’ Avigilon, Bosch, Hanwha Vision and Axis on the on-prem side, and Verkada, Brivo–Eagle Eye, Rhombus and Spot AI in the cloud. SNS Insider (February 2026) sizes the 2025 VMS software market at $14.02 billion, still 71% on-premises.

Table A. Who is who in the VMS market, October 2026. Rankings are vendor-reported readings of analyst data; each firm measures a different slice. For a ranked, side-by-side list, see our top video surveillance software companies comparison; this article explains how to read the market behind any list.

Read families, not logos

The single most useful move in this whole market is to stop ranking vendors and start sorting them. Before you compare Milestone against Genetec against Verkada, notice that those three are not really competing for the same job — they sit in different families that make different trade-offs on cost, control, and who runs the servers. Pick the family that fits your deployment first; only then does the vendor-versus-vendor comparison inside that family become meaningful.

There is a practical reason to lead with families rather than names: names move, structure stays. A list that says "the five best VMS platforms" is a snapshot of a market that reshuffles constantly through mergers and acquisitions. The four-family map, by contrast, has been stable for years and survives every merger, because a company changing hands does not change whether its product installs on your servers or runs from a vendor's cloud. If you only remember one thing from this article, remember to ask "which family?" before "which brand?"

Figure 1. The four families of VMS. Sort a vendor into a family first; the family fixes the cost shape, the lock-in, and who owns the AI long before the brand name matters.

The four families of VMS

Here is the map. Each family is a different answer to the question "where does the software live, and who keeps it running?"

Enterprise on-prem is the traditional model: you license a heavyweight platform and run it on your own servers, inside your own network. Genetec Security Center, Milestone XProtect, Bosch BVMS, and Avigilon Unity live here. The strength is scale and depth — these platforms run thousands of cameras across many sites and integrate with access control, intrusion alarms, and dispatch systems through mature extension kits. The cost is weight: real servers, real storage, an annual support fee, and usually a security integrator to roll it out. Think of it as owning the building and the boiler room.

Cloud-native video-surveillance-as-a-service (VSaaS) flips that around. The vendor runs the servers; you connect cameras (often the vendor's own) and operate everything from a browser and a phone. Verkada, Eagle Eye Networks (now merged with Brivo), Rhombus, Spot AI, Avigilon Alta and Milestone’s Arcules are the names here. The strength is that there is nothing to install and the software updates itself, so artificial-intelligence features — the automated detection of people, vehicles, and events — arrive on day one. The cost is a per-camera monthly fee that never stops, plus a dependence on the vendor's cloud and your upload bandwidth. This is renting a serviced apartment: you move in today and the landlord fixes the plumbing.

Open hybrid is the mid-market middle ground: commercially licensed software that leans on open standards, runs on commodity hardware you choose, and ships a developer kit so integrators can extend it. Network Optix Nx Witness, Digifort, Hanwha WAVE, and Luxriot EVO sit here. The strength is affordability and camera choice — these platforms talk to almost any camera that speaks the common industry standard, ONVIF, and let you keep your recordings on your own disks. The trade-off is a smaller analytics and integration ecosystem than the enterprise giants. It is the apartment you are allowed to renovate.

Custom-built is the fourth family, and it is a real option, not a dare. Here you assemble a system on proven components — an open recording engine, standard media pipelines, ONVIF camera discovery, an artificial-intelligence runtime — and write only the workflow layer that is unique to you. You reach for it when an off-the-shelf product cannot model your workflow, when you need to own proprietary analytics, or when you sell surveillance software and the VMS is your core product. The trade-off is a build-and-maintain commitment you carry yourself. We cover this family in depth in build vs buy vs customize a VMS and the product-team version in custom vs off-the-shelf VMS.

The four families read fastest side by side. Note the two columns that matter most for a buyer and that vendor listicles routinely omit: the deployment model, and whether the platform ships an open developer kit you can build on.

Table 1. The four VMS families across the dimensions a buyer actually weighs. No row crowns a single winner — the right family is the one whose trade-offs match your deployment. Pricing is illustrative; channel partners discount enterprise quotes heavily above 100 cameras.

The four axes you actually compare on

Once a vendor is sorted into a family, four axes separate the genuine differences. Run any product through all four and the comparison stops being a popularity contest.

Where the software runs. On-prem, cloud, or hybrid is the first axis because it cascades into everything else — bandwidth, who patches the servers, where your video physically sits, and whether a network outage blinds you. The deployment-model decision deserves its own treatment; we give it one in on-prem, cloud, and hybrid VMS. For reading the vendor market, just note that family already tells you most of the answer.

How open it is. Openness is two separate questions. First, can the platform talk to cameras from any maker? That is the ONVIF question, and it protects you from being trapped by your camera fleet. Second, can your team build on the platform through a documented software development kit — the published set of tools and programming interfaces, called an SDK, that lets outsiders add features? An open SDK is the difference between a product you can extend and one you can only configure. Enterprise and open-hybrid platforms tend to be strong here; pure VSaaS tends to be a closed box with an API the vendor controls.

Who owns the AI. Every vendor says "AI" now, so the useful question is not whether a platform has analytics but who controls them. With VSaaS, the analytics are the vendor's — you get what ships, when it ships, at the accuracy it delivers, and you cannot tune the model. With enterprise platforms, you can usually add third-party analytics through the SDK. With a custom build, you own the model outright. This matters when detection quality is your differentiator, because analytics accuracy is a precision-and-recall range that depends on scene, lighting, and tuning — never a single guaranteed number — so the freedom to tune it is worth real money. The catalogue of what these analytics actually do is in the video-analytics map.

Which rules it satisfies. Procurement law and privacy law quietly delete vendors from your shortlist before any feature comparison begins. We treat this as its own axis below, because in this market compliance is not a footnote — it is a filter.

Figure 2. The same market as a positioning map. The vertical axis is where the software runs; the horizontal axis is how open it is. Families cluster in regions — which is why "which family?" answers most of "which vendor?".

The money has two shapes, and the family decides which

Cost is where the family choice shows its teeth, because the four families do not just cost different amounts — they cost in different shapes. Get the shape wrong and a quote that looked cheap becomes the expensive option two years in.

Enterprise on-prem and open hybrid are a capital expense: a one-time license per camera channel, plus servers and storage, plus an annual support fee that is a fraction of the license. You pay a lump up front and a little each year. Cloud-native VSaaS is an operating expense: a recurring fee per camera per month that bundles software, cloud storage, and updates, and that bills forever. Neither shape is wrong; they suit different balance sheets. The mistake is comparing a one-time number against a monthly number without putting them on the same five-year footing.

Walk the arithmetic out loud once. Take a 200-camera estate and compare an open-hybrid CapEx model against a VSaaS OpEx model over five years. Hardware and cameras cost roughly the same in both, so leave them out.

on-prem_5yr = (license_per_cam × cameras) + (annual_support × cameras × years)
on-prem_5yr = ($120 × 200) + ($25 × 200 × 5)
on-prem_5yr = $24,000 + $25,000 = $49,000

vsaas_5yr   = monthly_per_cam × cameras × 12 × years
vsaas_5yr   = $25 × 200 × 12 × 5 = $300,000

At 200 cameras over five years the VSaaS bill is several times the on-prem one — yet VSaaS still wins for many buyers, because it removes the servers, the IT staff, and the integrator, and it puts modern AI on every camera on day one. The point is not that one is cheaper; it is that the shapes cross. Below a certain camera count and time horizon, the convenience of VSaaS is worth its premium; above it, the per-camera-per-month meter overtakes a one-time license. Find that crossover for your own numbers before you sign, because it is the real decision hiding behind the brand names. The full treatment is in the surveillance cost model.

Figure 3. The two cost shapes (illustrative). CapEx is a lump up front and a slow climb; OpEx starts cheap and rises forever. They cross — and where they cross, not the brand, is the decision.

Compliance is a market filter, not a footnote

In most software markets you compare features first and check compliance later. Surveillance inverts that, because two kinds of law can remove a vendor from contention before you ever open its datasheet. This is engineering and procurement guidance, not legal advice; confirm specifics with qualified counsel.

The first filter is procurement law. In the United States, Section 889 of the 2019 National Defense Authorization Act (Public Law 115-232) prohibits federal agencies and federal-grant recipients from buying video-surveillance equipment from five named Chinese manufacturers — Huawei, ZTE, Hytera, Hikvision, and Dahua — and their affiliates, where it serves security purposes. The implementing Federal Acquisition Regulation rule extended that prohibition to contractors who merely use such equipment anywhere in their operations. The effect on the vendor landscape is blunt: if you sell to government, take federal grant money, or sit in a federal supply chain, an entire tier of low-cost hardware is simply off the table, and the vendors who lead with "NDAA-compliant" messaging — Axis, Hanwha, Avigilon, Bosch, Verkada — are signalling exactly this. The Federal Communications Commission tightens the same filter for every US buyer, not just government ones: since its November 2022 order it grants no new equipment authorizations to Covered List vendors such as Hikvision and Dahua, and on 28 October 2025 it voted unanimously for rules that let it bar continued import and sale of previously authorized covered devices and close the “modular transmitter” loophole for covered components.

The second filter is privacy law, and it bites hardest on analytics. Under the European Union's General Data Protection Regulation (GDPR, Regulation (EU) 2016/679), running face recognition or behavioural analytics triggers a mandatory Data Protection Impact Assessment under Article 35, and a face template counts as special-category biometric data under Article 9. In the United States, Illinois' Biometric Information Privacy Act (BIPA, 740 ILCS 14) requires written consent before you capture a face template and lets the people in the footage sue — the kind of exposure that produced a $650 million Facebook settlement. An August 2024 amendment (SB 2979) now counts repeated scans of the same person by the same method as one violation and allows electronic-signature consent, so the exposure is smaller than it was, not gone. In the EU, the AI Act has prohibited untargeted scraping of facial images and, with narrow exceptions, real-time remote biometric identification by police in public spaces since February 2025; the Digital Omnibus (Regulation (EU) 2026/1744, in force since 27 July 2026) moved the stand-alone high-risk obligations, which include biometric identification systems, from 2 August 2026 to 2 December 2027. So a VSaaS platform whose headline feature is built-in face recognition is not automatically a shortlist winner; in some jurisdictions it is a liability you must gate before you switch it on. We treat these rules in depth in GDPR for video surveillance and BIPA and US biometric privacy law; for the market-reading purpose here, treat compliance as the first filter, not the last.

Openness: what ONVIF guarantees, and what it doesn't

Because "open" is the most abused word in vendor marketing, it pays to know precisely what the industry's interoperability standard does and does not promise. ONVIF is the common language that lets cameras and video software from different makers work together, and its governing body is explicit that "conformance to profiles is the only way that ensures compatibility between ONVIF conformant products." For video, the relevant profiles are S and T for live streaming, G for recording, and M for analytics metadata.

The newest profile goes straight at the cloud family’s lock-in. In July 2026 ONVIF published Profile V as a release candidate for camera-to-cloud VMS: a conformant camera opens a secure outbound connection to any conformant cloud VMS, streams live video over WebRTC, pushes events and encrypted recordings to cloud storage, and authenticates through a mandatory OAuth 2.0 security add-on. ONVIF expects to finalize it by the end of 2026. Until it ships and vendors certify against it, assume a VSaaS platform’s camera-to-cloud path is proprietary, and ask each cloud vendor whether it plans Profile V conformance.

The trap is assuming "ONVIF-conformant" means "fully interchangeable." It does not. ONVIF guarantees a baseline — the specific profile both the camera and the software conform to — and advanced features routinely sit outside that baseline. Edge analytics events, advanced pan-tilt-zoom tours, and proprietary codecs typically need the vendor's own SDK, not ONVIF. So when a vendor says "we support ONVIF," the right follow-up is "which profiles, and which of your advanced features fall back to your SDK?" Keep "baseline interoperability" and "full feature parity" as separate ideas and you will not be surprised after purchase. The mechanics are covered in ONVIF explained for engineers; the standard also reminds integrators that "compliance to regulations is outside the scope of ONVIF," so the legal filters above remain your responsibility regardless of how open a platform is.

Figure 4. The openness boundary. ONVIF guarantees a baseline both devices conform to; the advanced, differentiating features usually live outside it, behind a vendor SDK.

The market is consolidating — read motion, not snapshots

A vendor landscape is a moving picture, and the motion tells you as much as any single frame. Four patterns are worth tracking as you read the market.

First, the enterprise giants are inside larger companies now. Genetec remains independent and, in reports published in August 2026 on 2025 data, both Omdia and Novaira Insights rank it the global VMS leader: Omdia puts its 2025 growth at 20% against 13.3% for the video software and VSaaS market, and Novaira gives it a fifteenth consecutive year at the top in the Americas. Milestone has been part of the Canon Group since 2014 and in 2025 folded its BriefCam analytics and Arcules VSaaS businesses into the main company, reporting EUR 298 million in net revenue, up 10%. Avigilon is a Motorola Solutions brand, sold today as Avigilon Unity (on-prem) and Avigilon Alta (cloud). Ownership shapes roadmap, and roadmap shapes the product you will live with for years.

Second, cloud-native challengers are consolidating into platforms. The clearest signal came in December 2025, when Eagle Eye Networks and the access-control company Brivo merged into a single cloud-native physical-security company, operating under the Brivo name with Eagle Eye founder Dean Drako as CEO, and pitching one platform for video, access, and intrusion. Verkada pushes the same bundle from the other side: in January 2026 a CapitalG-led round valued it at $5.8 billion, with more than 30,000 customer organizations on its cloud platform. The lesson for a buyer is that the VSaaS family is racing to bundle video with the rest of the security stack, so "just a camera platform" is becoming "the whole building's security."

Third, open-source recording engines are now credible building blocks. Projects such as ZoneMinder (in production since 2002) and Frigate (built around on-device AI detection) are mature enough to anchor a custom build, which is part of why the custom family is no longer exotic. None of this changes the four-family map — it populates it. Read the motion, and a merger becomes information rather than a reason to redo your shortlist.

Fourth, the money is still mostly on-prem, even though the growth is in the cloud. SNS Insider (February 2026) sizes the 2025 VMS software market at $14.02 billion, forecasts 14.94% annual growth to $42.72 billion by 2033, and still gives on-premises deployments 71% of 2025 revenue, with North America the largest region at 36%. Analyst firms count VSaaS, hardware bundles and services differently, so treat any single “market share” chart, including a vendor’s own, as one reading of one definition.

A common mistake to avoid

The costliest pattern we see is shortlisting by brand fame instead of by family fit. A team reads a "best VMS software 2026" listicle, shortlists the three most-mentioned names, and discovers only after the demos that two of them are in the wrong family entirely — an enterprise on-prem giant pitched at a 25-camera single site, or a per-camera-per-month cloud platform pitched at a 2,000-camera estate that will hemorrhage money on the monthly meter. The fix is to choose the family before you collect names, then shortlist only inside it. A close cousin of this mistake is buying cameras before choosing the VMS. Cameras outlive the recorder, so a fleet bought without checking ONVIF conformance and procurement-law status can lock you out of the very family you later decide you need. Decide the family, set the compliance filters, then let those two constraints generate your shortlist — not a magazine's ranking.

For the commercial overview of the market this map sits inside, see Fora Soft's video surveillance management systems playbook and the rundown of modern VMS software features.

VMS vendor market: quick answers

Who are the largest VMS providers?

Genetec and Milestone Systems are the two largest VMS software vendors: Omdia and Novaira Insights ranked Genetec the global leader in August 2026, and Milestone (Canon Group) reported EUR 298 million in 2025 revenue. Motorola Solutions’ Avigilon, Bosch, Hanwha Vision and Axis follow on the on-prem side, and Verkada leads the cloud-native VSaaS family.

What is the VMS market share by vendor?

No analyst publishes free vendor percentages, so public “market share” claims are vendors’ own readings of Omdia or Novaira data. What is public: Genetec grew 20% in 2025 against 13.3% for the video software and VSaaS market (Omdia, August 2026), and SNS Insider sizes the whole VMS software market at $14.02 billion for 2025, 71% of it on-premises.

Is this the same VMS as a vendor management system?

No. Here VMS means video management system, the software that records and manages security cameras. Vendor management systems for contingent staffing are a separate market with separate vendors and analyst rankings.

Which VMS platforms let us use cameras and access control from multiple brands?

Open-architecture platforms in the enterprise and open-hybrid families: Genetec Security Center unifies video and access control, Milestone XProtect 2026 R1 adds AXIS Secure Entry access control inside the Smart Client, and Network Optix, Hanwha WAVE, Digifort and Luxriot record almost any ONVIF camera. Check ONVIF Profile S/T/G conformance for cameras and Profile A/C/D for access control before you sign.

How do I evaluate vendors for a hybrid on-prem and cloud deployment?

Score each vendor on where recordings live, what happens to recording when the internet link drops, and whether on-prem and cloud tiers share one licence and one user directory. Then run the five-year CapEx-versus-OpEx math above for your own camera count.

What licensing models do VMS vendors use?

On-prem and open-hybrid vendors sell a one-time licence per camera channel plus an annual software support plan; VSaaS vendors charge a recurring fee per camera per month that bundles software, cloud storage and updates. Many enterprise vendors now sell both, so ask for both quotes on the same five-year footing.

Where Fora Soft fits in

Fora Soft has built real-time video, streaming, and computer-vision software since 2005, across 250+ shipped projects, and we are usually called in at the right-hand edge of this map — the open-hybrid and custom families, where off-the-shelf products stop fitting. The first thing we do is talk teams out of building when an off-the-shelf family is the right answer, because reinventing recording is expensive and someone solved it twenty years ago. When a custom or composable build genuinely fits — a regulated workflow, proprietary analytics, a platform you need to own — the discipline is the one this whole section preaches: design for how the system behaves at full camera load and on a bad-network day first, with realistic detection precision and recall under real lighting, then the feature list. A platform that records every frame under load and federates across sites beats one that demos beautifully and stalls at 300 cameras. When the answer is custom, our video management software development team builds the composable platform, and our AI video recognition engineers add the proprietary detection, tracking and ANPR layer on top.

The handbook

Fora Soft Video Engineering Handbook

We wrote a seven-volume series that works through the whole video stack — encoding, delivery, audio and AI — so an engineer who has read it can design and build a surveillance platform and judge any vendor family on how its system really behaves. Volume 7 covers the two filters this article sorts the market by: what AI video costs to run in production and how GDPR-style rules shape the architecture. Volume 6 explains the detection models behind “who owns the AI”, and volume 1 gives you the codec and bitrate arithmetic under every storage and upload bill. Written by Nikolay Sapunov, CEO at Fora Soft.

Browse the handbook on Amazon →7 volumes · Kindle & paperback

See our case studies

References

1. ONVIF — "ONVIF Profiles" (an ONVIF profile has a fixed set of features a conformant device and client must support; "conformance to profiles is the only way that ensures compatibility between ONVIF conformant products"; video systems use Profiles D, G, M, S, and T; "compliance to regulations… are outside the scope of ONVIF." Page modified 2026-07-10; lists Profile V as a release candidate). Primary standard (tier 1). https://www.onvif.org/profiles/
2. U.S. Government / GSA — "Federal Acquisition Regulation: Prohibition on Contracting With Entities Using Certain Telecommunications and Video Surveillance Services or Equipment" (the FAR final rule implementing NDAA FY2019 Section 889(a)(1)(B); extends the prohibition to contractors that use covered equipment from Huawei, ZTE, Hytera, Hikvision, and Dahua). Primary regulatory document (tier 1). https://www.federalregister.gov/documents/2020/07/14/2020-15293/federal-acquisition-regulation-prohibition-on-contracting-with-entities-using-certain
3. U.S. Election Assistance Commission — "What is Section 889 of the FY 2019 NDAA?" (plain-language summary of the Section 889 covered-equipment prohibition and the named entities, with the FY2019 NDAA Pub. L. 115-232 reference). Issuing-agency guidance (tier 2). https://www.eac.gov/what-section-889-fy-2019-ndaa
4. European Union — "General Data Protection Regulation (Regulation (EU) 2016/679)" (Art. 9 treats biometric data used to uniquely identify a person as special-category data; Art. 35 requires a Data Protection Impact Assessment for high-risk processing such as systematic monitoring or large-scale biometric analytics). Primary law (tier 1). https://eur-lex.europa.eu/eli/reg/2016/679/oj
5. IEC — "IEC 62676 series: Video surveillance systems for use in security applications" (specifies minimum requirements and recommendations across the system lifecycle; EN IEC 62676-4:2025 covers application guidelines including information security and data privacy). Primary standard (tier 1). https://webstore.iec.ch/en/publication/34391
6. Fora Soft — "Video Surveillance Management Systems: The 2026 Buyer & Builder Playbook" (the market has split four ways — enterprise on-prem (Genetec, Milestone, Bosch, Avigilon), cloud-native VSaaS (Verkada, Eagle Eye, Rhombus, Spot AI), open hybrid (Network Optix Nx Witness, Digifort, Hanwha WAVE, Luxriot), and custom-built; pick the family first, then the vendor; on-prem ~$50–$300/channel one-time, VSaaS ~$10–$50/camera/month, open hybrid ~$50–$150/channel, custom $80K–$300K MVP; NDAA/GDPR/BIPA reshape the architecture). First-party engineering (tier 3); the required winning-blog outbound target. https://www.forasoft.com/blog/article/video-surveillance-management-systems
7. Genetec — "Independent analyst firms rank Genetec as global leader in video management software" (August 2026, on 2025 data: Omdia and Novaira Insights rank Genetec the global VMS leader; Omdia: Genetec grew 20% vs 13.3% for the video software and VSaaS market; Novaira: 15th consecutive year first in the Americas). First-party / analyst-cited (tier 4). https://www.genetec.com/press-center/press-releases/2026/08/independent-analyst-firms-rank-genetec-as-global-leader-in-video-management-software
8. SDM Magazine — "Brivo and Eagle Eye Networks Merge" (29 December 2025: the merged company operates under the Brivo name; Dean Drako, founder of Eagle Eye Networks and chairman of Brivo, serves as CEO; Steve Van Till as president). Trade press (tier 5). https://www.sdmmag.com/articles/104970-brivo-and-eagle-eye-networks-merge
9. ONVIF — "ONVIF Releases Profile V Draft" (9 July 2026: Profile V release candidate for camera-to-cloud VMS; outbound device connection, WebRTC live streaming, events, encryption before upload to cloud storage, mandatory OAuth 2.0 Security Add-on; finalization expected by end of 2026). Primary standards body (tier 1). https://www.onvif.org/pressrelease/onvif-releases-profile-v-draft/
10. Milestone Systems — "Milestone Integration Platform (MIP) SDK documentation" (the MIP SDK enables plug-in integrations inside XProtect and component integrations that share video and data; evidence of the open-SDK strength of the enterprise on-prem family). First-party engineering (tier 3). https://doc.developer.milestonesys.com/mipvmsapi/
11. SNS Insider via GlobeNewswire — "Video Management Software Market Size Worth USD 42.72 Billion by 2033" (21 February 2026: USD 14.02B in 2025, 14.94% CAGR 2026–2033, on-premises 71% share in 2025, North America 36%). Institutional/analyst (tier 5). https://rss.globenewswire.com/news-release/2026/02/21/3242205/0/en/Video-Management-Software-Market-Size-Worth-USD-42-72-Billion-by-2033-SNS-Insider.html
12. Milestone Systems — "Milestone grows net revenue to EUR 298 million in 2025 and invests in the intelligent video era" (26 March 2026: EUR 298M / DKK 2.2B net revenue, +10%; BriefCam and Arcules integrated into Milestone in 2025; part of the Canon Group since 2014). Primary company announcement (tier 3). https://www.milestonesys.com/company/news/press-releases/milestone-grows-invests-intelligent-video-era/
13. Milestone Systems — "Milestone Strengthens Security Operations and Cloud Capabilities with XProtect 2026 R1 and Arcules Update" (2026: AXIS Secure Entry access control inside XProtect Smart Client; Device Pack 14.1 with 16,300+ verified devices; Arcules camera-to-cloud). Vendor release notes (tier 3). https://www.milestonesys.com/press-releases/2026-r1-and-arcules-updates/
14. EURO SECURITY — "New round of financing raises Verkada's valuation to $5.8 billion" (30 January 2026: CapitalG-led round; 30,000+ organizations; 2M+ devices online in 171 countries). Trade press (tier 5). https://euro-security.de/en/new-round-of-financing-raises-verkadas-valuation-to-5-8-billion
15. U.S. Federal Communications Commission — press release on the Second Report and Order, FCC 25-71, ET Docket No. 21-232 (28 October 2025: process to prohibit continued import and sale of previously authorized Covered List devices; closes the modular transmitter loophole). Primary regulator (tier 1). https://docs.fcc.gov/public/attachments/DOC-415131A1.pdf
16. Davis Wright Tremaine — "Illinois Revises Biometrics Law To Reduce the Prospect of 'Ruinous' Damage Awards" (SB 2979 signed 2 August 2024: repeated collection from the same person by the same method is one violation; electronic signature consent). Legal analysis (tier 4). https://dwt.com/blogs/privacy--security-law-blog/2024/08/illinois-bipa-biometrics-law-amended-for-damages
17. EU AI Act information resource — "Digital Omnibus on AI" (Regulation (EU) 2026/1744, in force 27 July 2026; stand-alone Annex III high-risk obligations deferred from 2 August 2026 to 2 December 2027; links the Official Journal text). Legal reference (tier 4). https://www.euaiact.com/digital-omnibus-ai
18. ZoneMinder — project documentation (open-source video-surveillance / NVR software in production since 2002; an example of a mature open recording engine usable as a composable component in a custom build). Educational/community (tier 6). https://zoneminder.readthedocs.io/en/latest/
19. Frigate — project documentation (open-source NVR built around on-device AI object detection; an example of a modern composable recording component). Educational/community (tier 6). https://frigate.video/