3 Questions Security Teams Asked About Our Unified Physical Security Platform And Our Honest Answers

When we hosted our recent WaveFusion webinar, we expected questions about features. What we got instead were questions about architecture, resilience, and real-world deployment — the kind of questions that tell you people aren't just browsing, they're planning.

The engagement data told its own story: 32 security professionals from eight countries (Canada, US, Netherlands, Kenya, Saudi Arabia, Spain, UK, and Venezuela) stayed for an average of over 50 minutes. During that 60-minute session, the questions that came in weren't surface-level. They were the questions of teams actively planning their next platform decision.

If you’re evaluating unified security platforms in 2026, you’re probably asking the same things. Here are the three most critical questions from the session, and our honest answers.

Q1: "For organisations with existing access control and video systems — what does a typical migration to WaveFusion look like, and how disruptive is it?"

This is the question everyone wants answered but not everyone asks out loud. Migration anxiety is real — particularly when you've invested heavily in existing hardware.

The honest answer: if you're running Mercury controllers (MP or LP series), migration to WaveFusion is straightforward. Because WaveFusion is cloud-hosted, your integrator can adopt a "Configuration-First" approach. They can build the entire site — controllers, card formats, access levels, floor plans, and cardholder data — in the WaveFusion dashboard before touching a single piece of field hardware.

The data migration itself happens via our GraphQL API or batch import tools, allowing you to clean up legacy data before it hits the new system. When you're ready to switch, the controllers are simply pointed at the WaveFusion hosted environment and the site comes live. On the video side, any ONVIF-compliant cameras connect to Wavestore's VMS without proprietary adapters.

The disruption window isn't measured in weeks. It's measured in minutes.

What you don't have to do: rip out Mercury hardware, replace cameras that already work, or retrain your entire team on a complex thick-client application. WaveFusion is browser-based — every user, from the security director to the junior operator, goes to the same URL.

---

Q2: "A lot of platforms claim to be unified. What's fundamentally different about WaveFusion?"

This question cuts to the core of what we're building — and why. Enrico Bizzaro, our Head of Engineering, answered it during the webinar with a clarity we've been trying to articulate for months:

> *"We're not a simple integration between access control and video. We share API, events, and file storage across a single platform — rather than being an integration like many other competitors."*

The distinction is architectural, not cosmetic. Most platforms that describe themselves as "unified" are actually two separate systems connected by a translation layer (middleware). Access control generates an event. That event is translated, passed to the VMS, and then — hopefully — triggers a camera action. This creates two databases, requires two support teams, and relies on two development roadmaps that may or may not stay aligned.

WaveFusion is different because it was built from the ground up as a single platform. In a unified architecture, there is no "handshake" between systems because there is only one system.

When a card is swiped at a Mercury reader:

1. The access event fires instantaneously on the shared event bus.
2. The video feed responds immediately because it identifies the reader as a native data point.
3. The floor plan updates in the same browser session.
4. The PTZ camera moves to its preset without waiting for a third-party command.
5. The event is logged once in a single, unified database.

For integrators, this means no integration headaches or middleware to maintain. For end users, it means one browser-based interface where everything behaves like it was meant to be together.

Q3: "How does WaveFusion handle resilience and security, especially in environments with limited connectivity or strict policies?"

This question came from the audience during the moderated Q&A — and it's one we take seriously, particularly given we had attendees from regions where consistent internet connectivity isn't always guaranteed.

WaveFusion's cloud infrastructure runs on AWS with multi-availability zone hosting. This provides geographic redundancy and regional data residency options, including GovCloud for organisations with strict compliance requirements. But the real resilience story is at the edge.

Mercury controllers make all access decisions locally. Once a controller is configured and synced with WaveFusion, it stores the full decision database on-board. If the cloud connection drops — whether for seconds or hours — the doors keep working. Access grants, denials, schedules, and card formats all continue to operate based on the last-synced configuration.

For video, Wavestore supports fully on-premise recording with 4,096-bit encryption. This means footage never has to leave the building if your data policies require local storage. You can run cloud-managed access control alongside on-premise video storage — a hybrid model that gives compliance teams exactly what they need without sacrificing cloud management.

The combination is deliberate: cloud-scale management with hardware-grade resilience at the edge. Because in a hospital, a data centre, or a critical infrastructure facility — doors just have to work.

What these questions tell us

The three questions above have a common thread: they're all about trust. Can I trust that migration won't break what already works? Can I trust that "unified" means what it says? Can I trust that the system will work when the internet doesn't?

Those are the questions WaveFusion was designed to answer — not with marketing language, but with architecture.

Book a Personalised WaveFusion Demo

Watch the full webinar recording‍