On your infrastructure
Deployed on-premise or air-gapped — access records never leave national control.
Government & Public Sector
Sovereign access for the institutions that need it most.
For ministries and agencies, access records cannot live in someone else's cloud. MeetPass deploys entirely on your infrastructure — and is already in a live proof of concept with a national security ministry.
Validated
A national security ministry approached MeetPass directly to run a proof of concept.
A live MOI proof of concept — a credential no global tool holds in this region.
0% on-premise — records stay with you
0 pass types under one credential layer
0 dependency on external cloud
0 audited dashboard for every entry
Why government chooses it
Sovereignty is not a feature. It is the design.
Built in the region
Engineered in Doha, Arabic-first, and aligned with local data-residency law.
Defence-in-depth
Layered security from the gate to the database, with role-based access control.
Procurement-ready
Documentation, NDAs and an evaluation path that fit public-sector process.
The problem, in numbers
Trust is built at the counter — and lost in the queue.
Citizens judge a state by the encounter they actually have with it: whether they can get in, whether they are seen, and whether the person in front of them was chosen fairly. The public evidence on all three is not comfortable reading.
of people across 30 OECD countries report low or no trust in their national government — more than the 39% who report high or moderately high trust.
OECD Survey on Drivers of Trust in Public Institutions, 2024is the OECD average share of people who expect a politician would refuse a political favour in return for a well-paid private-sector job. Roughly two in three expect the opposite.
OECD Survey on Drivers of Trust in Public Institutions, 2024people worldwide still lack official proof of identity — about one person in ten — the first barrier to any public service that asks who you are.
World Bank ID4D / Global Findex, 2025is Qatar's rank of 193 in the UN E-Government Development Index 2024, up 25 places and 5th most improved worldwide.
UN E-Government Survey 2024 (UN DESA)Figures published by the OECD, the World Bank and UN DESA. Each links to its source.
Who gets seen
The queue should decide it. Not who you know.
In many administrations the appointment is informal: a phone call to someone inside, a name passed to the guard, a place found for whoever is connected. Everyone else waits, comes back tomorrow, or gives up. It is rarely corruption in the criminal sense — it is simply what happens when there is no system, and discretion is the only tool anyone has.
A recorded request changes the default. Every citizen files the same way, is verified the same way, and holds a pass that says exactly when they are expected. The officer at the door is no longer deciding who is important; they are checking whether a credential is valid.
- One route in — the same request form for every citizen, from any device
- A timestamped queue, so precedence is a matter of record, not of relationships
- Reasons recorded when a request is declined or reprioritised
- The officer verifies, not selects — discretion at the door is removed by design
Requests · Public counter 3
Today
- 01Request #4471filed 08:02 · verified09:15
- 02Request #4472filed 08:09 · verified09:30
- 03Request #4468priority · medical, reason logged09:45
- 04Request #4474filed 08:21 · verified10:00
Order and every change to it are written to the audit trail
The wasted journey
Nobody should travel to a closed door.
A citizen takes a morning off work, travels across the city, clears the gate — and the official was called into a session at eight. Their time is genuinely valuable and genuinely unpredictable; the problem is that the visitor is the last person to find out.
MeetPass binds the pass to the official's calendar. When availability changes, the pass changes with it — automatically, before the journey rather than after it — and offers the next slot in the same message.
- Pass status follows the diary — issued, confirmed, on hold or rescheduled
- The visitor is told first, by SMS and in the pass itself
- A replacement slot offered at the moment of cancellation
- Delegation to a deputy where the matter does not need the minister
- No silent no-shows — every change is attributable and logged
08:12 · issued
Confirmed
08:40 · diary changed
Rescheduled
Visitor notified 2h 20m before travelling
Ministers & senior officials
The scarcest resource in the building is an hour of their day.
Senior officials cannot see everyone, and pretending otherwise is what produces the crowd in the corridor. What they can do is decide, transparently, what deserves the hour — and let the system carry that decision through to the gate.
Their diary, their rules
Office hours, protected blocks and no-meeting windows set by the official or their bureau — requests can only land where the diary allows.
Prioritisation with a reason
Requests are triaged by subject, urgency and delegation rules. Whatever is moved up the queue carries a recorded justification.
Delegation that works
Route a matter to the right director or department instead of holding it for a minister who does not need to see it.
Protocol & closed sessions
Delegations, bilateral meetings and restricted sessions with their own clearance level and a separated record.
Minuted, then followed up
Every meeting produces signed minutes and tracked commitments — what the office undertook, and whether it was done.
Where the hours went
Reporting on requests received, seen, delegated and declined — by subject and by department, for the office and for oversight.
The door · verification & audit
Every entry, verified and accounted for.
The security half of the platform is built for national-grade accountability — identity checked at the source, screened against watchlists, and logged to an immutable record no one can quietly edit.
QID & passport verification
Document intelligence reads the Qatar ID or passport at registration, auto-fills the visitor record and flags mismatches before a pass is issued.
LDAP & directory screening
Hosts and staff authenticate against your own Active Directory. Identity stays in your directory — MeetPass never becomes a second source of truth.
Blacklist & watchlist
Every requester is screened against a platform-wide watchlist. Flagged identities are blocked at request, with dual-authorisation override for authorised officers.
Signed-QR entry
A cryptographically signed QR pass is validated at the gate in under a second — online or fully offline for air-gapped sites. No valid signature, no entry.
Immutable audit trail
Every request, scan, entry and exit is written to a tamper-evident log — searchable by date, gate, host or member, and exportable for any review or investigation.
Incident, lockdown & muster
Live watch on who is on premises, one-tap lockdown, and an instant evacuation roll-call of everyone inside — the accountability a security committee expects.
Screening at the source
A watchlist is only as good as its last update.
A list exported to a spreadsheet last quarter is not a control. MeetPass screens every request against lists that are refreshed from the systems that own them — central authorities, state and municipal registers, and the ministry's own records — so a name added this morning is enforced at the gate this morning.
- API integration with central, state and departmental registers
- Scheduled or event-driven sync, with the last successful update visible to supervisors
- Screened at request, not at arrival — a flagged identity never receives a pass
- Local entries too — a department can add its own restrictions in seconds
- Dual authorisation to override, with both approvers recorded
- Runs air-gapped — signed list bundles imported on your own schedule
Central authority
State register
Ministry list
Screening engine
- Request #4471cleared
- Request #4472cleared
- Request #4473blocked · list match
Deployment model
On-premise. Air-gapped if required.
From a private-cloud rollout to a fully air-gapped installation with no external network, MeetPass meets the security posture your mandate requires.
- On-premise on your own servers
- Air-gapped with offline verification
- Private cloud where appropriate
Gates & apps
01
Verification gateway
02
National servers
03
Sovereign data store
04
Engagement
A clear path from briefing to rollout.
-
1
Confidential briefing
We walk through the platform and architecture with your security team, under NDA.
-
2
Proof of concept
A scoped deployment in your environment — exactly as the Ministry of Interior is running today.
-
3
Evaluation & hardening
Your team validates security, residency and audit against your requirements.
-
4
Sovereign rollout
Full deployment across sites — on-premise, air-gapped or private cloud.
Government FAQ
What a security committee asks first.
Yes. An air-gapped installation runs entirely inside your boundary, with signed watchlist bundles imported on your own schedule and gate verification working fully offline.
Document intelligence reads the QID or passport at registration, auto-fills the visitor record and flags mismatches before a pass is issued. Staff authenticate against your own directory rather than a second identity store.
Yes. Screening lists refresh from the systems that own them — central authorities, state and municipal registers and the ministry's own records — on a schedule or on change, with the last successful sync visible to supervisors.
Records inherit a classification at creation and controls tighten as the class rises, up to segregated records, dual authorisation on overrides and air-gapped deployment at Secret. Applicable controls remain determined by your own risk assessment.
A confidential briefing under NDA, then a scoped proof of concept in your environment, then your own security and residency evaluation, then rollout. Documentation is prepared for public-sector process rather than adapted to it.
Access to Restricted and Secret sessions is gated on clearance rather than role alone, those records are segregated, and every access is written to a tamper-evident log that neither your team nor we can quietly edit.
Arrange a confidential government briefing.
Speak with our team — including full documentation and a proof-of-concept path under NDA.