Skip to main content
LARUS
Discuss your IPv4 needs
Explore

IPv4 Infrastructure Services

IPv4 infrastructure, operated end to end.

From court-recognized RIR shareholder rights and first-party address supply to network delivery, fully automated allocation, API control and Continuity, LARUS keeps every operating decision inside one accountable company.

For ISPs, hosting platforms, data centres, cloud infrastructure and network operators that cannot leave production IPv4 to a chain of intermediaries.

Check IPv4 Availability
One operating lineRIR to production
  1. RIR foundationCourt-recognized shareholder rights in the RIR system
  2. First-party supplyAddress resources supplied directly by LARUS
  3. Network deliveryDeployment and routing into production networks
  4. Automation and APIAllocation and control through one workflow
  5. Address operationsRPKI, rDNS, geolocation, abuse and support
  6. Continuity by planOperating and renewal treatment matched to the workload

One company remains accountable across every stage.

Why the operating model matters

Every extra handoff becomes infrastructure you cannot control.

A broker chain can deliver an address while leaving resource control, routing, operations and renewal in different companies. LARUS keeps those decisions connected.

Operating eventFragmented supplier chainLARUS operating line
Supply and renewalThe resource holder, broker and service operator can make separate sale, lease and renewal decisions.First-party supply and the operating counterparty stay connected inside LARUS.
Activation and changeRouting, registry and customer teams can sit in different companies, making ownership and escalation unclear.Network delivery, registry coordination and customer controls follow one operating path.
Production operationsAbuse, geolocation, rDNS or route reputation work can cross multiple support queues.The LARUS operations line owns the same controls after activation.
Supplier exitIf an upstream party exits, the network using the addresses can still carry migration and renumbering risk.Continuity treatment is defined with the operator responsible for the address and production service.

Your team should not have to arbitrate contracts between the parties that keep one address block usable.

What LARUS operates

One responsibility line from requirement to production.

Each stage answers a real infrastructure question before it becomes a support problem.

Requirement and capacityWhat must the network support?
Confirm quantity, region or RIR, workload, term and the cost of renumbering before capacity is committed.
Address and registryWho controls the resource relationship?
Coordinate first-party supply, registry records and delivery responsibility around one deployment.
Network deliveryHow does the block reach production?
Define the network path, BGP delivery and RPKI or ROA controls required by the workload.
Automation and allocationHow does the team control change?
Configure and assign through the LARUS console or API instead of moving requests between vendors.
Production operationsWho remains responsible after launch?
Carry rDNS, geolocation, abuse, support and route-related changes through the same operating team.
Continuity treatmentWhat happens at renewal or disruption?
Keep operating and renewal treatment attached to the selected plan. Critical alone includes Guaranteed Renewal.

Institutional foundation

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

The published Supreme Court of Mauritius order is the inspectable record behind this position. The evidence page owns the dated legal detail; this infrastructure service carries that foundation into one operating relationship.

Inspect the court record

Continuity is an infrastructure choice

Pay for protection in proportion to the cost of disruption.

Use Capacity Only for non-critical needs. Start live workloads with Production. Move to Enterprise when response and renewal priority matter, and choose Critical when renumbering is unacceptable.

  1. For non-critical capacity

    IPv4 Capacity Only

    Operations
    Best-effort capacity for price-sensitive or self-managed use
    Renewal
    Subject to availability

  2. Recommended for live workloads

    Continuity Production

    Operations
    Production operations for routing, naming, reputation and response
    Renewal
    90-day renewal review

  3. For business-critical networks

    Continuity Enterprise

    Operations
    Priority operations where service continuity has commercial impact
    Renewal
    Renewal priority and right of first refusal

  4. When renumbering is unacceptable

    Continuity Critical

    Only tier with Guaranteed Renewal
    Operations
    Highest-priority continuity operations for keeping the same IPv4 block
    Renewal
    Guaranteed Renewal

Guaranteed Renewal applies only to Continuity Critical. Capacity Only, Production and Enterprise retain their stated renewal treatment.

Compare Continuity Assurance

What happens next

Move from availability to operated capacity without rebuilding the supply chain.

The commercial handoff starts with the requirement and keeps the delivery and Continuity decision inside the same operating path.

  1. Check the requirement

    Start with capacity, region, term, workload and the impact of renumbering.

  2. Confirm delivery

    Align the address resource, network path and production responsibility.

  3. Configure control

    Prepare allocation, RPKI, rDNS, geolocation and the console or API workflow.

  4. Operate under one plan

    Carry support, abuse handling, change and renewal through the selected Continuity level.

Make IPv4 one less dependency to worry about.

Check capacity first. LARUS will connect the address requirement, delivery path and Continuity choice to one operating relationship.

Check IPv4 Availability