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.
Office Egress
Public network identity for office egress and business workflows
Document dedicated public Identity Addresses for office, finance, supplier, application, and security workflows.
USD 6,998 per Identity Unit-yearLocal delivery is separate from the LARUS One subscription.
Value
Document office traffic for independent review
Use Identity Addresses for office egress, finance workstations, executive access, internal applications, APIs, supplier systems, and security reviews. Each address can be named with rDNS and documented in an Identity Passport.
Identity Address examples
Assign public network identity to the systems that need recognition
- Main office egress
- Finance workstation
- Executive remote access
- Office firewall
- Supplier access gateway
- Internal application gateway
- AI workstation group
- Developer API gateway
- Security operations gateway
- Guest network identity
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
Delivery configuration
After purchase, configure a Certified Partner, existing provider, or managed delivery path.
Business evidence
Submit Identity Passport and Allowlist Pack evidence for independent review. Banks, suppliers, customers, and security teams decide whether to accept it, and acceptance is not guaranteed.
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
Can an office use multiple Identity Addresses?
Identity Address availability depends on the delivered configuration and is confirmed after payment.
Can office AI tools use their own Identity Addresses?
AI workstations, coding agents, API tools, and developer gateways can receive named Identity Addresses from the purchased Unit. Available quantity depends on the delivered configuration.
Can we use our existing office provider?
Yes. Choose your existing provider, a Certified Partner, or managed LARUS One delivery. A provider or location change is handled as a delivery change.
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.