Web console
LiveOne command surface for operators, admins, and security teams.
Platform foundation
One identity DB. One audit log. One event spine.
Duall Master is platform-based at the core and module-based in adoption. The same identity model, device fabric, NATS event spine, immutable audit hypertable, AI Assistant, and deployment controls back every module — so the modules can stay focused without becoming silos.
Shared command surface
Platform overview
Foundation capabilities
Seven primitives — every module is built on the same seven.
Identity, devices, events, audit, AI, integrations, and deployment. Each module uses these instead of recreating its own — which is why adding a second or third module doesn't double your operational surface area.
01
Identity graph
Companies, tenants, users, roles, credentials, zones, and permissions stay aligned across modules.
02
Device fabric
Doors, gates, cameras, intercoms, terminals, and future endpoints connect to the same site model.
03
Realtime event spine
Access, visitor, parking, video, attendance, and operator signals resolve into one timeline.
04
Audit history
Policy changes, overrides, reviews, and command actions remain traceable for operations and investigation.
05
AI Assistant
Natural-language interface for the whole platform — operators ask in English or Tiếng Việt (Korean rolling out) and the assistant explains, previews, and executes safely with full audit.
06
Integration layer
APIs, webhooks, event flows, and partner connectors support phased modernization.
07
Deployment control
Cloud, on-premise, and hybrid models support different site policies and risk postures.
Platform architecture
One shared foundation beneath every module and site workflow.
Duall Master connects apps, modules, devices, data, integrations, and deployment controls through one platform foundation. The exact connectors and hosting model are validated per customer project.
01 / Apps and operators
Role-specific surfaces, one operating picture
Mobile and resident apps
By deploymentRole-specific workflows for admins, residents, guards, and staff.
Vertical experiences
ConfigurableOffice, residential, school, factory, and campus views without splitting the platform.
02 / Product modules
Customers start with the modules they need
Access Control
Doors, credentials, schedules, zones, and access history.
Visitor Management
Invites, approvals, badges, hosts, and temporary access.
Attendance
Clock events, shifts, leave, and workforce reporting.
Parking
Vehicles, sessions, gates, ANPR-fed flows, and site movement.
VMS
Cameras, live view, clips, and event-linked investigation.
Video Intercom
Roadmap / project scopeDoor-station and call workflows where required.
03 / Shared platform foundation
The common backend truth that prevents module silos
Identity + permissions
Tenants, companies, users, roles, credentials, and RBAC.
Site + zone model
Buildings, floors, areas, doors, cameras, gates, and shared location context.
Realtime event spine
Device signals, module events, operator actions, and WebSocket updates.
Audit + governance
Reviewable policy changes, overrides, access events, and operational history.
API + integration layer
Gateway-controlled APIs, partner connectors, and project-specific integrations.
Deployment control
Cloud, on-premise, and hybrid rollout depending on customer risk posture.
04 / Devices, data, integrations, deployment
The physical site and surrounding systems stay connected
Access devices
Terminals, controllers, doors, gates, lifts, and turnstiles.
Video + intercom
Cameras, RTSP streams, clips, and door-station context.
External systems
HR, reporting, tenant apps, partner systems, and public APIs when validated.
Data stores
Operational records, event history, media objects, cache, and tenant assets.
Technical grounding behind the simplified diagram
- Current backend is a Go service plane including auth, identity, access, device gateway, audit, visitor, parking, VMS, and attendance services.
- Device connectivity uses MQTT through EMQX; internal events use NATS JetStream; data is stored in Postgres/TimescaleDB with MinIO for objects and MediaMTX for video paths.
- Access terminals are designed offline-first: devices can make local decisions while the platform syncs rules, receives events, and supports investigation.
Hardware ecosystem
The platform connects software workflows to the real devices on site.
Duali access terminals and readers, plus compatible third-party cameras, intercoms, gates, lifts, turnstiles, parking equipment, sensors, and controllers feed into the same identity model, realtime event spine, operator UI, and audit hypertable described above.
Device onboarding and provisioning
Secure device gateway and MQTT/event layer
Realtime status, events, and history
Deployment-specific third-party connector validation
Shared foundation in use
Module view
Why it matters
Modules can start focused without becoming silos.
One identity DB across users, credentials, roles, companies, and sites — add a module without re-onboarding people.
One realtime event spine (NATS JetStream) so cross-module activity resolves into one operating picture.
One operator UI so security, reception, and facilities do not switch tools to do their job.
One AI Assistant that reaches every module, with permissioned search, review, and summarization.
One deployment model that supports cloud, on-premise (with Ollama), and hybrid configurations.
One extension path so new modules and vertical experiences grow from the same core.
Cloud rollout for speed and portfolio reach
Faster start, managed operations, default Anthropic Claude LLM. Best for greenfield deployments.
On-premise control for sensitive sites
Full stack inside your perimeter — TimescaleDB, NATS, EMQX, MediaMTX, MinIO, Ollama. Required for residency-bound tenants.
Hybrid modernization when cutover risk matters
Control plane in cloud, sensitive workloads on-prem. Per-tenant LLM profile lets one portfolio mix postures.
Next step
See the platform in action
Review how Duall Master connects modules, events, operators, integrations, and deployment requirements.