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.
Production Server
Public network identity for production servers and networked services
Production systems may need public-address evidence for customer, security, supplier, API, and monitoring reviews. LARUS One can provide named Identity Addresses and documentation for independent review. Each third party decides whether to accept an address, and a provider or location change requires a fresh assessment with no guarantee of address continuity.
USD 6,998 per Identity Unit-yearLocal delivery is separate from the LARUS One subscription.
Value
Make production services easier to document and operate
Use Identity Addresses for application servers, database gateways, monitoring systems, internal APIs, production endpoints, AI service gateways, and customer-facing systems.
Identity Address examples
Assign public network identity to the systems that need recognition
- Production application server
- Database gateway
- Monitoring endpoint
- Internal API gateway
- AI service gateway
- Customer-facing service endpoint
- Operations access point
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 production identities
Assign dedicated Identity Addresses and rDNS names to eligible production services.
Evidence
Document service identity for independent customer, supplier, and security review; third-party acceptance is not guaranteed.
Delivery flexibility
Deploy through an approved provider path. Any provider or location change requires a fresh technical and delivery assessment, and keeping the same address is not guaranteed.
FAQ
Answers to common questions
Can production systems have individual Identity Addresses?
Identity Address availability depends on the delivered configuration and is confirmed after payment.
Can AI service gateways use Identity Addresses?
Yes. AI gateways, model access points, and automation endpoints can be assigned named Identity Addresses.
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.