Commercial Datasheet
ThrustID
ThrustID is a visitor identification and access-record solution for organizations that need a more efficient, controlled, and professional way to manage visitor intake at reception desks, gatehouses, guard stations, and other access points.
It combines an on-site appliance with cloud-connected oversight so teams can run locally first while still supporting remote administration, onboarding, and multi-device visibility when needed.
Core Capabilities
- Assisted ID document capture
- Structured data extraction from identity documents
- Operator review and correction before records are finalized
- Visitor history and searchable scan records
- Local administration and user management
- Reporting-oriented views for operational review
- Cloud device visibility and remote inspection
Typical Use Cases
- Corporate entrances and office receptions
- Security checkpoints and guard stations
- Gated properties and managed communities
- Schools, private facilities, and restricted-access sites
- Organizations with one site or multiple locations
Deployment Model
| Operating model | Local-first appliance deployment |
| Remote management | Cloud-connected workspace and device oversight |
| Connectivity | Device-initiated outbound connectivity when cloud features are enabled |
| Administration | Browser-based local interface and cloud portal |
| Installation | Assisted setup and deployment workflow |
Platform Highlights
- Supports on-site operation without requiring internet connectivity
- Designed for controlled-access environments and visitor workflows
- Supports a structured review process before records are finalized
- Suitable for organizations that want a physical device with centralized oversight options
Environment and Hardware
| Reference appliance class | Compact edge appliance |
| Processor | Quad-core 64-bit ARM processor |
| Memory | 512 MB RAM or 1 GB RAM |
| Camera | 5MP camera module |
| Storage | microSD, starting from 32 GB |
| Triggering | Document placement Sensor |
| Connectivity | Wireless and/or local network connectivity for local access and cloud connection |
| Power Input | 5 V DC appliance power |
| Operating environment | Indoor or controlled-access environments |
Hardware accessories, enclosure format, and mounting details can vary by deployment package.
Software Specifications
| Local processing model | On-device capture, OCR processing, review workflow, and record management |
| User interface | Local browser-based administration and operator interface |
| Record handling | Structured storage of scans, extracted fields, review status, visitor history, and operational events |
| OCR capabilities | Document detection, image preparation, structured field extraction, confidence-oriented review support, and configurable document regions |
| Review workflow | Operator validation, correction, and approval of captured information |
| Reporting | Searchable history, reviewable records, and export-oriented reporting workflows |
| Administration | Local user management, licensing, setup, and configuration |
| Language support | English and Spanish interface support |
| Resilience features | Retry handling, stale-job recovery, and persistence-failure safeguards |
| Remote access model | Cloud-connected visibility layered on top of the local appliance |
| Fleet visibility | Multi-device overview with per-device status and activity insight |
Network Requirements
| Local network access | Required for browser-based administration on the local site network |
| Internet access | Required only when cloud-connected features, remote management, or cloud pairing are enabled |
| Connectivity model | The device initiates outbound communication for remote connectivity; direct inbound exposure is not required for cloud-managed operation |
| Deployment consideration | Customer networks should allow secure outbound access to the configured cloud services when remote management is enabled |
| Offline operation | Core local capture, review, and record management remain local-first |
Security and Data Handling
ThrustID is intended for identity-related records and should be deployed with customer-defined access control, retention, and privacy policies.
The cloud-connected model is designed so devices initiate outbound communication rather than exposing the appliance directly to the internet. Access to remote management is workspace-scoped and limited to approved actions.
Included Components
| Hardware appliance | Integrated edge device for on-site operation |
| Embedded software | Local capture, OCR, review, reporting, administration, and licensing functions |
| Cloud access | Remote management and fleet visibility capability |
| Device licensing | Device-bound license model |
| Deployment package | Configuration, pairing, and operational support materials |
Commercial Fit
| Technical buyers | Clear deployment model, operating scope, and connectivity expectations |
| IT departments | Defined local-first behavior with remote management |
| System integrators | Assisted deployment model and configurable hardware package |
| Technical resellers | Solution framing that supports consultative sales |
| Deployment engineers | Practical guidance on hardware, environment, and operational setup |
Support Information
| Model | ThrustID |
| Document | Commercial datasheet v1.0 |
| Target market | Security, facilities, property management, enterprise visitor management, and channel partners |
| Maintenance | Supports software updates, re-pairing, licensing updates, and operational review |
| Availability | Available by project or through authorized partners |
| Support | Deployment, onboarding, maintenance, and technical support |
| Warranty | Per commercial agreement |
- The local runtime is the primary supported workflow.
- The cloud path is additive and optional.
- Exact enclosure, power arrangement, and accessory package should be defined per deployment.