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.

Lease IPv4 Now Sell IPv4 to LARUS

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.

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.

Read Note:35 →

Note:35 • Lu Heng Why 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 note →

Court-recognized continuity provider

The 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.

Modern Ferris wheel structure against blue sky

System Design Structure 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.

Bright multicolor fireworks filling the night sky

Demand Reality Spikes punish weak supply chains. Burst demand turns hidden fragility into visible downtime.

Visibility See the real risk layer clearly. Registry exposure in the wrong entity becomes operational debt.

Craft Continuity needs disciplined execution. Serious infrastructure is built with precision, not slogans.

Asset Value Treat 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.

Direct holding internalizes the registry layer. Your operating company becomes the direct subject of payment, audit, policy, compliance, suspension, termination, and revocation machinery.

Public RIR contracts are not infrastructure insurance. They read like service or membership frameworks. Registry leverage stays upstream while contractual downside can remain tiny relative to network impact.

Your actual loss is renumbering a live network. Service disruption, routing changes, firewall and ACL rework, allowlist resets, engineering labor, customer churn, and contract exposure are the costs that matter.

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. That is why self-holding is often much less safe than it looks.

RIR Public contract logic Why 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 meaning You still sit behind a thin contract while the registry stays at the operational control point.

Official agreement →

ARIN

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 meaning You 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 agreement →

APNIC

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 meaning Direct holding does not remove dependence. It formalizes dependence under a renewable service framework.

Official agreement →

RIPE 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 meaning You stay inside a membership-and-procedure framework whose downside is far smaller than the cost of continuity failure on your network.

Official agreement →

LACNIC

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 meaning Direct holding is still direct exposure to a registry-controlled renewal and revocation model.

Official agreement →

What 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.

Indicative monthly pricing

Start with the block size you need now.

The pricing below reflects the current public structure for annual billing and scales within the same first-party leasing model as your network grows

/24$97.28

256 IP addresses

For small production environments, pilot deployments, and compact entry points that still need serious continuity.

Per month, if paid annually

/23$194.56

512 IP addresses

For operators moving beyond trial scale while keeping the commercial structure simple.

Per month, if paid annually

/22$378.88

1,024 IP addresses

For growing cloud, adtech, and hosting demand that needs room to expand without adding counterparties.

Per month, if paid annually

/21$716.80

2,048 IP addresses

For networks that need more headroom while staying inside one direct leasing structure.

Per month, if paid annually

/20$1,269.76

4,096 IP addresses

For scaled multi-service deployment where continuity matters more than a theoretical ownership story.

Per month, if paid annually

/19$2,457.60

8,192 IP addresses

For established operators that need growth capacity within one accountable model.

Per month, if paid annually

/18$4,915.20

16,384 IP addresses

For regional infrastructure, scaled platforms, and capacity-heavy environments.

Per month, if paid annually

/17$9,830.40

32,768 IP addresses

For larger footprints that need predictable recurring supply rather than secondary-market exposure.

Per month, if paid annually

/16$19,660.80

65,536 IP addresses

For enterprise, cloud, AI, and carrier-grade environments operating at scale.

Per month, if paid annually

Programs

Two ways to work with LARUS at scale.

Use LARUS as a direct source of IPv4 for your network, or exit unused address holdings to a direct end buyer that is structured to carry the ongoing burden.

Network Partner Program

Deploy LARUS-owned IPv4 inside your own network.

LARUS remains the asset owner and continuity authority. Partners focus on deployment, end customers, and recurring revenue without internalizing the ownership problem.

LARUS owns and governs the resource layer
Partners operate, assign, and monetize
Continuity remains centralized upstream

For IPv4 holders

Sell IPv4 to LARUS and exit the long-tail burden.

Unused IPv4 space is not just a balance-sheet line. It carries transfer work, compliance drag, and registry-facing responsibility. LARUS buys directly and assumes the ongoing post-transfer layer.

Direct end buyer rather than broker spread stacking
One accountable transfer workflow
Clear exit from continuing registry-side exposure

Trusted by

Trusted By

Real operators, platforms, carriers, and infrastructure providers already using the LARUS model.

Frequently asked questions

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.

Lease IPv4 directly from LARUS, a first-party IPv4 leasing provider.

On registry risk and business continuity.

The world's only court-recognized continuity provider in the history of the RIR system.

Direct holding can feel safer while exposing you more.

Lease the utility. Avoid internalizing the fragility.

Buying on the secondary market

LARUS first-party leasing

The cost of IPv4 failure is not the invoice.

Start with the block size you need now.

Two ways to work with LARUS at scale.

Deploy LARUS-owned IPv4 inside your own network.

Sell IPv4 to LARUS and exit the long-tail burden.

Trusted By

Direct answers, without brochure language.

Get production IPv4 from a team that understands the risk layer.

Sales

General inquiry

Phone

Office line