Skip to main content
Public network identity for supplier access and B2B workflows.

Supplier Access

Public network identity for supplier access and B2B workflows

Supplier systems, vendor portals, logistics workflows, and operational counterparties may request public-address documentation. LARUS One can provide named Identity Addresses and the evidence they ask for.

USD 6,998 per Identity Unit-yearChoose your local delivery partner after purchase.

Value

Give supplier workflows one public identity

Use Identity Addresses for supplier portals, procurement systems, logistics tools, vendor APIs, finance operations, and controlled operational access points.

Identity Address examples

Assign public network identity to the systems that need recognition

  • Supplier portal access
  • Procurement gateway
  • Vendor API access
  • Logistics system endpoint
  • Finance supplier gateway
  • Operations access review

The LARUS advantage

One identity, with LARUS behind you

01

Scale by active Location, not by address count

People, devices, rooms, network segments, and workflows do not change the subscription count. Count the Locations used at the same time.

02

LARUS and your provider, working together

LARUS anchors identity. The selected provider delivers the local network.

03

Put your network identity in your partners' hands

Share your Identity Passport and Allowlist Pack with business partners to introduce your network identity and support access requests.

04

Built to work with your security setup

Bring your LARUS network identity into the firewalls, SASE and access policies your team already manages.

From use case to paid pilot

Your first paid pilot

  1. 01

    Start one paid pilot

    Create an account and sign in to purchase one annual Identity Unit online.

  2. 02

    Add the first Location

    After purchase, add the office, property or other place where you will use the identity. Location profiles are free; one Unit serves one active Location at a time.

  3. 03

    Arrange delivery and activate

    Choose an available Certified Delivery Partner or submit your existing BYOIP-capable provider for review. LARUS coordinates delivery and activation with the selected provider.

  4. 04

    Share your identity. Grow your reach

    Share your Identity Passport and Allowlist Pack, put your first workflow to work, then add one Unit for each additional Location you use at the same time.

How LARUS One helps

LARUS anchors identity. The selected provider delivers the local network

01

Allowlist Pack

Package Identity Addresses, rDNS names, and operational purpose for supplier onboarding.

02

Delivery change assessment

Confirm any provider or location change with LARUS before you switch.

03

Business deployment

Deploy to offices, enterprise sites, data centers, API edges, and private networks.

FAQ

Answers to common questions

Can suppliers use these addresses for allowlists?

Customers can share named Identity Addresses and Allowlist Pack documentation with suppliers.

Can supplier access be separated from ordinary office traffic?

Yes. Identity Addresses can be assigned to specific gateways, applications, or access workflows.

One paid pilot

Bring LARUS One to your first Location

Choose the connection that matters most. We coordinate delivery and activation, then grow with you as you add Locations.