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.
Supplier Access
Public network identity for supplier access and B2B workflows
Supplier systems, vendor portals, logistics workflows, and operational counterparties may request public-address documentation. LARUS One can provide named Identity Addresses and evidence for independent review; each supplier 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
Document supplier workflows for independent review
Use Identity Addresses for supplier portals, procurement systems, logistics tools, vendor APIs, finance operations, and controlled operational access points.
Identity Address examples
Assign public network identity to the systems that need recognition
- Supplier portal access
- Procurement gateway
- Vendor API access
- Logistics system endpoint
- Finance supplier gateway
- Operations access review
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
Allowlist Pack
Package Identity Addresses, rDNS names, and operational purpose for independent supplier review; onboarding approval is not guaranteed.
Delivery change assessment
A provider or location change requires a fresh technical and delivery assessment. Keeping the same address is not guaranteed.
Business deployment
Deploy to offices, enterprise sites, data centers, API edges, and private networks.
FAQ
Answers to common questions
Can suppliers use these addresses for allowlists?
Customers can submit named Identity Addresses and Allowlist Pack documentation to suppliers for independent review. Each supplier decides whether to allowlist an address, and acceptance is not guaranteed.
Can supplier access be separated from ordinary office traffic?
Yes. Identity Addresses can be assigned to specific gateways, applications, or access workflows.
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.