The upstream decision
If the holder controlling the address changes its sale or renewal decision, the downstream customer may have little time and no direct path to resolve it.
Certified Delivery Partner Programme
Deliver one network identity on every connection.
Customers buy the annual Identity Unit from LARUS with automatic renewal. Your network delivers it locally as one complete product.
Your application opens in your LARUS provider account, right after sign-in.
For ISPs, hosting providers, data centres and managed network operators.
One Identity Unit serves one Location at a time.
AUTOMATIC RENEWALBuilt into every active Identity Unit.
Customer journey
One product from purchase to everyday service.
LARUS provides the product. The customer chooses where to use it and which certified local provider delivers the connection.
Buy the Identity Unit
The customer buys the annual Identity Unit directly from LARUS.
Choose a Location and Delivery Partner
The customer selects one Location and your certified network as the Delivery Partner for that deployment, or configures its own ASN. The Partner Customer ID identifies the customer in your delivery workflow.
Activate as one service
LARUS prepares the network identity while your team confirms access, routing and installation readiness.
Keep it active
Automatic renewal stays with LARUS. Local network service and support stay with the Delivery Partner.
What the customer avoids
A supplier chain leaves the hard parts with the customer.
One connection can hide a holder, a broker, an address operator and a local provider. When their decisions or queues diverge, the customer becomes the person joining them back together.
The intermediary hand-off
Every added intermediary divides responsibility. A provider can pass the issue upstream while the customer’s production service still waits.
Where operators leave gaps
Routing, RPKI, rDNS, geolocation and abuse handling cross different queues, contracts and escalation paths.
The renumbering burden
When access ends without a workable path forward, renumbering applications, allowlists and customer systems becomes the customer’s migration project.
One product, two accountable operators
The customer always knows who owns the next answer.
LARUS, the customer and the Delivery Partner each hold their own contract. The Partner programme adds one Master Revenue Share Agreement, and customers remain free to use their own ASN or another provider.
Network identity
LARUS
LARUS remains accountable for the annual Identity Unit and its automatic renewal.
- Identity Unit and customer identity record
- Identity Address assignment and address operations
- rDNS workflow and identity naming
- Identity Passport and Allowlist Pack
- Automatic renewal of the active Identity Unit
Local delivery
Delivery Partner
The provider remains accountable for the network and local service it sells and operates.
- Broadband, DIA, cloud, data centre or managed access
- Installation, equipment and on-site work
- Routing, network policy and local operations
- First-line support and operational escalation
- Local service contract and customer relationship
One customer. One clear answer at every layer.
Certification standard
Certification is earned before a service appears in the directory.
The review brings your delivery capability, service coverage and operational ownership together in one clear partner profile for the LARUS directory.
Validated delivery capability
Show the network, ASN, product and technical contacts behind the proposed service.
Specific service coverage
Name the countries, cities and service profiles customers can actually order, with realistic activation estimates.
Named support ownership
Define first-line support, escalation contacts and the operational handoff between your team and LARUS.
Customer-facing clarity
Keep Identity charges, Delivery charges, service limits and each operator’s responsibilities explicit.
Formal application
Show us the service you can stand behind.
The application is for providers ready to document a real delivery product, service area, technical owner and support model.
Apply on behalf of your provider organisation: sign in or create an account to start.
Become a Certified Delivery PartnerNot yet registered? Create a provider account first
WHAT YOU’LL NEED
Prepare these details before you begin
- Provider organisation and authorised operator
- ASN and technical contact email
- Product name, service type and website
- Countries, cities, service profiles and activation estimate
- Customer ID format, support model and escalation ownership
- Service logo and acceptance of the current partner agreement
After you apply, LARUS works with you to confirm partner fit and delivery details, then prepares approved services for directory publication.