Stayntouch PMS Network & Communication Guidelines

Modified on: Thu, 30 Oct, 2025 at 4:42 PM

Applies to:          Stayntouch PMS          

Stayntouch PMS Network & Communication Guidelines


TABLE OF CONTENTS

NETWORK & COMMUNICATION

System Architecture


Stayntouch is a fully cloud-based hotel property management system (PMS) built on a mobile-first architecture. The application tier operates as stateless services running in multiple AWS Availability Zones behind load balancers and Auto Scaling Groups, ensuring high availability and automatic failover. The data tier uses Amazon Aurora (Multi-AZ) with a single writer and multiple readers, providing automatic failover and regular backups to local and remote regions. Cross-region disaster recovery is supported with warm standby in remote regions, and the system is designed to recover from regional outages within four hours, with plans for active-active regional failure readiness. The architecture employs a modular integration approach, supporting real-time, low-latency data exchanges via event-driven architectures, and seamless integration with mobile, web, and cloud-native applications through REST, GRPC, and GraphQL APIs. Performance is optimized through on-demand data retrieval, search-first architecture, data compression, and progressive disclosure, ensuring fast load times and efficient bandwidth usage. Stayntouch is a cloud-native SaaS solution, delivering scalability, resiliency, and continuous innovation, with infrastructure responsibilities fully managed within the SaaS environment. The platform is certified for GDPR, PCI DSS Level 1, SOC2, and ISO 27001 compliance.

Where are data centers located?


The primary and secondary data centers are located in the Northern Virginia region, where customers are served from multiple AWS availability zones within that region. For the EU production instance, the primary location is Frankfurt with backups in Ireland. In the U.S., the primary region is Virginia with a backup in Oregon. Hosting can also be provisioned in the AWS Frankfurt region to meet specific data residency requirements.

What is the typical latency for the application?


Small data sets are processed instantly, while large data sets may take 30 seconds to a minute. The system is designed to ensure fast initial page loads and consistent responsiveness across different data volumes and user scenarios by using on demand data retrieval, data compression, and progressive disclosure. Large processing tasks are sent to a background process and are available as soon as generated. Our average latency is 150 ms.

INTERNET/BANDWIDTH REQUIREMENTS


To connect to Stayntouch PMS, the hotel must maintain a reliable internet service with sufficient bandwidth to support day-to day operational needs. Under normal conditions, Stayntouch PMS consumes minimal bandwidth; however, usage may temporarily increase during activities, such as printing reports or downloading exported data. Stayntouch recommends a minimum of 10–20 Mbps dedicated bandwidth per hotel, depending on the number of active workstations and users.

INTERFACE PC REQUIREMENTS


For on-property integrations, where servers are not located on the cloud (e.g., keys, PBX, WiFi, etc.), an interface PC is required. The interface PC needs access to https://app.us1.stayntouch.com/login, https://app.us2.stayntouch.com/login, or https://app.eu1.stayntouch.com/login (depending on which environment your property uses to log into the system) AND https://ifc.stayntouch.com, https://ifc.us.stayntouch.com, or https://ifc.eu.stayntouch.com.

DELPHI REQUIREMENTS


If connecting to Delphi S&C, please confirm the interface PC used for Delphi can successfully communicate with Stayntouch’s IP addresses over port 80. Additionally, we'll require the property’s public IP address as well as verification that all required whitelisting and port forwarding configurations have been completed.

EMV TERMINAL REQUIREMENTS


For payment gateway connectivity, here is some information about supported payment gateways and EMV device models:


The EMV terminal needs to be open to our public IP addresses.

KEY ENCODER REQUIREMENTS


We offer direct integrations with Saflok, SALTO, and Ving key encoders; however, we support multiple key integrations through our middleware partner, Comtrol. You can find more information about our direct key integrations here and a full list of our key integration partners here.


The key encoder needs to be open to our public IP addresses.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.