For network providers and managed delivery teams
Keep your local connectivity and support relationship. Add ongoing network identity and LARUS-guaranteed renewal to the services you deliver.
The customer buys LARUS One. The customer and partner contract separately for local delivery.
Who should apply
Certification is for providers and managed delivery teams that can define a real service boundary, operate it, and support the customer after activation.
You can own access, installation, routing, equipment, on-site work, and local service for named customer Locations.
You can publish realistic activation assumptions and provide a named support, incident, and escalation path.
You can contract transparently with customers, jointly qualify opportunities, and coordinate delivery evidence with LARUS.
LARUS reviews the application and controls publication. The customer still approves each Location, contract, quote, design, activation, and third-party dependency independently.
Commercial model
The product, local delivery, and partner program are related, but they are not one bundled contract or one public price.
Delivery models
Both models require a Location-specific technical and commercial review. Neither changes what the customer buys from LARUS.
Partner path
Certification follows evidence and an agreed operating model; it is not an instant logo submission or self-published listing.
Share the provider identity, delivery capability, service areas, support model, and the types of customers you can serve.
LARUS reviews the operating, customer-support, commercial, and delivery evidence before certification.
Confirm joint-selling, separate contracting, delivery coordination, certification, and the agreed revenue-share terms.
Define the customer Location, identity requirement, connectivity model, local scope, activation assumptions, and acceptance criteria.
Coordinate routing, RPKI, rDNS, installation, activation, support ownership, and evidence without blurring the three parties' responsibilities.
After approval, publish only the reviewed service areas and delivery details. Update them when availability or operating scope changes.
Certified Delivery Partner
Request the current application. LARUS will return the evidence, commercial, delivery, and publication requirements for review.
FAQ
No. Certification records an approved partner relationship and reviewed public service information. It does not guarantee customer demand, opportunity volume, revenue, capacity, or selection for a specific Location.
The customer contracts with LARUS for the annual identity service and contracts separately with the selected Delivery Partner for local connectivity, installation, equipment, and support. The LARUS-partner relationship is a separate agreement.
Revenue share is agreed in the applicable LARUS-partner commercial terms for eligible delivery. There is no universal public percentage, and local customer charges remain governed by the separate partner-customer agreement.
An approved BYOIP arrangement may be used when the resources, registry authority, routing design, RPKI, security boundary, and operating responsibilities pass technical and commercial review. BYOIP is not automatic certification.
The directory publishes reviewed partner identity, service areas, service type, status, and activation estimate. It is not a live capacity reservation, customer quote, acceptance guarantee, or promise of third-party treatment.