MeetPass integrates, it doesn't rip-and-replace. It sits on top of your identity, telecom, payment and gate hardware — and where a ministry mandates specific middleware, our validation logic is portable and self-contained.
The interfaces are not privileged. Every core object is reachable programmatically, so MeetPass can feed your data warehouse, your service desk or your own front end rather than becoming another island.
Where policy forbids outbound calls entirely, the API still exists — it is simply served inside your boundary. Nothing about integration requires the platform to reach the public internet.
If a security policy forbids external cloud calls, MeetPass runs entirely inside your environment — credentials pre-seeded in your local database, validation logic packaged as a portable module. The same principle behind the region's trusted national platforms.
Yes. Every core object — request, pass, meeting, scan — is readable and subscribable over a REST API with scoped, revocable token auth, pagination, since-cursors and published rate limits.
Payloads are signed so you can verify the source, delivery is retried with backoff, and every attempt is recorded in a delivery log you can inspect per tenant.
Active Directory and Entra ID for directory sync, SAML 2.0 for SSO and SCIM for provisioning, so joiners and leavers flow through without a second identity store.
In most cases yes. Turnstiles, barriers, access controllers, QR scanners, badge printers and ANPR feeds are driven from the same credential rather than replaced.
The same API is served inside the boundary. There is no mandatory outbound call — watchlists and updates arrive as signed bundles on physical media, and exports leave as checksummed packages.