We are currently working on the technical architecture for an enterprise Visitor Management System in KSA and wanted to open up a discussion around a few architectural and regulatory challenges specific to the Saudi Arabian market.

Building an enterprise VMS here brings a unique mix of physical security hardware and strict compliance standards:

Local Data Residency & PDPL Compliance: Under Saudi Arabia's Personal Data Protection Law (PDPL), visitor PII (national IDs, phone numbers, facial recognition / photos) needs strict retention and local hosting rules. How are you architecting your database isolation and retention policies for local cloud deployments (e.g., AWS/GCP local regions in KSA)?
Hardware & Edge Integration: We need real-time communication with physical gates, QR-code turnstiles, and thermal badge printers across remote branches with intermittent connectivity. What protocols are you favoring for this—MQTT over WebSockets, or localized edge gateways that sync back to the cloud?
Identity Verification & OTP Latency: When handling pre-registration and walk-in passes, keeping check-in latency under 5 seconds is critical.

If you’ve built or integrated a smart office or visitor management solution
, what does your tech stack look like? How do you balance real-time edge sync with strict data compliance?

Would love to hear your thoughts and lessons learned!