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.
Security Gateway
Public network identity for security gateways and controlled access points
Security gateways, firewalls, SASE edges, monitoring systems, access controls, and administrative endpoints may need public-address evidence for customer, supplier, and internal reviews. LARUS One can provide named Identity Addresses and documentation; each reviewer decides whether to accept it, and acceptance is not guaranteed.
USD 6,998 per Identity Unit-yearLocal delivery is separate from the LARUS One subscription.
Value
Support security review with documented network identity
Use Identity Addresses for firewalls, SASE gateways, Zero Trust access points, monitoring gateways, SOC systems, residence security systems, and administrative endpoints.
Identity Address examples
Assign public network identity to the systems that need recognition
- Firewall gateway
- SASE edge
- Security monitoring endpoint
- Access control gateway
- SOC connector
- Admin workstation
- Residence security gateway
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
Named security endpoints
Give security infrastructure clear public identity and rDNS naming.
Policy alignment
Submit Identity Passport and Allowlist Pack evidence for independent customer security review; approval is not guaranteed.
Delivery changes
A provider, location, or architecture change requires a fresh technical and delivery assessment. Keeping the same address is not guaranteed.
FAQ
Answers to common questions
Does public identity change security policy?
Public identity works with the customer security architecture. Firewalls, SASE, routing, segmentation, and access policies continue to control what is reachable.
Can security devices have distinct Identity Addresses?
Yes. Identity Addresses can be assigned to gateways, access points, monitoring systems, and security workflows.
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.