NutoPass — Biometric School Management for the Modern Campus
End-to-End School Management Platform with On-Device AS608 Biometric Identity, Multi-Tenant Isolation, and Production Azure Cloud Pipeline
The Problem
Student registration, attendance tracking, and result management at most Nigerian institutions still runs on spreadsheets, paper registers, and WhatsApp group announcements. There's no single source of truth — a student's record lives in five different places and none of them talk to each other. For final year students, this is worse: registration queues, manual fingerprint enrollment with no digital backup, and results published on physical notice boards. The goal was to build the system that should have existed already.
Key Bottlenecks Before Engineering:
- Fragmented student data living across spreadsheets, paper registers, and disparate chat announcements.
- Final-year administrative bottlenecks: chaotic physical registration queues and manual fingerprint enrollment without cloud backup.
- Results and academic records published on physical notice boards with zero real-time student portal access.
- The ask: A unified, single-source-of-truth campus management system built around verified physical identity.
What I Built
NutoPass is a full school management platform with biometric identity at its core. Students enroll their fingerprint once — the system handles everything else.
The Hard Problems I Solved:
Real biometric hardware integration
NutoPass uses a genuine AS608 fingerprint sensor with onboard DSP, not a simulated input. Fingerprint templates are captured, processed on-device, and matched against enrolled records. This isn't a demo — it works with physical hardware.
Multi-tenancy via Prisma Client Extensions
Like CeVo, every query is tenant-scoped at the ORM layer. Multiple schools can run on the same deployment without any data crossover.
Azure deployment pipeline & production debugging
NutoPass is live on Azure App Service via GitHub Education, with Oryx handling the build pipeline. DNS configured through Name.com. The deployment process involved debugging Oryx build failures and resolving a PWA service worker caching bug causing jwk-kid-mismatch auth errors — all resolved and confirmed stable.
Clerk production authentication
Full authentication in production, not dev mode. Session management, role-based access, and secure token handling across the platform.
The Result
NutoPass is live at cpeautomation.app, accessed by real supervisors and students. It was successfully defended as a final year project and represents the first biometric-integrated school management system built and deployed by a student engineer at UNILORIN's Computer Engineering department.
Measurable Impact & Deployment Metrics:
- Live at cpeautomation.app and actively accessed by real supervisors, faculty, and students.
- Successfully defended as a final year engineering project at UNILORIN.
- First biometric-integrated school management platform designed and shipped by a student engineer in the department.
- Architected to onboard additional institutions as isolated tenants without any infrastructure changes.
What This Unlocked & Proves
Most developers talk about biometric integration. NutoPass shipped it — with real hardware, a production cloud deployment, and a multi-tenant architecture underneath. The same foundation applies to any institution that needs secure, centralised student management.
🔒 Note: Live at cpeautomation.app. Full video walkthrough and hardware demonstration available.
Want to build a system like this?
Let’s discuss your architecture, database constraints, and operational workflows.