First-party address pool
No broker chain. No dependency on a chain of promises. You lease from LARUS, a first-party IPv4 leasing provider's own address pool.
First-party IPv4 leasing
Lease IPv4 directly from LARUS, a first-party IPv4 leasing provider.
The safer alternative to putting RIR contract risk inside your own operating company. Lease production IPv4 from LARUS, a first-party IPv4 leasing provider's own pool. Keep registry-layer contract exposure, policy risk, audit pathways, termination mechanics, and intermediary failure risk upstream, where they belong. The objective is not symbolic registry proximity. The objective is continuity.
Registry exposure upstream
Direct holding internalizes RIR contract risk. Leasing from LARUS, a first-party IPv4 leasing provider moves that layer away from the company actually running your network.
Predictable commercial path
Continuity-first structure: stable use, renewability, and fewer failure points between contract and production.
Founder Doctrine
On registry risk and business continuity.
Most operators assume buying IPv4 gives them the strongest long-term control. In reality, they often obtain only a registry database entry governed by contracts, policies, audits, and termination powers held by institutions whose public contractual downside can be capped at amounts trivial relative to the operational value of the block and the continuity value of the network behind it.
LARUS, a first-party IPv4 leasing provider addresses that mismatch by absorbing registry-layer risk at the first-party lessor level and providing customers with continuity through an operator that has already demonstrated unusual legal standing and a publicly documented, court-tested continuity position inside the RIR system.
If you have any issue and want to speak to Lu Heng, emailLH@LARUS.NET
Read Note:35Why the registry layer is a structural risk — and why LARUS is the only proven business-continuity guarantor.
Why direct IPv4 ownership can expose operators to more registry-layer risk than leasing from the right provider.
Read the full noteThe world's only court-recognized continuity provider in the history of the RIR system.
Ordinary holders typically stand behind thin, standard-form RIR contracts while carrying infrastructure-scale downside on their own network. LARUS does not rely on that ordinary posture. The Mauritius Supreme Court order dated 11 June 2025 directed rectification of AFRINIC's register of members to add Cloud Innovation Ltd and recorded the written undertaking to rectify AFRINIC's records within 15 days. That is why LARUS states that it is the world's only court-recognized continuity provider in the history of the RIR system. This is not normal market posture. It is a legally differentiated continuity position.
Read the court judgment
Why this matters
The difference is legal position, not branding.
A customer choosing between direct holding and leasing should ask one question: who is structurally better placed to absorb registry-layer failure? LARUS can answer with first-party control plus court-recognized continuity record.
- First-party pool, not broker chain
- Court record, not abstract safety language
- Stronger continuity case than an ordinary holder with a thin RIR contract
System DesignStructure determines what survives scale.LARUS is designed as a continuity structure, not a transaction layer. That difference becomes visible when networks grow and failure paths matter.
Demand RealitySpikes punish weak supply chains.Burst demand turns hidden fragility into visible downtime.
VisibilitySee the real risk layer clearly.Registry exposure in the wrong entity becomes operational debt.
CraftContinuity needs disciplined execution.Serious infrastructure is built with precision, not slogans.
Asset ValueTreat IPv4 like strategic capital.The wrong structure destroys value in the long tail.
Why direct holding feels safe but isn't
Direct holding can feel safer while exposing you more.
This is the natural comparison after the LARUS continuity case. If you do not lease from a specialist continuity provider, what exactly are you taking onto your own operating company? Across all five RIRs, the answer is materially the same: you keep the weak contract and the catastrophic downside at the same time.
If you self-hold, you usually keep the weak contract and the catastrophic downside at the same time.The details differ, but the structure does not. Across AFRINIC, ARIN, APNIC, RIPE NCC, and LACNIC, public agreements preserve registry-side control while leaving continuity-scale damage on the operator's side.
RIRPublic contract logicWhy that is dangerous for an operator
AFRINIC
Best-effort service, immediate control, nominal downside.Public AFRINIC materials frame the RSA as a best-effort service relationship with liability limited at a trivial level relative to operator-side damage, while termination or expiry can lead to immediate resource revocation and service cessation.
Commercial meaningYou still sit behind a thin contract while the registry stays at the operational control point.
Official agreementARIN
Registry leverage preserved, liability capped at trivial scale.ARIN's RSA ties the holder to policy, permits future changes to become binding, and preserves judicial-order compliance and capped-liability logic.
Commercial meaningYou may pay a large upfront price and still face a public-contractual recovery ceiling measured at USD 100 or a few months of fees.
Official agreementAPNIC
Yearly consent plus delegated-resource revocation path.APNIC's membership framework renews yearly, renewal is deemed acceptance of the then-current agreement, and rights including delegated resources can be revoked, with cease-use obligations following the notice.
Commercial meaningDirect holding does not remove dependence. It formalizes dependence under a renewable service framework.
Official agreementRIPE NCC
Can change without re-signing while your network still carries the risk.The RIPE NCC Standard Service Agreement can be amended by General Meeting resolution without re-signing, incorporates RIPE policies and procedures, and keeps liability tightly bounded relative to the real downside of a live operator.
Commercial meaningYou stay inside a membership-and-procedure framework whose downside is far smaller than the cost of continuity failure on your network.
Official agreementLACNIC
Non-negotiable adhesion text with annual renewal dependence.LACNIC's public RSA is an adhesion agreement, runs for one year, binds the applicant to guidelines as modified over time, and ties non-payment, breach, or termination to resource revocation.
Commercial meaningDirect holding is still direct exposure to a registry-controlled renewal and revocation model.
Official agreementWhat follows from that
Lease the utility. Avoid internalizing the fragility.
If every public RIR framework leaves the operator holding continuity-scale downside, the practical decision is where that risk should live: on your own balance sheet, or upstream with LARUS.
Buying on the secondary market
- Capital structure
- You may pay a large upfront price and still leave your operating company directly exposed to the registry framework.
- Registry exposure
- Your company bears the policy, audit, payment, termination, and revocation machinery itself.
- Organizational burden
- You gain symbolic registry proximity while keeping infrastructure-scale downside on your own balance sheet.
LARUS first-party leasing
- Capital structure
- You buy continuity of use without putting the registry-facing layer inside your operating company.
- Registry exposure
- LARUS carries the upstream registry contract stack while you contract with a specialist continuity provider.
- Operational focus
- First-party pool, reduced intermediary risk, and a court-recognized continuity position create a stronger survivability case than ordinary direct holding.
Continuity is the product
The cost of IPv4 failure is not the invoice.
It is renumbering a live network. Service disruption, routing changes, firewall and ACL rework, allowlist resets, engineering labor, customer churn, and contract exposure are infrastructure-scale costs. That is why this page is built around continuity, not brochure language.
New Continuity Assurance
Capacity is only the starting point.
IPv4 Capacity Only uses the current IPv4 pricing system, calculated by block size and billing term. For production workloads, LARUS Continuity Assurance adds operational controls for RPKI/ROA validity, rDNS, abuse workflow, geolocation handling, support SLA, and renewal certainty.
IPv4 Capacity Only
- Current IPv4 pricing
- Basic unmanaged IPv4 leasing for customers who need low-cost address capacity and can accept best-effort operations.
- Best for
- Price-sensitive, non-critical, or self-managed IPv4 use cases.
Continuity Assurance
- Base price + continuity add-on
- Production adds $0.25/IP/month; Enterprise and Critical add stronger continuity levels for production IPv4 operations.
- Includes
- Routing validity, rDNS, abuse workflow, geolocation priority, support SLA, and renewal controls by plan.
Indicative monthly pricing
Start with the block size you need now.
The legacy homepage presents a block-size pricing path for production IPv4. This static migration keeps the visible choice structure, while current quotes and ordering start through the contact form.
/24Quote required
256 IP addresses
A practical entry block for small production deployments.
Per month, if paid annuallyOrder Now
/23Quote required
512 IP addresses
More room for growing services without jumping to a large range.
Per month, if paid annuallyOrder Now
/22Quote required
1,024 IP addresses
A balanced pool for teams expanding active network capacity.
Per month, if paid annuallyOrder Now
/21Quote required
2,048 IP addresses
Useful for operators that need multiple customer or service groups.
Per month, if paid annuallyOrder Now
/20Quote required
4,096 IP addresses
Designed for broader infrastructure planning and stable allocation.
Per month, if paid annuallyOrder Now
/19Quote required
8,192 IP addresses
A larger production block for networks with sustained demand.
Per month, if paid annuallyOrder Now
/18Quote required
16,384 IP addresses
Suited to high-capacity operations that need routeable continuity.
Per month, if paid annuallyOrder Now
/17Quote required
32,768 IP addresses
For large-scale deployments that require careful onboarding.
Per month, if paid annuallyOrder Now
/16Quote required
65,536 IP addresses
Enterprise-scale IPv4 capacity planned with LARUS coordination.
Per month, if paid annuallyOrder Now
Programs
Two ways to work with LARUS at scale.
The current legacy homepage places Programs after the pricing path and keeps two scale-oriented entries: deploying LARUS-owned IPv4 in partner networks, or selling IPv4 to LARUS.
Network Partner Program
Deploy LARUS-owned IPv4
Work with LARUS to broadcast, route, and support LARUS-owned IPv4 inside your own network, while LARUS owns and governs the resource layer.
- Network operation without resource ownership burden
- Partner-led availability for LARUS-owned IPv4
- Clear separation between routing work and registry-layer ownership
Sell IPv4 to LARUS
Exit the long-tail burden of IPv4 ownership through a sale path with a buyer that understands transfer readiness, registry coordination, and market execution.
- Convert idle IPv4 into liquidity
- Reduce registry and transfer workload
- Move from one-off disposal to a structured buyer path
Trusted by
Trusted By
Real operators, platforms, carriers, and infrastructure providers already using the LARUS model.
Direct answers, without brochure language.
These are the questions your legal, compliance, and board teams should ask before putting RIR-side risk onto the operating company.
Why can leasing from LARUS be safer than holding addresses directly under our own RIR account?
Because direct holding usually puts your operating company directly inside the RIR framework: payment, audit, policy, compliance, termination, and revocation. Leasing from LARUS moves that layer to a specialist first-party lessor while your own company stays focused on production continuity.
Isn't it safer if our own company is the direct holder?
Not necessarily. Direct holding can increase formal exposure without giving proportionate practical protection. The right comparison is not name-in-database versus lease. The right comparison is who carries the RIR-side risk and who can better absorb failure without forcing a live network into renumbering.
Why is the Cloud Innovation judgment relevant to continuity?
Because it moves the position away from the ordinary pattern of a holder standing only behind a thin standard-form registry contract. The court-ordered rectification of AFRINIC's member records and the recorded undertaking to rectify AFRINIC's records materially strengthen the continuity story behind LARUS.
Why does first-party leasing matter more than using a broker?
A broker mainly matches transactions. LARUS leases from its own pool. Fewer layers mean fewer failure points, clearer accountability, and a cleaner path from contract to live use.
Why does LARUS talk about legal structure instead of just price?
Because the large cost in IPv4 failure is rarely the invoice. It is renumbering, service disruption, engineering labor, customer churn, and contract fallout. The commercial question is therefore continuity and survivable legal position, not only monthly rate.