Skip to main content
Public network identity for family offices and private infrastructure.

Family Office

Public network identity for family offices and private infrastructure

Family offices operate across residences, offices, advisors, finance systems, private servers, managed IT, and security workflows. LARUS One can provide named Identity Addresses and evidence for independent review; every bank, advisor, supplier, or other third party decides whether to accept an address, and acceptance is not guaranteed.

USD 6,998 per Identity Unit-yearLocal delivery is separate from the LARUS One subscription.

Value

Document each selected family office delivery location

Use Identity Addresses for family office systems, residence gateways, finance workstations, advisor access, private servers, executive remote access, AI workstations, and managed IT handoffs.

Identity Address examples

Assign public network identity to the systems that need recognition

  • Family office gateway
  • Residence gateway
  • Banking workstation
  • Advisor access point
  • Private server
  • Executive remote access
  • AI workstation
  • Managed IT access
  • Security system gateway

Shared service model

Every use case follows the same commercial boundary

01

Scale by active Location, not by address count

People, devices, rooms, network segments, and workflows do not change the subscription count. Count the Locations used at the same time.

02

Identity, local delivery, and customer controls stay separate

LARUS anchors identity. The selected provider delivers the local network.

03

Evidence supports review; every third party decides its own acceptance policy

Identity Passport and Allowlist Pack evidence supports independent review. Every third party applies its own policy and decides access.

04

Customer controls

Public identity works with the customer security architecture. Firewalls, SASE, routing, segmentation, and access policies continue to control what is reachable.

From use case to paid pilot

Your first paid pilot

  1. 01

    Start one paid pilot

    Create an account and sign in to purchase one annual Identity Unit online.

  2. 02

    Add the first Location

    After purchase, add the office, property or other place where you will use the identity. Location profiles are free; one Unit serves one active Location at a time.

  3. 03

    Arrange delivery and activate

    Choose an available Certified Partner or an existing provider that supports BYOIP. LARUS and your provider confirm the delivery design and validate activation before you use the identity at that Location.

  4. 04

    Review Identity Passport evidence

    Review the Identity Passport and allowlist evidence, validate the workflow, then add one Unit for each additional active Location.

How LARUS One helps

LARUS anchors identity. The selected provider delivers the local network

01

Private infrastructure identity

Assign globally unique Identity Addresses from the purchased Unit to systems that need documented public addressing.

02

Discreet documentation

Submit Identity Passport and Allowlist Pack evidence for independent review. Counterparties decide whether to accept it, and acceptance is not guaranteed.

03

Delivery choice

After purchase, choose a Certified Partner, existing provider, or LARUS One Edge path. Provider or location changes are handled as delivery changes.

FAQ

Answers to common questions

Can one family office deploy multiple Identity Units?

Yes. Customers can purchase multiple Identity Units online. Each concurrent residence or office location uses its own Unit and delivery configuration.

Can residence and office systems both use LARUS One?

Yes. Purchase and configure one Identity Unit for each residence or office location that needs a concurrent network identity.

One paid pilot

Choose one workflow and one Location to validate first

Confirm local delivery, routing, evidence, and reviewer fit before adding more active Locations.