About
QID Secure exists because visitor logs at most sites are either paper, a spreadsheet, or a cloud tool that stops working the moment the internet does. We built the opposite: a self-hosted platform that treats the visitor journey as a chain of evidence.
What we believe
- Registration is not approval. A submitted form is a request, not permission to enter. A human supervisor decides.
- OCR is an assistant, not an authority. Extracted values are shown with confidence and confirmed by a person.
- Offline is a requirement, not a mode. The core journey must work on a local network with no internet.
- PII stays out of links. QR codes and SMS carry references and URLs, never identity data.
- History is append-only. An audit log that can be edited is not an audit log.
Who it is for
Facilities and security teams in Qatar managing contractors, visitors, deliveries and staff movements across one or more sites. The platform is designed around Qatar ID and passport capture, Arabic and English names, and the reality of a gate tablet on a local Wi-Fi network.
How it is deployed
Three containers — web gateway, API and a single-node MongoDB replica set — plus an encrypted uploads volume. The same compose file runs on a mini-PC on site or on a cloud VPS when remote access is needed. Backups are a nightly mongodump and a volume snapshot, with a restore tested before go-live.
What is deliberately deferred
NFC tap reading, passport chip reading, automatic Arabic-to-English translation, BI analytics, Keycloak SSO and central multi-site sync are not part of the first release. They are documented as deferred rather than silently promised.
Talk to us
If you are evaluating QID Secure for a site, start a free workspace or request a walkthrough. We will map your gates, roles and retention policy before any deployment.