Public network identity for production servers and networked services.

Production Server

Production Server

Public network identity for production servers and networked services.

Production systems may need public-address evidence for customer, security, supplier, API, and monitoring reviews. LARUS One can provide named Identity Addresses and documentation for independent review. Each third party decides whether to accept an address, and a provider or location change requires a fresh assessment with no guarantee of address continuity.

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 document 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 server
  • Database gateway
  • Monitoring endpoint
  • Internal API gateway
  • AI service gateway
  • Customer-facing service endpoint
  • Operations access point

How LARUS One helps

LARUS anchors identity. The selected provider delivers the local network

Named production identities

Assign dedicated Identity Addresses and rDNS names to eligible production services.

Evidence

Document service identity for independent customer, supplier, and security review; third-party acceptance is not guaranteed.

Delivery flexibility

Deploy through an approved provider path. Any provider or location change requires a fresh technical and delivery assessment, and keeping the same address is not guaranteed.

FAQ

Answers to common questions

Can production systems have individual Identity Addresses?

Up to 254 globally unique Identity Addresses is the technical maximum for one Identity Unit at one approved deployed location, not a guaranteed quantity. The available quantity is confirmed after technical and delivery assessment.

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

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.

LARUS OneIdentity Unit

One Unit · One Location

Start Identity Unit purchase