The customer buys identity from LARUS.
LARUS maintains the Identity Unit, Identity Addresses, rDNS workflow, Identity Passport, Allowlist Pack, renewal record, and continuity record.
Certified Delivery Partner Program
Add public network identity to the access you already sell.
The program lets providers attach a documented identity layer to business access, cloud edge, data center, SASE, and managed network services. You operate the delivery path. LARUS anchors the identity record.
Mid-country operator model
A 1% attach rate can become a board-level revenue line.
Use a typical operator size in a mid-sized country: 10 million end customers, 1% qualified adoption, and 30% partner revenue share on paid identity continuity.
10M
Typical operator customer base in a mid-sized country.
1%
Qualified attach rate creates 100,000 Identity Units.
$209.94M/yr
Annual partner share before incremental managed-service fees.
~100%
Potential EBITDA-scale uplift if current EBITDA is about $210M.
The access business stays intact: delivery, routing, support, and managed service revenue remain with the provider.
Business locations with named public identity
API, automation, and AI endpoint recognition
Clear attribution above access service
Premium customer environments
Service areas customers can keep using
A new annual revenue layer above access service.
The product is sold as an annual Identity Unit. Each Identity Unit is priced at USD 6,998/year and can activate up to 254 globally unique Identity Addresses at one selected location. Approved partners participate in qualified Identity Unit revenue while still charging for broadband, DIA, cloud, data center, SASE, routing, installation, managed service, and support.
The customer buys delivery from you.
The provider contracts local access, broadband, DIA, routing, managed router, SASE handoff, cloud edge, data center service, support, and local operations.
The partner agreement defines the economics.
Certification, qualified revenue, 30% share, attribution, renewal handling, billing coordination, support boundaries, escalation, and listing requirements are defined before launch.
Partner economics
Attach paid identity continuity to customers already buying access.
Each Identity Unit is priced at $6,998 per year. A 30% partner revenue share equals $2,099.40 per year, or $174.95 per month when averaged monthly. For a 10-million-customer operator, 1% qualified adoption creates 100,000 Identity Units and $209.94 million in annual partner share before any extra managed-service revenue.
100,000
qualified Identity Units at 1% attach from 10 million end customers
$17.50M/mo
average monthly partner share before extra managed-service fees
$209.94M/yr
annual partner share at the 1% attach scenario
Math: 10,000,000 end customers x 1% qualified attach = 100,000 Identity Units. 100,000 x ($6,998 x 30%) = $209,940,000 per year, or $17,495,000 per month. The ~100% EBITDA-scale uplift assumes current annual EBITDA around $210M and low incremental delivery cost because access revenue remains separately charged.
Delivery stays with the provider
Add identity above the path you already operate.
The customer buys a stable public identity layer. The provider still sells and operates the access path, routing handoff, managed service, support, and local escalation.
Customers do not buy this for more bandwidth.
They buy it because some public IP workflows have become part of how their business is recognized. The product is relevant when public network identity is used by banks, suppliers, API providers, security teams, compliance teams, internal systems, production servers, privileged users, or partner allowlists.
The customer gets continuity.
Public identity remains documented and portable across provider changes, routing changes, migrations, and security reviews.
The provider keeps the delivery relationship.
The customer still needs local access, routing, managed service, support, traffic policy, and escalation from the selected provider.
LARUS anchors the identity record.
LARUS maintains the Identity Unit, Identity Addresses, rDNS workflow, Identity Passport, renewal, and continuity evidence.
Where providers attach identity continuity.
The fastest attach points are accounts where public identity is already operationally important: finance access, supplier portals, API access, customer allowlists, production systems, security gateways, AI workflows, and compliance records.
Offer identity continuity above office egress.
Attach identity continuity to customers that need stable public identity for finance systems, supplier portals, API access, partner allowlists, and security reviews.
Add documented identity to workloads.
Support APIs, callbacks, production services, self-hosted runners, developer endpoints, AI workflows, and customer-facing applications.
Help tenants move without identity resets.
Keep a stable identity layer across provider changes, routing changes, migrations, disaster recovery events, and customer security reviews.
Give selected gateways named identity.
Use globally unique Identity Addresses while the customer's firewall, segmentation, SASE, and access policies continue controlling reachability.
Sell a premium network option.
Serve locations where business customers need dedicated public identity instead of anonymous shared access.
Stabilize trusted automation endpoints.
Support customers whose AI agents, build systems, API clients, and automation workers need recognized public identity.
Office, DIA, and business access accounts
Cloud, API, automation, and AI workloads.
Use stable documented public identity for customer-facing endpoints, API callbacks, build systems,
AI workers, and security allowlists.
Service areas listed by provider coverage.
Certified partners can be presented by city, country, or coverage model so customers know where
local delivery can be supported.
Provider control
Identity above access. Control stays with the provider.
The product does not create a new circuit, bypass provider controls, or move local support away from the selected provider. It gives selected endpoints stable documented public identity while traffic continues over the contracted delivery service.
Policy stays local.
Firewall, access control, traffic policy, acceptable-use rules, and fair-use enforcement remain
with the customer and provider.
Delivery stays yours.
Broadband, DIA, cloud, data center, SASE, routing handoff, managed router, and local support stay
under the provider relationship.
Identity is documented.
LARUS maintains the Identity Unit, Identity Addresses, rDNS workflow, Identity Passport,
continuity evidence, and reputation escalation path.
Attribution improves.
Dedicated Identity Addresses make public network identity clearer than shared NAT or CGNAT for
security reviews and partner allowlists.
Attribution remains visible
Operational responsibility is separated.
This separation lets providers add identity continuity without turning LARUS into the access provider and without turning the provider into the identity anchor.
What LARUS handles.
- Identity Unit and Identity Address records
- rDNS workflow, Identity Passport, and Allowlist Pack
- Renewal status and provider-change continuity
- Identity-side evidence, reputation escalation, and certification record
What the provider handles.
- Customer access service and local delivery contract
- Broadband, DIA, cloud, data center, SASE, routing, and handoff
- Installation, activation, managed router or gateway service
- Traffic policy, fair-use enforcement, local support, and customer service
Certified delivery
Certification makes the provider easier to choose.
A Certified Delivery Partner is prepared to deliver the identity product through a defined service area, service type, support model, activation process, and escalation workflow. The mark helps customers see that the provider is ready for identity delivery, not just generic transit.
Website: show the mark on product pages, solution pages, partner pages,
and service pages that sell certified delivery; clickable marks should link to the same product page.
Offline: use the mark in sales decks, brochures, event handouts,
service catalogs, and account presentations where the partner sells the delivery service.
Advertising: include the mark in campaign landing pages, sponsored
posts, webinar pages, marketplace promotions, and launch announcements for certified delivery.
Certified Delivery Partner Program
Approval path
Apply. Qualify. Align. Launch.
Certification is reserved for providers that can support customer qualification, delivery planning, routing coordination, local operations, and escalation.
Submit service areas, delivery types, support model, routing capability, and target customer segments.
LARUS reviews delivery readiness, activation workflow, AUP enforcement, and escalation ownership.
The agreement defines qualified revenue, attribution, billing coordination, renewal handling, and support boundaries.
Approved partners can be listed by service area, deliver local access and support, and earn qualified Identity Unit revenue.
Commercial outcome
Qualified identity revenue above the access you already sell.
Customers buy documented identity continuity. Providers keep the delivery relationship. LARUS maintains the Identity Unit, Identity Addresses, rDNS workflow, and continuity record.
Review the product mechanics first, then start partner review for service area, delivery model, support ownership, escalation path, and revenue-share terms.
