Enterprise & multi-location
One recognizable network identity for every office
Give office egress, privileged users, APIs, and production services a named identity record that is not defined by one local ISP.
Explore enterprise use case
Use cases
Choose the workflow where One Network Identity must stay recognizable
LARUS One gives a selected Location or digital service One Network Identity across reviewed provider and Location changes.
Choose the office, property, residence, application, or gateway where a changing public source creates repeated trust reviews.
USD 6,998 per year. One Unit serves one Location at a time.
Local delivery is separate from the LARUS One subscription.
Customers
Begin with the operating environment you already manage
Each customer path explains the continuity problem, Unit and Location calculation, delivery boundary, evidence, and first-pilot sequence for that environment.
Hotels & hospitality
One recognizable network identity for every property
One managed network identity for PMS, POS, payment, supplier, staff, security, and premium-service workflows across hotel providers and properties.
Explore hospitality use casePrivate clients and family offices
One recognizable network identity across private Locations
One managed network identity for family-office, finance, advisor, residence, security, and private-infrastructure workflows across providers and Locations.
Explore private-client use caseUse case library
Find the workflow that should not restart after a network change
These pages explain the review context for a specific workflow. They do not redefine LARUS One as an address product, VPN, proxy, or guarantee of third-party acceptance.
Business use cases
Business access and independent review
Office, finance, supplier, customer, and privileged-access workflows often depend on a public source that another organization reviews.
Locations
Location and property operations
Residences, family offices, hotel properties, and hospitality systems need documented identity without turning local connectivity into the product.
Infrastructure
Applications, automation, and security
APIs, production services, AI workflows, and security gateways need named network evidence while customer controls remain in charge.
Shared service model
Every use case follows the same commercial boundary
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.
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
Prove one workflow at one Location before expanding
- 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.
FAQ
Use-case questions before the first pilot
Which use case should we start with?
Start with one Location and one workflow where a bank, supplier, customer, API provider, security team, advisor, or operator already reviews the public source. The pilot should test a real continuity dependency, not every possible use at once.
Does every workflow need its own Identity Unit?
No. One Identity Unit serves one active Location at a time. Multiple approved workflows can use that Location's delivered identity; add Units when additional Locations must be active at the same time.
Can we use our existing ISP?
Yes, if the provider supports BYOIP for the Location and can coordinate routing and RPKI with LARUS. Enter the provider name, ASN, technical contact, and authorization details in the client portal for review.
Is local delivery included in the annual price?
No. USD 6,998 covers the annual LARUS One subscription. Taxes shown at checkout and local partner installation, access, routing, equipment, and on-site service charges are separate.
Does the Passport guarantee allowlisting or approval?
No. It supports independent review. Each bank, supplier, customer, API provider, auditor, and security team decides whether to recognize or allowlist an address.
Is LARUS One an ISP, VPN, or proxy?
No. LARUS One provides a managed public network identity and continuity workflow. It does not provide anonymity, endpoint protection, MFA, a firewall, a VPN, monitoring, incident response, or household cybersecurity.
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.