How It Works
From scan to
secured.
The full NestGuard pipeline — six steps, under one second, fully automated. Scroll to explore.
Scan
A student places their finger on the AS608 optical biometric reader mounted at the gate terminal. The sensor captures the fingerprint and performs a 1:N match against the enrolled template database on-device.
Verify
The gateway microcontroller receives the match result from the sensor. If the fingerprint matches an enrolled student, the system checks for duplicate or replay events (e.g., the same student scanning twice within seconds). If no anomalies are found, the gate relay is triggered.
Unlock
The relay energizes the solenoid lock, retracting the bolt for a configurable duration (default: 5 seconds). The student passes through, and the lock re-engages automatically. A green LED confirms access; a red LED signals denial.
Log
The hardware gateway service translates the raw sensor event into a structured access log entry and sends it to the central NestGuard server via HTTP. The event appears on the live dashboard feed within 400ms of the scan. Logs are write-once — they cannot be edited or deleted after creation.
Analyze
The AI anomaly engine evaluates the new event against the student's behavioral baseline. Factors include time of day relative to normal patterns, gate familiarity, and recent access frequency. If the event deviates significantly, a confidence-scored anomaly flag is attached to the log entry.
Alert
If the event is flagged as anomalous or the scan was unauthorized (no fingerprint match), the system generates a real-time alert. Wardens and security staff see the alert on their dashboard immediately. Critical alerts can also trigger notifications via email and Telegram integration.