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.
Banking Workstation
Public network identity for banking workstations and finance access
Customers may need to document the public addresses used by finance workstations and gateways for access reviews. LARUS One can provide named Identity Addresses and supporting evidence, but each bank or finance system decides whether to accept them and acceptance is not guaranteed.
USD 6,998 per Identity Unit-yearLocal delivery is separate from the LARUS One subscription.
Value
Give financial access a documented address record
Use Identity Addresses for banking workstations, treasury systems, finance APIs, family office operations, payment workflows, counterparty reviews, and supplier finance portals. Financial institutions and other third parties decide whether to accept an address; acceptance is not guaranteed.
Identity Address examples
Assign public network identity to the systems that need recognition
- Banking workstation
- Treasury access gateway
- Family office finance endpoint
- Payment operations gateway
- Finance API access
- Counterparty review endpoint
Shared service model
Every use case follows the same commercial boundary
Identity, local delivery, and customer controls stay separate
LARUS anchors identity. The selected provider delivers the local network.
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.
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
- 01
Start one paid pilot
Create an account and sign in to purchase one annual Identity Unit online.
- 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.
- 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.
- 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
Review documentation
Submit Identity Address names and Identity Passport evidence for independent review. Financial counterparties decide whether to accept them, and acceptance is not guaranteed.
Location delivery
Deploy to an office, family office, secure residence, or private network.
Delivery changes
A provider, location, or delivery-path change is handled as a service change. Address continuity depends on the completed migration.
FAQ
Answers to common questions
Can banks receive an Identity Passport?
Customers can submit an Identity Passport and Allowlist Pack to banks, suppliers, customers, and security teams for independent review. Each third party decides whether to accept it, and acceptance is not guaranteed.
Can finance workstations have separate identities?
Identity Addresses can be assigned to workstations, gateways, applications, and controlled access points from the purchased Unit.
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.