Certified Locations

For customers

Certified Locations

Learn how a venue may become a Certified Location.

No customer-ready Certified Location listings are currently published. The formats below describe the planned certification program for venues that want to support dedicated public network identity.

Use them when the work session needs documented public network identity for independent allowlist or access review, APIs, Codex workflows, secure meetings, or project team delivery.

Ask about future availabilityApply as a venue

Business use cases

Use a certified venue when the network identity matters

Each scenario starts with a customer problem: a public endpoint needs documentation for review by a client, supplier, API provider, security team, or private system. The location provides the managed network path; LARUS provides the Identity Unit and evidence. Each third party independently decides recognition, allowlisting, and access; LARUS does not guarantee acceptance.

  • AI Developer Room

    Who needs it
    A hotel room, serviced office, or reserved workspace used for AI-assisted development sessions.
    Workflow
    The developer opens a laptop, reconnects to the same Codex thread, reaches Git, package registries, model gateways, APIs, and internal tools from a dedicated Identity Address instead of shared venue NAT.
    Value
    Security teams can independently review the dedicated room or workspace address without treating every venue guest as the same public endpoint; allowlisting is not guaranteed.

  • Client-Allowlisted Access

    Who needs it
    Consultants, advisors, agency teams, and vendor staff who need access to a client system while working from a managed venue.
    Workflow
    The location provides a documented Identity Address and Identity Passport for the customer endpoint. The client independently decides whether to allowlist that address.
    Value
    The client sees a stable public network identity tied to the work session instead of rotating broadband or shared Wi-Fi egress.

  • Dedicated Identity Meeting Room

    Who needs it
    Board meetings, diligence sessions, legal reviews, finance calls, and private client meetings.
    Workflow
    The room network is assigned a dedicated Identity Address for meeting devices, conferencing systems, secure portals, or temporary workstations.
    Value
    Participants can submit documented network identity to counterparties, banks, suppliers, and enterprise security teams for independent review; recognition is not guaranteed.

  • Project Team Network Pack

    Who needs it
    Short-term project teams working from a coworking site, serviced office, hotel floor, or client war room.
    Workflow
    The team receives a documented set of Identity Addresses for developer laptops, API test tools, gateways, runners, and controlled access points.
    Value
    The project can start with documented network identity for allowlist review and keep evidence consistent through the engagement; each third party decides access independently.

  • Executive Access

    Who needs it
    Executives, family offices, board members, and private clients working from lounges, suites, clubs, or managed offices.
    Workflow
    The venue provides a dedicated public network identity that can be submitted for privileged-access, banking-portal, private-infrastructure, or executive remote-access review.
    Value
    The access point can be documented without exposing the customer through a shared venue address; each system operator independently decides recognition and access.

Codex workflow

Separate the development session from the network identity

A developer can arrive at a certified room or workspace, open the laptop, continue the same Codex thread, pull from Git, call APIs, reach package registries, and use a model gateway from a documented Identity Address.

Codex maintains the development session and project context. LARUS One provides the endpoint's network identity.

What Codex does

Codex keeps the coding thread, repository context, task history, edits, tests, and development workflow state.

What LARUS One does

LARUS One anchors the public network identity, rDNS, Identity Passport, Allowlist Pack, and continuity record for the endpoint.

Location options

Illustrative location formats

These are illustrative service formats, not currently available venue listings. Every venue requires certification and delivery approval.

Hotel suite or long-stay room
AI Developer Room
One customer endpoint or room network uses one dedicated Identity Address.
Illustrative only — certification and delivery approval required
Managed meeting room
Dedicated Identity Meeting Room
Meeting devices and approved workstations use documented Identity Addresses.
Illustrative only — certification and delivery approval required
Coworking project room
Project Team Network Pack
Team endpoints, API gateways, and runners receive named Identity Addresses.
Illustrative only — certification and delivery approval required

Next step

Start with delivery availability, then choose the location

Customers should confirm whether a Certified Partner or approved provider can deliver the Identity Unit at the target venue before treating the location as ready for allowlist review. A provider or location change requires a new delivery assessment, and uninterrupted continuity is not guaranteed.

Ask about future availabilityApply as a Certified Location