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.
POS / PMS Systems
Public network identity for POS, PMS, and hospitality operations
Hospitality payment systems, property management platforms, supplier access, and operational tools may need public-address documentation. LARUS One can assign eligible hotel systems named Identity Addresses with evidence for independent review; vendors and payment partners decide whether to accept them, and acceptance is not guaranteed.
USD 6,998 per Identity Unit-yearLocal delivery is separate from the LARUS One subscription.
Value
Give hospitality operations a clean identity layer
Use Identity Addresses for POS systems, PMS systems, payment access, supplier systems, staff networks, hotel APIs, and operational gateways.
Identity Address examples
Assign public network identity to the systems that need recognition
- POS gateway
- PMS platform endpoint
- Payment operations identity
- Supplier access point
- Hotel API gateway
- Staff operations network
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
Payment and operations identity
Assign named Identity Addresses to critical hotel systems.
Supplier access
Submit Identity Passport and Allowlist Pack evidence for independent review. Vendors and payment partners decide whether to accept it, and acceptance is not guaranteed.
Delivery changes
A provider or location change requires a fresh technical and delivery assessment. Keeping the same address is not guaranteed.
FAQ
Answers to common questions
Can POS and PMS systems have separate Identity Addresses?
Yes. Customers can assign Identity Addresses by system, gateway, or operational workflow.
Can suppliers receive allowlist documentation?
LARUS One provides Identity Passport and Allowlist Pack documentation for independent supplier review. Each supplier decides whether to allowlist an address, and acceptance is not guaranteed.
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.