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.
AI Workflows
Public network identity for AI coding agents, developer endpoints, and API workflows
AI work now runs across homes, offices, developer workstations, self-hosted runners, model gateways, API sandboxes, and private automation. LARUS One can assign eligible endpoints globally unique Identity Addresses with documentation for independent review. Each 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
AI workflows need clean identity at the network edge
Document dedicated public Identity Addresses for eligible AI coding agents, developer workstations, API sandboxes, model gateways, and automation endpoints.
Identity Address examples
Assign public network identity to the systems that need recognition
- AI coding agent gateway
- Self-hosted runner
- Internal API gateway
- Model gateway
- MCP server
- Webhook receiver
- Automation sandbox
- Developer workstation
- Office AI lab
- Home AI workstation
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 AI endpoints
Assign Identity Addresses to AI workstations, coding agents, runners, gateways, API sandboxes, and automation endpoints.
API review evidence
Document a named public address for API allowlists, webhook callbacks, supplier systems, enterprise security reviews, and internal access controls. Third-party approval is not guaranteed.
Home and office delivery
Bring globally unique Identity Addresses to the home, office, family office, lab, or enterprise site where AI workflows actually run.
Identity Passport
Document the Identity Unit, deployed location, active Identity Addresses, rDNS names, and delivery status for security and operations teams.
Continuity anchored by LARUS
A carrier, provider, or deployment Location can change. Your renewable Identity Unit, named access, and verification record remain the continuity layer.
FAQ
Answers to common questions
Why do AI workflows need public network identity?
AI agents, coding tools, API sandboxes, and automation systems often interact with external services that use allowlists, logs, callbacks, and access policies. A named public address provides documented evidence for independent review, but each external service decides whether to accept it and acceptance is not guaranteed.
Can I use LARUS One for AI work from home?
Yes. Buy an Identity Unit online for a home, private residence, secure residence, or family office, then configure delivery to that location.
Can different AI tools use different Identity Addresses?
Identity Address availability depends on the delivered configuration and is confirmed after payment.
Does public identity change my security controls?
Public identity works with the customer security architecture. Firewalls, SASE, routing, segmentation, and access policies continue to control what is reachable.
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.