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.
Customer Allowlist
Public network identity for customer allowlists and security reviews
When customers review network access, they may request clear address evidence. LARUS One provides named Identity Addresses, rDNS workflow, Identity Passport, and Allowlist Pack documentation for independent review; each customer decides whether to approve or allowlist an address.
USD 6,998 per Identity Unit-yearLocal delivery is separate from the LARUS One subscription.
Value
Make customer-facing access easier to document and review
Use Identity Addresses for production services, API access, enterprise integrations, customer allowlists, support systems, and security reviews.
Identity Address examples
Assign public network identity to the systems that need recognition
- Customer allowlist gateway
- API customer access
- Production service endpoint
- Enterprise integration gateway
- Support system access
- Customer security review endpoint
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
Review documentation
Identity Passport and Allowlist Pack provide evidence for independent review; customer approval is not guaranteed.
Named addresses
Assign rDNS names that match access purpose and operational ownership.
Delivery changes
An infrastructure, provider, or location change requires a fresh technical and delivery assessment. Keeping the same address or allowlist entry is not guaranteed.
FAQ
Answers to common questions
Can customers receive documentation for allowlisting?
LARUS One provides Identity Passport and Allowlist Pack evidence for independent review. Each customer decides whether to allowlist an address, and acceptance is not guaranteed.
Can different customers use different Identity Addresses?
Yes. Customers can activate multiple Identity Addresses for different integrations, 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.