Claimed Tunnel Domains
Claim a tunnel domain when an integration needs the same public URL across development sessions. Claims are managed through LPM CLI and can use any currently enabled base returned by LPM.dev Registry.
URL Types
| Account | URL when no domain is supplied | Claimed domains |
|---|---|---|
| Free | Random 10-character *.lpm.fyi URL for each session | 0 |
| Pro | <username>.lpm.fyi | 3 |
| Organization | A personal URL based on the connecting member's plan | 10 per organization |
The automatic Pro URL does not consume one of the three personal claims. To use an Organization tunnel account, select one of its claimed domains when starting the tunnel.
List the Base Domains
lpm tunnel domains
The command reads the currently enabled bases from LPM.dev Registry. The current bases are:
lpm.fyi, used for Free random URLs, Pro account URLs, and paid claims.lpm.llc, used for paid claims.
Claim a Personal Domain
Personal claims require a Pro account:
lpm tunnel claim acme-api.lpm.llc
Claims are first-come, first-served within each base domain. acme-api.lpm.fyi and acme-api.lpm.llc are separate names.
The chosen subdomain must:
- Use lowercase letters, digits, and hyphens only.
- Be between 3 and 32 characters.
- Start and end with a letter or digit.
Claim an Organization Domain
Organization owners and admins can claim a domain for the organization:
lpm tunnel claim acme-api.lpm.llc --org acme
An Organization account can hold up to ten claims. The claims belong to the organization, not to the member who created them.
Start the Tunnel
Any current organization member can use an Organization domain:
lpm tunnel 3000 acme-api.lpm.llc
Do not pass --org when starting the tunnel. LPM.dev Registry resolves the claim from the domain, verifies current organization membership, and applies that organization's concurrency, request, and billing account.
The claim is not tied to a local port. A later session can point the same domain to a different port:
lpm tunnel 4500 acme-api.lpm.llc
List Claims
lpm tunnel list
lpm tunnel list --org acme
lpm tunnel list --json
Any organization member can list its domains. Output includes each domain and when it was claimed.
You can also review and release personal claims from the tunnels dashboard. Organization claims are under Dashboard > Organization > Tunnels. New claims are created through LPM CLI.
Release a Domain
lpm tunnel unclaim acme-api.lpm.llc
lpm tunnel unclaim acme-api.lpm.llc --org acme
lpm tunnel release is an alias for unclaim. Only an organization owner or admin can release an Organization domain.
Released names immediately return to the shared pool and can be claimed by another account.
Membership and Billing
Organization ownership is checked whenever a member starts a tunnel. A removed member can no longer bind an Organization domain, so offboarding does not require changing the domain.
If organization billing is interrupted, its claims remain available during the grace period. LPM.dev Registry blocks their use while billing is lapsed and releases them after the grace period ends.
Current Domain Boundary
The hosted service accepts only the base domains returned by lpm tunnel domains. A newly provisioned multi-label base works without a new LPM CLI or
Worker application-code allowlist, but it must already have LPM.dev Registry
DNS, TLS, and Worker routing. Bring-your-own DNS names are not currently
supported.
For exact claim, list, and release output, see the LPM CLI tunnel reference.
Continue
- Start a Tunnel — Bind a local port to a claimed domain.
- Request Inspector — Inspect and replay requests received through the domain.