Scale by active Location, not by address count
People, devices, rooms, network segments, and workflows do not change the subscription count. Count the Locations used at the same time.
Hotel Room Identity
Public network identity for hotel rooms, POS, PMS, and hospitality operations
Keep one recognizable network identity for a hotel's approved room, suite, event, POS, PMS, and staff workflows when its ISP or delivery partner changes.
USD 6,998 per Identity Unit-yearLocal delivery is separate from the LARUS One subscription.
Value
Give hotel POS, PMS, and room workflows a recognizable public identity
Use one managed Identity Unit to document the public source behind eligible room, suite, event, POS, PMS, payment, and staff workflows. Start with the workflow an outside party already needs to recognize.
Identity Address examples
Assign public network identity to the systems that need recognition
- Room network identity
- Suite identity
- Event network identity
- Premium guest identity
- Staff operations gateway
- Hotel security gateway
- Conference API access
Shared service model
Every use case follows the same commercial boundary
Identity, local delivery, and customer controls stay separate
LARUS anchors identity. The selected provider delivers the local network.
Evidence supports review; every third party decides its own acceptance policy
Identity Passport and Allowlist Pack evidence supports independent review. Every third party applies its own policy and decides access.
Customer controls
Public identity works with the customer security architecture. Firewalls, SASE, routing, segmentation, and access policies continue to control what is reachable.
From use case to paid pilot
Your first paid pilot
- 01
Start one paid pilot
Create an account and sign in to purchase one annual Identity Unit online.
- 02
Add the first Location
After purchase, add the office, property or other place where you will use the identity. Location profiles are free; one Unit serves one active Location at a time.
- 03
Arrange delivery and activate
Choose an available Certified Partner or an existing provider that supports BYOIP. LARUS and your provider confirm the delivery design and validate activation before you use the identity at that Location.
- 04
Review Identity Passport evidence
Review the Identity Passport and allowlist evidence, validate the workflow, then add one Unit for each additional active Location.
How LARUS One helps
LARUS anchors identity. The selected provider delivers the local network
Guest and event identity
Assign named Identity Addresses to eligible rooms, suites, and event networks.
Operations identity
Use dedicated Identity Addresses for eligible POS, PMS, security systems, and staff workflows.
Hospitality evidence
Document the deployment with Identity Passport and support records.
FAQ
Answers to common questions
Can a hotel give rooms or suites their own network identity?
A hotel can request Identity Addresses for eligible room, suite, event, or operational workflows. The delivered design, address availability, and third-party acceptance are confirmed separately.
Can hotel POS and PMS systems have separate Identity Addresses?
Yes. An eligible hotel can assign Identity Addresses by POS, PMS, room, suite, event, payment, or staff workflow; delivery design and third-party acceptance are confirmed separately.
Does this replace hotel Wi-Fi or guest security?
No. Hotel Wi-Fi, guest isolation, firewalls, captive portals, and local security policy continue to control what is reachable.
One paid pilot
Choose one workflow and one Location to validate first
Confirm local delivery, routing, evidence, and reviewer fit before adding more active Locations.