Up to 254 globally unique Identity Addresses
Activate named public identities for the systems and workflows that need stable recognition.

Identity Units
An Identity Unit is the annual LARUS One asset you buy, renew, and deploy. Each Identity Unit can activate up to 254 globally unique Identity Addresses at one deployed location for devices, endpoints, computers, servers, gateways, applications, APIs, and trusted access points that need stable public network identity.
Included
Actual activation design is confirmed during delivery. Actual usable count may depend on delivery design, security policy, and local network configuration.
Activate named public identities for the systems and workflows that need stable recognition.
Activate named Identity Addresses for banks, suppliers, APIs, servers, offices, private residences, hotels, applications, and privileged access points that need stable public network identity.
Deploy one Identity Unit to the home, office, hotel, family office, API edge, private location, or enterprise site that needs continuity.
Keep reverse DNS aligned with the business systems that rely on stable trust.
Download customer evidence for allowlists, onboarding, reviews, and support escalation.
Give counterparties a clean package for trusted access and security review.
Use a Certified Partner, existing provider review, LARUS One Edge, or advanced delivery path.
Keep public network identity continuity anchored across provider and location changes.
Use cases
Give AI coding agents, developer workstations, API sandboxes, model gateways, and automation endpoints stable public network identity.
Explore use caseGive an office a stable public network identity for recurring trusted workflows.
Explore use caseSupport executive access with named Identity Addresses and continuity evidence.
Explore use caseGive a private residence a recognizable identity for trusted access and managed IT.
Explore use caseUse stable public network identity where banks and finance teams need recognition.
Explore use caseShare clear evidence with suppliers and operational counterparties.
Explore use caseGive customers a stable identity for security review and access policy.
Explore use caseDocument server identity for counterparties, support, and reviews.
Explore use caseUse named Identity Addresses for API access, callbacks, and application allowlists.
Explore use caseAssign stable identity to rooms, suites, and premium guest services.
Explore use caseSupport hospitality payment and property systems with documented identity.
Explore use caseKeep identity evidence aligned with security systems and access controls.
Explore use caseSupport advisors, private infrastructure, and family office operations.
Explore use case