CustomizationHardware, software and DejaOS development around your project.Explore customization Start with the workflow your operation needs.
Explore common operating directions, then confirm the hardware, software, integration, and delivery scope around your real environment.
Explore the operation first.
Choose the direction closest to your workflow. Each one opens a practical starting point, without assuming that every device or integration fits automatically.
CustomizationHardware, software and DejaOS development around your project.Explore customization Plan the entrance workflow.
Read the selection questions before choosing hardware. Model, firmware, interface and site conditions determine which approach fits.
Access & Visitor Management
Common starting points
Face, card, QR, or multi-credential entry.
Time-bound visitor credentials and reception flows.
Policy-led verification for sensitive zones.
Project scope, platform compatibility and field acceptance must be confirmed for the selected configuration. These scenarios are planning examples, not named customer results.
Discuss this workflowWorkplace & Smart Buildings
Common starting points
Consistent access workflows across locations.
Flexible credentials for shared buildings.
Hardware starting points for wider building systems.
Project scope, platform compatibility and field acceptance must be confirmed for the selected configuration. These scenarios are planning examples, not named customer results.
Discuss this workflowHospitality & Residential
Common starting points
Guest credentials and room access workflows.
Resident and temporary access for properties.
Remote credential management for short stays.
Project scope, platform compatibility and field acceptance must be confirmed for the selected configuration. These scenarios are planning examples, not named customer results.
Discuss this workflowFitness & Membership
Common starting points
Member QR, card, and identity checks.
Credential flows tied to membership status.
Verification starting points for 24-hour venues.
How should a membership entrance be evaluated?
Map the complete path from credential to confirmed passage. Your membership platform, reader and gate have separate roles. Use these checks to select and test the configuration.
- Read the credential
Choose QR, card or face verification for the entrance. Confirm the reader model, firmware, credential format and where identity is checked.
- Check membership permission
Decide which system checks membership status, bookings and access hours. Define what happens when permission is refused or the platform does not respond in time.
- Operate the door or gate
Match the reader output to the controller input. Confirm electrical requirements, wiring, direction and signal timing before connecting the devices.
- Confirm actual passage
A command acknowledgement does not prove that a person passed through. Identify the available door-contact or gate sensor feedback and the events the platform needs to record.
- Expire and reuse credentials
Test an expired membership and a repeated credential. Decide where expiry and reuse rules run, how changes reach the entrance, and what the selected firmware can enforce.
- Test offline operation and recovery
Agree on behaviour during network loss, authorization timeouts and late replies. Verify any local permissions, event storage and reconnection process on the actual configuration.
Project scope, platform compatibility and field acceptance must be confirmed for the selected configuration. These scenarios are planning examples, not named customer results.
Discuss this workflowIndustrial & Workforce
Common starting points
High-throughput workforce verification.
Contractor and employee credential flows.
Access control around operational zones.
Project scope, platform compatibility and field acceptance must be confirmed for the selected configuration. These scenarios are planning examples, not named customer results.
Discuss this workflowParking & Transportation
Common starting points
QR and credential verification at vehicle gates.
Fast scan flows at transport checkpoints.
Operator-facing verification hardware.
Project scope, platform compatibility and field acceptance must be confirmed for the selected configuration. These scenarios are planning examples, not named customer results.
Discuss this workflowSelf-Service & Smart Lockers
Common starting points
Pickup credentials and compartment access.
Embedded scanning and identity touchpoints.
User verification before asset release.
Project scope, platform compatibility and field acceptance must be confirmed for the selected configuration. These scenarios are planning examples, not named customer results.
Discuss this workflowOEM Smart Terminals
Common starting points
Brand, enclosure, and interface adaptation.
Reader modules integrated into a wider product.
Developable UI and workflow exploration.
Project scope, platform compatibility and field acceptance must be confirmed for the selected configuration. These scenarios are planning examples, not named customer results.
Discuss this workflowFollow the layer that needs more work.
These tracks help frame software, management, and project-specific workflows alongside the eight popular directions.
DejaOS Application Development
Shape supported device interfaces, local rules, data handling, and connections in JavaScript, then validate the application on the target hardware.
Discuss this trackSmart Lock Management
Plan credential, property, lock, and operating workflows around the confirmed lock model and management environment.
Discuss this trackVideo Intercom Workflows
Define calling, entry, resident, and property workflows before confirming device, platform, and network requirements.
Discuss this trackSmart Locker Workflows
Connect identity or pickup steps with compartment control and the system that manages each transaction.
Discuss this trackAttendance & Campus
Map enrollment, verification, attendance records, and access rules to the systems and devices used at the site.
Discuss this trackFitness Access
Coordinate member credentials, booking or membership checks, entry feedback, and unattended access requirements.
Discuss this trackConfirm each layer before deployment.
The path stays flexible, but the checks remain explicit.
- 01Define the workflow
- 02Choose the hardware
- 03Validate integrations
- 04Confirm deployment
FROM SCENE TO SYSTEM
Give each part a clear job.
Start with the operating sequence, then follow a relevant device to its references. These are planning examples; a final hardware and software combination needs a project review.
A booked room or shared entrance
A booking creates a credential. The reader passes the credential to the host; the host checks permission and the door-control equipment performs the release.
Decide before selecting
Define who issues and revokes credentials, how the host receives reader output, and what should happen when the connection is unavailable.
Take the next step
Review the reader role and installation planning. Request the exact interface and wiring reference for the selected version.
A visitor who needs to call inside
An entrance terminal starts a call. A receiving client handles the conversation, and an authorized person decides whether to release the entrance.
Decide before selecting
Name the receiving device or application, platform and network. Confirm pairing and the release path before treating the combination as a complete system.
Take the next step
Use the product and video intercom manuals as a starting point; the receiving client and project pairing still need confirmation.
Several doors with shared management
Readers identify the credential at each entrance. Door-control equipment and the management platform carry out the agreed permission and release workflow.
Decide before selecting
Prepare a door schedule: each reader, lock, exit input, power supply and cable route. Confirm the reader protocol and individual terminal assignments from the approved wiring reference.
Take the next step
Review the FCC4904 port reference, wiring guide and manual together. The final combination depends on the selected reader and lock versions.
Prove the whole sequence on a sample.
Use a valid credential, an expired or revoked credential, and an unavailable network or host connection. Record the expected response, the actual response and which component made the decision. Confirm normal entry, exit and recovery with the project’s installer before deployment.
