Identity Units

Each Identity Unit can activate up to 254 globally unique Identity Addresses at one deployed location.

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

A renewable identity asset for trusted public recognition.

Actual activation design is confirmed during delivery. Actual usable count may depend on delivery design, security policy, and local network configuration.

Up to 254 globally unique Identity Addresses

Activate named public identities for the systems and workflows that need stable recognition.

Designed for trusted use

Activate named Identity Addresses for banks, suppliers, APIs, servers, offices, private residences, hotels, applications, and privileged access points that need stable public network identity.

One active location deployment

Deploy one Identity Unit to the home, office, hotel, family office, API edge, private location, or enterprise site that needs continuity.

rDNS workflow

Keep reverse DNS aligned with the business systems that rely on stable trust.

Identity Passport

Download customer evidence for allowlists, onboarding, reviews, and support escalation.

Allowlist Pack

Give counterparties a clean package for trusted access and security review.

Provider delivery workflow

Use a Certified Partner, existing provider review, LARUS One Edge, or advanced delivery path.

Continuity anchored by LARUS

Keep public network identity continuity anchored across provider and location changes.

Use cases

Use your Identity Addresses where lasting recognition matters.

Office egress

Give an office a stable public network identity for recurring trusted workflows.

Executive VPN

Support executive access with named Identity Addresses and continuity evidence.

Private residence gateway

Give a private residence a recognizable identity for trusted access and managed IT.

Banking workstation

Use stable public network identity where banks and finance teams need recognition.

Supplier access

Share clear evidence with suppliers and operational counterparties.

Customer allowlist

Give customers a stable identity for security review and access policy.

Production server

Document server identity for counterparties, support, and reviews.

API application

Use named Identity Addresses for API access, callbacks, and application allowlists.

Hotel room identity

Assign stable identity to rooms, suites, and premium guest services.

POS and PMS systems

Support hospitality payment and property systems with documented identity.

Security gateway

Keep identity evidence aligned with security systems and access controls.

Family office systems

Support advisors, private infrastructure, and family office operations.