Face Terminals
Face, display, and credential terminals
Explore this category →Products
The right device.
For your next idea.
Explore access hardware by form or application. Then find the information you need to take the next step.
QR Readers & Terminals
Embedded and standalone scan devices
Explore this category →
Card Readers
RFID, NFC and keypad credential readers
Explore this category →
Access Controllers
Control and integration hardware
Explore this category →
Power Supplies
Access-control power infrastructure
Explore this category →
Security Modules
Secure relay and control modules
Explore this category →
Smart Locks
Connected lock platforms
Explore this category →
Turnstiles & Gates
AB interlocking gates, swing gates, flap barriers, tripod and full-height turnstiles
Explore this category →
Entry & Exit Hardware
Exit controls, entrance gates, turnstiles, and installation accessories
Explore this category →How will your platform use the hardware?
Choose the integration path before selecting firmware. A device interface alone does not establish protocol support, and DejaOS development is available only on supported configurations.
Keep business logic in your platform.
Request the protocol reference for the exact model and application firmware. Define credentials, authorization, execution and access-event reporting with your integration team.
Compare standard protocol integration →Write the device application in JavaScript.
Compare supported devices and SDK targets when your team needs to develop the interface and business logic that run on the device.
Choose a DejaOS development device →A few things worth knowing.
What should I share when choosing a device?
Tell us which credentials people will use, where the device will be installed, which interfaces are required and what should happen in the software workflow. A mounting drawing, host-equipment description or simple process diagram helps us identify the questions that must be confirmed before recommending a configuration.
Does every configuration include the same features?
No. Credential modules, interfaces, mounting parts, network options and software can vary within the same product family. Confirm the exact model and selected options in writing before designing an enclosure, cable set or integration around it.
How can I get a manual or datasheet?
Find available documents by model in the download center. If the manual, specification or installation drawing you need is not listed, send the model and configuration to our team so we can identify the matching document.
How should we evaluate a product for our project?
Start with the credential, mounting, interfaces and software flow that matter to the final installation. Confirm the sample configuration in writing, test it in the intended environment and record any differences before planning a larger rollout.
What is the difference between standard-device integration and DejaOS development?
Standard-device integration connects your platform to the supplied device application. It exchanges commands and events through the matching protocol. DejaOS lets you write an on-device application in JavaScript.
DejaOS requires supported hardware and the modules available for that target. Confirm the exact model, application firmware and workflow before choosing either path.
Do we need to rewrite the device application to connect our platform?
Not necessarily. Keep the supplied device application if its matching protocol supports your workflow. Your platform can implement that protocol.
A custom interface or device behaviour may need application development. Consider DejaOS only on a confirmed supported configuration. Validate the workflow and firmware before deciding.