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.
Executive Remote Access
Public network identity for executive remote access and privileged workflows
Executive remote access can involve board materials, private infrastructure, enterprise applications, and sensitive workflows. LARUS One can assign eligible access points globally unique Identity Addresses with evidence for independent review. Each bank, supplier, or other third party decides whether to accept an address, and acceptance is not guaranteed.
USD 6,998 per Identity Unit-yearLocal delivery is separate from the LARUS One subscription.
Value
Privileged access deserves a clear identity layer
Assign Identity Addresses to eligible remote access gateways, privileged workstations, private office networks, secure residence gateways, and controlled access points. Submit rDNS and Identity Passport evidence for independent review; internal security teams, banks, suppliers, and other counterparties decide whether to accept it, and acceptance is not guaranteed.
Identity Address examples
Assign public network identity to the systems that need recognition
- Executive remote access gateway
- Board access endpoint
- Private office gateway
- Secure residence access
- Banking access workstation
- Family office remote access
- Controlled admin workstation
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
Named access points
Document named public Identity Addresses for eligible executive access endpoints.
Controlled delivery
After purchase, choose a Certified Partner, existing provider, or LARUS One Edge path. Provider or location changes are handled as delivery changes.
Evidence
Document the Identity Unit and delivered configuration in the Identity Passport. A provider or location change is handled as a service change; address continuity depends on the completed migration.
Delivery changes
A provider, location, or delivery-path change is handled as a service change. Address continuity depends on the completed migration.
FAQ
Answers to common questions
Is this suitable for private residences?
Yes. Buy an Identity Unit online for a home, private residence, secure residence, or family office, then configure delivery to that location.
Can security policies still control access?
Yes. Customer-managed firewalls, secure-access policy, SASE, and access controls continue to define 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.