Answers before your first paid pilot

An Identity Unit is your annual LARUS One subscription for one managed Network Identity. Use it at one active Location at a time, with LARUS responsible for the identity service and renewal.

A fixed IP from one ISP is tied to that provider's connection. With LARUS One, your Network Identity service and renewal stay with LARUS while your local delivery provider can change.

LARUS One is not a VPN, proxy, anonymity service, address rental, cybersecurity product, or local internet connection.

USD 6,998 per Unit covers one year of the managed Network Identity service. Location profiles are free. Checkout taxes and local installation, connectivity, routing, equipment and on-site services are separate.

IPv4 addresses are assigned for use during the active subscription. Purchasing a subscription does not transfer ownership of the addresses to the customer.

No. Choose an available Certified Delivery Partner or an existing provider that supports BYOIP. LARUS and the provider confirm the Location, delivery design, costs and activation before use.

It means using a provider that can route the LARUS-assigned Identity Addresses for the customer's Location. It does not mean the customer must own or contribute the address space.

LARUS guarantees renewal of your Network Identity service, supported by its RIR shareholder-equivalent continuity rights and operating team. Renew with LARUS while local delivery can change.

Keep your identity service with LARUS while changing local delivery. LARUS and the provider assess the new Location and delivery path, confirm costs and validate activation before use.

After activation, the Identity Passport and Allowlist Pack help you show your identity and current deployment to the organizations that need to recognize it. They support a review; the receiving organization makes its own access decision.

Yes. Create an account, sign in, and purchase one or more annual Identity Units online without an application or sales approval. Select the first Location and local delivery path after payment.

Sign in with the email address on the account, open the affected Identity Unit and Location, and begin with that service context. If account access is the problem, email public support from the account email address when possible.