Tunnels
LPM.dev Registry tunnels give a local development server a public HTTPS URL. LPM CLI opens the connection, forwards requests to your local port, and starts a local browser inspector for incoming traffic.
lpm login
lpm dev --tunnelUse a standalone tunnel when your server is already running:
lpm tunnel 3000Both workflows require an active LPM.dev Registry login.
Choose a Workflow
| Workflow | Command |
|---|---|
| Start the development server and its tunnel together | lpm dev --tunnel |
Tunnel the only active lpm dev endpoint | lpm tunnel |
| Expose an explicit local port | lpm tunnel 3000 |
| Use a claimed domain | lpm tunnel 3000 acme-api.lpm.llc |
Bare lpm tunnel does not assume port 3000. It uses the only active lpm dev endpoint and asks for an explicit port if it finds none or more than one.
See Getting Started for inspector controls, session names, webhook auto-acknowledgement, and tunnel authentication.
Tunnel URLs
- Free accounts receive a random 10-character subdomain on
lpm.fyifor each session. - Pro accounts that do not specify a domain use
<username>.lpm.fyi. - Pro accounts can claim up to three stable domains.
- Organization accounts can claim up to ten stable domains shared by their members.
Current claimed-domain bases are lpm.fyi and lpm.llc. See Claimed Tunnel Domains for naming rules, organization roles, and claim management.
Plan Limits
| Capability | Free | Pro | Organization |
|---|---|---|---|
| Concurrent tunnels | 1 | 3 | 10 |
| Included requests | 20,000 per UTC month | 100,000 per billing period | 100,000 per billed seat and billing period |
| Account request rate | 4,000/min | 20,000/min | 20,000/min per billed seat |
| Maximum request body | 10 MB | 100 MB | 100 MB |
| Session duration | 1 hour | No plan limit | No plan limit |
| Claimed domains | 0 | 3 | 10 |
| Tunnel authentication | No | Yes | Yes |
| Browser inspector | Yes | Yes | Yes |
The included allowance is shared by all tunnels owned by the account. An Organization domain uses the organization account rather than the connecting member's personal allowance.
Pro and Organization overage is enabled by default at $1 per 100,000 additional requests. It can be disabled from the tunnels dashboard to stop at the included limit.
When to Use a Tunnel
- Webhook development. Send Stripe, GitHub, Slack, or other callbacks to a local handler and inspect what arrived.
- Preview sharing. Give a teammate a temporary URL without deploying the application.
- Mobile testing. Reach a local development server from a phone on another network.
- Remote integrations. Connect an external service to an HTTP endpoint running on your machine.
Request Inspector
LPM CLI starts a local inspector alongside the tunnel unless you pass --no-inspect. It shows live requests and responses, searches capture history, exports cURL commands, and replays requests against the local server.
See Request Inspector for the capture database, replay behavior, and current terminal-command limitation.
LPM CLI Reference
These pages describe the hosted tunnel service, account limits, and claimed domains. For the complete command, flag, configuration, and relay reference, use:
