Named production identities
Assign stable Identity Addresses and rDNS names to production services.
Production Server
Public network identity for production servers and trusted services.
Production servers are recognized by customers, security teams, suppliers, APIs, and monitoring systems. LARUS One gives production systems named Identity Addresses that can be documented, trusted, and maintained across provider changes.
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 production services easier to recognize and operate.
Use Identity Addresses for application servers, database gateways, monitoring systems, internal APIs, production endpoints, AI service gateways, and customer-facing systems.
Identity Address examples
Assign public network identity to the systems that need recognition.
Production application serverDatabase gatewayMonitoring endpointInternal API gatewayAI service gatewayCustomer-facing service endpointOperations access point
How LARUS One helps
LARUS anchors identity. The selected provider delivers the local network.
Evidence
Document service identity for customers, suppliers, and security teams.
Delivery flexibility
Deploy through a selected provider path while continuity remains anchored by LARUS.
FAQ
Customer-facing answers for this use case.
Can production systems have individual Identity Addresses?
Yes. One Identity Unit can activate up to 254 globally unique Identity Addresses at one deployed location.
Can AI service gateways use Identity Addresses?
Yes. AI gateways, model access points, and automation endpoints can be assigned named Identity Addresses.
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 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 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 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.