Allowlist Pack
Package Identity Addresses, rDNS names, and operational purpose for independent supplier review; onboarding approval is not guaranteed.
Supplier Access
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.
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
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
How LARUS One helps
LARUS anchors identity. The selected provider delivers the local network
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.
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.