هذه الوثيقة التقنية متاحة باللغة الإنجليزية.
Planning reference: volumes and infrastructure figures in this document are hypothetical sizing scenarios, not measured product capacity or deployed installations. Validate workload, costs, security and recognition performance before procurement. The current feature overview is available at /features.
This documentation explains how to deploy Sentinel ID for a national agency: from a single pilot server to a two-site installation designed for more than 4 billion fingerprint, face and vehicle records and over 4 million cameras, on hardened servers hosted inside your organisation, with no outside access.
Who it is for
| Reader | Start with |
|---|---|
| Decision makers and architects | Architecture for 4 billion records, then Sizing |
| System and database administrators | Prerequisites, then the installation pages in order |
| Security officers and auditors | Security hardening and Data protection |
| Integrators and developers | The Developers page and the API reference |
| Operations teams | Camera network and Operations |
The building blocks
Every server runs ordinary operating-system services (systemd on Linux, Windows services on Windows Server), on hardware the agency owns.
| Tier | Software | Role |
|---|---|---|
| Edge | HAProxy + keepalived, nginx | TLS, load balancing, a floating virtual IP |
| Application | Sentinel ID application servers | Web app, field app, REST API, alerts, dispatch, voice signalling |
| Ingest | Sentinel ID, ingest role | Plate reads and events from millions of cameras |
| Matching | Sentinel ID matcher nodes, native C++ matching | In-memory fingerprint shards |
| Indexes | Fingerprint shortlist index, face vector index | Narrow each search before exact matching |
| Data | Oracle Database or MongoDB | People, vehicles, cases, sightings, audit log |
| Files | Central storage: NFS on a NAS cluster, or S3-compatible object storage | Photos, evidence, video, camera crops |
| Management | Bastion, monitoring, log collection, backup | Run and watch everything, from a separate network |
Two important notes
Capacity is proven on your hardware. The figures in these pages are engineering estimates from measured component performance. Final sizing is confirmed by an acceptance benchmark before national rollout. See What is built today and what the project delivers.
Biometric matches are leads, not verdicts. At billions of records even a tiny false-match rate produces candidates. A trained examiner confirms every match before anyone acts on it.