Guest and event identity
Assign recognizable identities to rooms, suites, and event networks.
Hotel Room Identity
Public network identity for hotel rooms, suites, events, and hospitality operations.
Hotels, serviced residences, and private clubs can use LARUS One to assign named Identity Addresses to rooms, suites, event networks, premium guests, staff systems, POS, PMS, and security operations.
Identity capacity
One Identity Unit. Up to 254 globally unique Identity Addresses.
Each LARUS One Identity Unit can activate up to 254 globally unique Identity Addresses at one deployed location, for the devices, endpoints, computers, servers, gateways, applications, APIs, and trusted access points that need stable public network identity.
The Identity Location is the selected home, office, family office, hotel, enterprise site, API edge, or private network where the Identity Unit is deployed through the LARUS One delivery network.
Actual usable count may depend on delivery design, security policy, and local network configuration.
Value
Bring accountability and continuity to hospitality networks.
Use Identity Addresses for premium rooms, long-stay guests, conference networks, payment systems, staff workflows, access control, and security monitoring.
Identity Address examples
Assign public network identity to the systems that need recognition.
Room network identitySuite identityEvent network identityPremium guest identityStaff operations gatewayHotel security gatewayConference API access
How LARUS One helps
LARUS anchors identity. The selected provider delivers the local network.
Operations identity
Use stable Identity Addresses for POS, PMS, security systems, and staff workflows.
Hospitality evidence
Document the deployment with Identity Passport and support records.
FAQ
Customer-facing answers for this use case.
Can one hotel use multiple Identity Addresses?
Yes. Each Identity Unit can activate up to 254 globally unique Identity Addresses at one deployed location.
Can hotel systems remain protected by local policy?
Yes. Guest isolation, firewalls, captive portals, and local security policy continue to control what is reachable.
Related use cases
Continue through the identity workflows connected to this page.
POS / PMS network identity
Public network identity for POS, PMS, and hospitality operations.
Use LARUS One Identity Addresses for POS systems, PMS platforms, payment operations, hotel suppliers, security reviews, and hospitality networks.
View related use caseSecurity gateway identity
Public network identity for security gateways and trusted access points.
Give firewalls, SASE gateways, security monitoring systems, access controls, and trusted security endpoints stable public network identity.
View related use caseSupplier access identity
Public network identity for supplier access and trusted B2B workflows.
Use LARUS One Identity Addresses for supplier allowlists, vendor portals, operations systems, logistics workflows, and trusted B2B access.
View related use caseCustomer allowlist identity
Public network identity for customer allowlists and security reviews.
Give customers stable Identity Addresses for allowlists, security review, API access, supplier systems, and trusted enterprise connectivity.
View related use caseDeploy
Deploy one Identity Unit to one selected location.
Deploy one Identity Unit to one selected location and activate up to 254 globally unique Identity Addresses for the systems that need stable public network identity.
LARUS maintains the Identity Unit, Identity Addresses, Identity Passport, Allowlist Pack, and continuity record. The selected provider delivers the local network service.