Evidence-ready
Identity Passport and Allowlist Pack give customers a clean review package.
Customer Allowlist
Public network identity for customer allowlists and security reviews.
When customers review, approve, and allowlist network access, they need clear identity evidence. LARUS One provides named Identity Addresses, rDNS workflow, Identity Passport, and Allowlist Pack documentation for customer-facing access.
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 recognize and document.
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 gatewayAPI customer accessProduction service endpointEnterprise integration gatewaySupport system accessCustomer 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.
Continuity
Keep customer allowlists stable as infrastructure and providers change.
FAQ
Customer-facing answers for this use case.
Can customers receive documentation for allowlisting?
Yes. LARUS One supports Identity Passport and Allowlist Pack evidence.
Can different customers use different Identity Addresses?
Yes. Customers can activate multiple Identity Addresses for different integrations, applications, or access workflows.
Related use cases
Continue through the identity workflows connected to this page.
API application identity
Public network identity for APIs, applications, and callbacks.
Use LARUS One Identity Addresses for API allowlists, webhooks, application callbacks, AI tool access, production services, and customer integrations.
View related use caseProduction server identity
Public network identity for production servers and trusted services.
Give production servers stable public network identity with named Identity Addresses, rDNS workflow, customer evidence, and provider-portable continuity.
View related use caseSupplier access identity
Public network identity for supplier access and trusted B2B workflows.
Use LARUS One Identity Addresses for supplier allowlists, vendor portals, operations systems, logistics workflows, and trusted B2B access.
View related use caseSecurity gateway identity
Public network identity for security gateways and trusted access points.
Give firewalls, SASE gateways, security monitoring systems, access controls, and trusted security endpoints stable public network identity.
View related use caseAI coding agents and API identity
Public network identity for AI coding agents, developer endpoints, and API workflows.
Give AI coding agents, developer workstations, API sandboxes, model gateways, and automation endpoints stable public network identity with LARUS One Identity Addresses.
View related use caseDeploy
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.