Allowlist Pack
Package Identity Addresses, rDNS names, and support contact information for supplier onboarding.
Supplier Access
Public network identity for supplier access and trusted B2B workflows.
Supplier systems, vendor portals, logistics workflows, and operational counterparties often need to recognize a stable public network identity. LARUS One gives supplier-facing access points named Identity Addresses that can be documented and shared.
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
Give supplier workflows an identity they can recognize.
Use Identity Addresses for supplier portals, procurement systems, logistics tools, vendor APIs, finance operations, and approved operational access points.
Identity Address examples
Assign public network identity to the systems that need recognition.
Supplier portal accessProcurement gatewayVendor API accessLogistics system endpointFinance supplier gatewayApproved operations access
How LARUS One helps
LARUS anchors identity. The selected provider delivers the local network.
Stable recognition
Keep supplier access consistent across provider and location changes.
Business deployment
Deploy to offices, enterprise sites, data centers, API edges, and private networks.
FAQ
Customer-facing answers for this use case.
Can suppliers use these addresses for allowlists?
Yes. Customers can share named Identity Addresses and Allowlist Pack documentation with suppliers.
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
Continue through the identity workflows connected to this page.
Office egress identity
Public network identity for office egress and trusted business workflows.
Give office networks stable public identity for employees, finance systems, supplier access, security reviews, applications, and trusted workflows.
View related use caseCustomer allowlist identity
Public network identity for customer allowlists and security reviews.
Give customers stable Identity Addresses for allowlists, security review, API access, supplier systems, and trusted enterprise connectivity.
View related use caseAPI 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 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 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.