Inlet's ecosystem:
Our core lock service underpins a complete digital customer journey by integrating ordering, payment, access, communication, and control systems into a seamless Inlet Ecosystem. This modular approach delivers a frictionless and comprehensive customer experience.
Inlet is "access control-/lock system" agnostic:
Inlet interfaces with a wide array of lock systems, consolidating functionalities from multiple sources into a single solution. We can assign uniform codes across systems or provide tailored keys to support various user journeys.
Lock Communication:
To securely connect with lock systems, Inlet requires specific API access, along with whitelisted IP addresses and ports. This approach not only enhances security but also enables real-time status monitoring through a unified interface.
Booking Integration:
Our booking process integrates multiple channels—from SMS and QR code reservations to comprehensive PMS solutions for hotels and activity venues. Strategic partnerships ensure we meet diverse booking requirements with optimal solutions for end customers.
API Security:
Built on Laravel’s proven security framework, our session-based API token restricts access to authorized IP addresses. All communications occur over HTTPS, secured by Let's Encrypt certificates and managed via an Azure gateway, protecting against DDoS and similar threats.
Azure Hosting:
Hosted entirely in the cloud, Inlet benefits from rapid inter-service communication and robust security layers provided by Azure. Internal components are isolated using Docker, which supports secure, automated deployments with comprehensive logging and rollback capabilities.
Despite this, we design the internal parts with good security and logging, in separate silos, to prevent a potential error in one place from spreading to other parts of the application. We use Docker for this purpose, ensuring backup, automatic deployment of new versions with testing, and easy rollback if something goes wrong. For more in-depth information, you can read an article about Docker and security here: https://docs.docker.com/engine/security/
"Docker containers are, by default, quite secure; especially if you run your processes as non-privileged users inside the container." - docker.com
Locks Connector:
Inlet connects to various lock systems using IT-defined security protocols, typically via IP address and port, with SSL recommended when available. Connection requires a username and a robust password (minimum 12 characters with a mix of letters, numbers, and symbols). IT providers should ensure firewall whitelisting for our production facility.
Portal Dashboard:
Our dashboard provides real-time monitoring of locations and locks, enabling prompt alerts for any unusual or unauthorized activity.