Hardware & device ecosystem
Software command for the real devices on site
Duall Master is not only software. It connects Duali access hardware and compatible third-party building systems so doors, readers, cameras, intercoms, gates, lifts, parking, sensors, and controllers can feed the same command platform.
Connects
Duali hardware
Connects
Third-party integrations
Connects
One operating timeline
Edge to command
Devices keep the site moving. Duall Master turns their signals into operator context, governed actions, and audit history.
Two device sources
Bring Duali hardware and compatible third-party devices into one ecosystem.
The buyer story is simple: use the devices that make sense for the site, then connect them to one identity, event, policy, and audit foundation.
Duali portfolio
Native access hardware
Access terminals
Face, card, QR, PIN, and touch-screen authentication terminals for lobbies, doors, and controlled areas.
Readers and credential devices
Card, NFC/RFID, and biometric readers such as DQ-200, DQ-100, and HF-RA08 references from prior Duali deployments.
Door and lift access points
Terminals, readers, relays, controllers, and site access points aligned to doors, gates, lifts, and turnstiles.
Offline-first edge logic
Supported access terminals are designed to keep local rules and event queues so sites can continue operating during connectivity issues.
Third-party ecosystem
Compatible site systems
Cameras / VMS
Integrates with compatible camera and VMS environments where streams, clips, and event context can be validated for the deployment.
Intercom systems
Connects intercom workflows to identity, visitor, access, and operator response when project-specific connector scope is confirmed.
Gates, turnstiles, lifts
Works with compatible access equipment, controllers, and relay paths through deployment-specific integration validation.
Parking equipment
Supports parking flows around compatible LPR, gate, payment, or parking systems through phased integration design.
Sensors and controllers
Can bring compatible door sensors, controllers, alarms, and site signals into the same operating picture.
Enterprise / building systems
APIs, event flows, and connectors support surrounding systems without claiming one universal compatibility list.
Edge-to-platform flow
Different devices. One command platform.
Duali hardware and validated third-party systems can feed the same operating model: provisioned endpoint, secure connection, realtime signal, platform context, operator action, and audit.
Duali devices
Terminals, readers, controllers
Third-party systems
Cameras, intercom, parking, gates
Device gateway
Secure onboarding, MQTT/events, adapters
Duall Master
Identity, policy, realtime status, audit
Operators
Monitor, investigate, control, report
Buyer-facing model. Exact hardware support, protocol adapters, and command permissions are validated per customer deployment.
Platform capabilities
The platform does the boring hard parts buyers actually need.
Provision
QR or approval-based onboarding assigns devices to the right company, site, zone, and role in the platform.
Secure connection
A device gateway and secure messaging layer connect supported endpoints to Duall Master without exposing operator workflows to raw device plumbing.
Live status
Heartbeat, online/offline state, and realtime events help operators see what is happening now.
Command / control
Where supported, operators can send governed actions such as sync, unlock, snapshot, configuration, or diagnostic commands.
Audit history
Device events, operator actions, policy changes, and investigation context remain reviewable.
Integration-ready
Third-party hardware is validated per project using APIs, events, protocol adapters, and partner delivery where needed.
How to evaluate fit
Start with the site's devices, not a generic compatibility promise.
The professional answer is to inventory the device estate, separate native Duali hardware from third-party equipment, validate connectors, then design the rollout path module by module.
Next step
Discuss hardware and integration requirements
Review Duali device options, existing third-party hardware, provisioning approach, realtime event needs, and deployment-specific connector validation.