Identity Unit
The annual continuity asset you buy from LARUS.
Buy, renew, deploy, and document it as the customer continuity asset.
Public network identity
Network identity for the places that need lasting recognition.
Buy an Identity Unit. Deploy it to a home, office, family office, hotel, API edge, enterprise site, or private network. Activate up to 254 globally unique Identity Addresses for the devices, endpoints, computers, applications, servers, gateways, APIs, and trusted access points that need stable public network identity.
LARUS anchors the identity. Your selected provider delivers the network.
Identity Unit
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.
Actual usable count may depend on delivery design, security policy, and local network configuration.
Identity Location
The place where you deploy it: home, office, residence, hotel, cloud edge, or enterprise site.
One deployment profile for one annual continuity asset.
Identity Address
A globally unique public identity you can name and assign to a device, endpoint, computer, server, gateway, application, API, or trusted access point.
Use it where stable public identity matters.
How it works
From purchase to trusted use.
- 1Buy an Identity Unit
Choose the number of annual Identity Units your individual profile or business needs.
- 2Choose a location
Deploy to a home, office, hotel, family office, API edge, private network, or enterprise site.
- 3Select delivery
Choose a Certified Partner, request review of your existing provider, or use a managed LARUS One delivery path.
- 4Activate Identity Addresses
Assign up to 254 globally unique Identity Addresses for the systems and access points that need lasting recognition.
- 5Name your identities
Use rDNS to align each Identity Address with its role, service, location, or trusted access purpose.
- 6Share your Identity Passport
Give banks, suppliers, partners, security teams, and internal teams clear evidence of your public network identity.
Where to use it
One identity model across private and operational locations.
Name your Identity Addresses, configure rDNS, share your Identity Passport, and use your network identity where banks, suppliers, partners, security teams, applications, and private infrastructure need to recognize you.
Delivery
Use the provider you choose. Keep the identity with LARUS.
Your selected provider delivers the local network service. LARUS anchors the public network identity and continuity record.
Certified Partner Delivery
The aligned delivery path for customers who want faster implementation, known escalation, and a provider already prepared for LARUS One.
Existing Provider Review
Keep your current provider relationship and ask LARUS to review the delivery path.
LARUS One Edge
Managed edge delivery for homes, private residences, family offices, and smaller offices that prefer a guided setup.
Why LARUS
Continuity needs an anchor.
LARUS One is built for the public network identities a customer wants to keep using when providers, locations, access methods, or infrastructure change. LARUS anchors the Identity Unit, Identity Addresses, rDNS workflow, Identity Passport, and continuity record, while the selected provider delivers the local network service.
Identity record
LARUS keeps the Identity Unit, active Identity Addresses, deployment record, rDNS workflow, and Identity Passport aligned in one continuity structure.
Provider choice
Customers can use a Certified Partner, request review of an existing provider, or use a guided LARUS One delivery path.
Evidence for trust
Identity Passport and Allowlist Pack help customers share their public network identity with banks, suppliers, partners, security teams, and internal stakeholders.
Works with your security architecture.
Public identity works with firewalls, SASE, routing, segmentation, and access policies. LARUS One gives important endpoints a stable public identity while your security architecture continues to control what is reachable.
From Lu Heng's Notes
The thinking behind LARUS One.
LARUS One comes from Lu Heng's long-running work on public network identity, Internet number continuity, provider independence, and the economics of trusted infrastructure.
Note:68
The economics of network identity
The core LARUS One thesis: customers keep continuity, partners earn delivery revenue, and LARUS anchors public network identity.
Read noteContinuity thesis
Why continuity needs a first-party anchor
A deeper explanation of why long-term network identity depends on a provider built for continuity, evidence, and operational responsibility.
Read noteInternet number context
The governance background behind continuity
Background reading on Internet number governance and why durable network identity requires institutional memory.
Read notePricing
LARUS One Identity Unit
Deploy one Identity Unit to one location. Activate up to 254 globally unique Identity Addresses. Local network delivery is contracted separately with your selected provider.
Actual activation design is confirmed during delivery. Actual usable count may depend on delivery design, security policy, and local network configuration.