Skip to main content
Identity Passport continuity evidence landscape

Continuity evidence

Document One Network Identity for independent review

Give your IT team, delivery provider and counterparties one current picture of your identity service. Share the details they need in a customer-controlled PDF.

Included with the USD 6,998 annual Identity Unit. Local delivery is separate.

Start one paid pilotSee what the Passport records

Inside the Passport

One current record of the paid Unit and its active deployment

The PDF is generated from the customer's authenticated service record. Download a fresh copy after a service change to give the next reviewer current context.

Why LARUS One

Identity Passport

Current service record

Customer-controlled PDF
Customer and Identity Unit
Customer legal name, LARUS One account ID, Unit name, and Unit reference.
Current deployment
Active Location, Location type, deployment status, and selected Delivery Partner.
Identity Addresses
Current active, pending, and reserved counts plus the approved addresses shown after activation.
rDNS names
The current names associated with documented Identity Addresses.
Continuity state
Issue date, continuity status, deployment status, and the current delivery path.
Operating guidance
Allowlist use, support escalation, and router or firewall review guidance.

Who reviews it

Help reviewers understand the identity before they decide access

Bring customer, Location and delivery details together for the teams you work with. Share the context each reviewer needs when setting up or updating a workflow.

01

Counterparty security and risk

Review a named network endpoint before deciding whether to recognize or allowlist it.

02

Enterprise IT and procurement

Match the paid identity service to its current Location, provider, operating status, and support path.

03

Hospitality and property operations

Document the identity used for reviewed property, payment, supplier, staff, or premium-service workflows.

04

Family office and managed IT

Keep residence, office, advisor, banking, security, and managed-service review context together.

Evidence boundary

Document the service without promising the reviewer's decision

Identity Passport

A downloadable snapshot of the customer, paid Unit, current deployment, delivery path, named addresses, rDNS, and continuity state.

Allowlist Pack

Supporting context for a reviewer assessing named Identity Addresses and rDNS. It accompanies the Passport; it is not a separate security approval.

Independent decision

The receiving bank, supplier, customer, API provider, auditor, or security team applies its own policy and decides recognition or access.

From pilot to evidence

From your first pilot to a current service record

The evidence starts with a paid Unit and confirmed delivery. It stays useful when customers download a current copy after approved service changes.

  1. 01

    Start one paid pilot

    Buy one annual Identity Unit online and choose the first Location that needs a durable network identity.

  2. 02

    Activate the Location

    Confirm the separate delivery path, routing, named Identity Addresses, rDNS, and support ownership.

  3. 03

    Generate the current Passport

    After the Unit has a Location, download the current PDF from the authenticated client portal.

  4. 04

    Share for independent review

    The customer chooses the recipient and shares the Passport and relevant Allowlist Pack context.

  5. 05

    Reassess service changes

    A provider or Location change requires a new technical and delivery assessment. Download a current Passport after the approved change.

Included with the annual Unit

Create the evidence from one real pilot Location

The USD 6,998 annual Identity Unit includes Identity Passport and Allowlist Pack management. Local delivery, installation, equipment, taxes, and third-party services are separate.

Review the full annual price
Start one paid pilot

FAQ

Identity Passport and review questions

What is an Identity Passport?

It is a customer evidence PDF for the paid Identity Unit and its current deployment. It records the customer, Unit, Location, delivery path, Identity Addresses, rDNS, operating status, continuity state, and support context available for that deployment.

When can a customer download the Identity Passport?

The Identity Passport becomes available in the authenticated client portal after the Identity Unit has a Location. Identity Addresses appear after activation.

Is Identity Passport included in the annual price?

Yes. Identity Passport and Allowlist Pack management are included with the USD 6,998 annual Identity Unit. Local network delivery, installation, equipment, taxes, and third-party services are separate.

How is the Allowlist Pack different?

The Identity Passport documents the broader current service record. The Allowlist Pack provides supporting context when a specific reviewer assesses named Identity Addresses and rDNS. Neither replaces the reviewer's own security or access policy.

Does the Passport guarantee allowlisting or approval?

No. It supports independent review. Each bank, supplier, customer, API provider, auditor, and security team decides whether to recognize or allowlist an address.

Is the Identity Passport public?

No. It is generated inside the authenticated client portal. The customer controls who receives the downloaded PDF and any supporting review context.

What happens after a provider or Location change?

Your identity service stays with LARUS. A provider or Location change requires a new technical and delivery assessment. Download a current Passport after the approved change.