FAQ
Delivery Partner FAQ
LARUS One is designed so each party keeps the role it is best placed to perform: LARUS anchors identity, the partner delivers local service, and the customer keeps continuity.
Who is the end customer?
The customer selects a delivery partner for a specific LARUS One deployment. The local network service is provided through the partner's own customer relationship, service terms, onboarding process, and support model.
What does the partner deliver?
The partner delivers the local network service: broadband, DIA, managed network, SASE, CPE, installation, local routing, DDoS options, bandwidth plans, and local support where applicable.
What does LARUS deliver?
LARUS provides the Identity Unit, Identity Addresses, rDNS workflow, Identity Passport, deployment record, and continuity record anchored by LARUS.
How does revenue share work?
The customer pays LARUS for the LARUS One identity continuity layer. When a certified partner delivers the selected location, LARUS shares LARUS One revenue with the delivery partner.
How are bandwidth and traffic handled?
Bandwidth, access, local service plans, throughput, DDoS options, and traffic policies are handled through the partner's own service relationship with the customer. LARUS One revenue share is incremental to the partner's local service revenue.
How are compliance and customer records handled?
The partner keeps its own local customer relationship and compliance process. LARUS maintains the LARUS One identity record, including Identity Unit, Identity Location, active Identity Addresses, rDNS, and delivery status.
Can a partner decline or pause delivery?
A delivery partner may apply its local service policies, support process, and network protection procedures. LARUS and the partner coordinate identity status, delivery status, and customer communication.