Review documentation
Identity Passport and Allowlist Pack provide evidence for independent review; customer approval is not guaranteed.
Customer Allowlist
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.
Identity capacity
One Identity Unit. Up to 254 globally unique Identity Addresses
Each LARUS One Identity Unit can activate up to 254 globally unique Identity Addresses at one deployed location, for the devices, endpoints, computers, servers, gateways, applications, APIs, and trusted access points that need stable public network identity.
The Identity Location is the selected home, office, family office, hotel, enterprise site, API edge, or private network where the Identity Unit is deployed through the LARUS One delivery network.
Actual usable count may depend on delivery design, security policy, and local network configuration.
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
How LARUS One helps
LARUS anchors identity. The selected provider delivers the local network
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.
Related use cases
Explore related ways to use network identity
Deploy
Deploy one Identity Unit to one selected location
Deploy one Identity Unit to one selected location and activate up to 254 globally unique Identity Addresses for the systems that need stable public network identity.
LARUS maintains the Identity Unit, Identity Addresses, Identity Passport, Allowlist Pack, and continuity record. The selected provider delivers the local network service.