Skip to content
Sign in
HTTPS URLs for HTTP plus public TCP/UDP ports

Ship localhost without losing the plot.

Proxlane is a developer tunnel service with a small Go CLI, HTTPS-backed HTTP tunnels, public TCP/UDP endpoints, custom domains, background profiles, traffic inspection, and relay-side access controls.

Sign inGetting started
HTTPS

TLS edge for HTTP tunnels

HTTP

callbacks and web apps

TCP

random or fixed ports

UDP

Bedrock and datagrams

proxlane
relay ready

$

DoctorHTTPSTCPUDP

Domains

custom

Background

service

Safety

guard

Support

bundle

Publish your first local service

Install Proxlane, connect your account, then publish a service that is already running locally.

  1. 1

    Install

    Choose the Windows Launcher or the Linux/Windows CLI.

  2. 2

    Connect your account

    Use the Launcher sign-in or the browser-based CLI authorization.

  3. 3

    Check and publish

    Check your local service, start the tunnel, and share its public address.

CLI example for a local HTTP service on port 3000

proxlane login
proxlane doctor http 3000
proxlane http 3000
Complete installation guide

Built-in workflow

The parts developers reach for after the first tunnel.

Start from dashboard

Custom domains with DNS checks

Plus and Pro users can point a CNAME at Proxlane, verify DNS in the dashboard, and run HTTPS tunnels on their own hostname.

Background tunnels

Profiles and OS services keep tunnels running after the terminal closes, with status, logs, and dashboard visibility.

Traffic Inspector

HTTP, TCP, and UDP activity can be filtered, searched, inspected, and copied as replay-ready curl commands.

Endpoint Protection

The relay checks Basic Auth, Bearer tokens, and saved IP and country access lists before traffic reaches your local service.

Safety guard

Suspicious paths, oversized bodies, rate spikes, access policy denials, and custom domain DNS failures are blocked and surfaced in Safety.

Support bundle

A redacted diagnostic bundle captures version, OS, profiles, service status, doctor output, and recent logs for support.

Recently shipped

More than a tunnel command now.

The product now covers the pieces that matter after a tunnel is online: stable hostnames, long-running agents, visibility, and safer public edges.

Bring your own hostname

Reserve a custom HTTP domain, follow the CNAME guide, verify DNS, then start with proxlane http --domain.

Keep tunnels alive

Use background profiles and the local service runner on Linux or Windows when a tunnel should survive a closed terminal.

Protect the edge

Basic Auth, Bearer tokens, and IP and country access lists are enforced at the relay before requests reach localhost.

Know what happened

Traffic logs, Safety events, usage accounting, DNS health, and support diagnostics now share one SQLite-backed control plane.

Common jobs

Useful when local work needs a real URL.

Receive HTTPS callbacks

Point a service callback at a Proxlane HTTPS URL while your app runs on localhost.

Read webhook guide

Share previews

Send a protected URL to a teammate or client without deploying the branch.

Read localhost guide

Debug traffic

Open the metadata inspector when status, bytes, remote address, or endpoint routing look wrong.

Read webhook guide

Test TCP and UDP services

Expose local SSH, database, Java or Bedrock game-server ports when HTTP is not enough.

Browse guides

Keep endpoints stable

Reserve a Plus or Pro hostname, custom domain, or fixed TCP/UDP port once, then reuse it from the CLI for demos and callbacks.

Read localhost guide

Keep tunnels running

Save a background profile when a tunnel needs to keep working after the terminal closes.

Read localhost guide

Pricing

Start free, upgrade only when limits grow.

Free is enough to try the agent. Plus and Pro add active tunnel capacity, reserved HTTP hostnames or custom domains, fixed TCP/UDP ports, and monthly transfer for regular development work.

Free

Â¥0/month

Active tunnels
1
Connected devices
3
Protocols
HTTP / TCP
Monthly transfer
5 GB
Log retention
1 day
Reserved HTTP hosts / custom domains
No reservations; random HTTP host
Fixed TCP ports
0
Fixed UDP ports
0
UDP
Not included
More limits and protection
Automation tokens
1
Basic authentication
Included
Bearer token protection
Not included
IP access rules
Not included
Country access rules
Not included

Plus

Â¥390/month

Active tunnels
3
Connected devices
10
Protocols
HTTP / TCP / UDP
Monthly transfer
50 GB
Log retention
7 days
Reserved HTTP hosts / custom domains
1
Fixed TCP ports
1
Fixed UDP ports
1
UDP
Included
More limits and protection
Automation tokens
3
Basic authentication
Included
Bearer token protection
Included
IP access rules
Included
Country access rules
Included

Pro

Â¥980/month

Active tunnels
10
Connected devices
30
Protocols
HTTP / TCP / UDP
Monthly transfer
200 GB
Log retention
14 days
Reserved HTTP hosts / custom domains
5
Fixed TCP ports
5
Fixed UDP ports
5
UDP
Included
More limits and protection
Automation tokens
10
Basic authentication
Included
Bearer token protection
Included
IP access rules
Included
Country access rules
Included

Traffic flow

Outbound agent connections publish a local endpoint.

Caddy terminates HTTPS for HTTP traffic, the relay matches active endpoints, applies optional HTTP protection, records metadata, then forwards traffic through agent-opened data connections.

Outbound agent

The CLI keeps a control session to the relay and opens data connections outward for traffic.

Scoped identity

Tokens, subdomains, tunnels, and logs stay tied to the signed-in user.

Protected edge

Authentication and IP and country access lists are checked by the relay before traffic reaches localhost.

Fig. 1 - traffic through Proxlane
  1. A public request reaches the edge and Relay.
  2. The Relay finds the active host, checks Basic/Bearer protection and records status, transfer and duration.
  3. The Agent makes an outbound connection and forwards the request to localhost:3000.
  4. The development app stays local; the dashboard shows the connection log.
Detailed diagram

Scroll horizontally to read the full diagram. Arrow keys also work when this area is focused.

public internetedge + relaylocal machineGET /previewhttps://demo.proxlane.commatch active hostenforce basic / bearerlog status / bytes / timeagent dials outPagentoutbounddev applocalhost:3000local only200GET /preview64ms

Network patterns

The paths Proxlane actually runs today.

These diagrams match the current relay, CLI, dashboard, and SQLite-backed policy implementation: outbound agent sessions, relay-side protection, reserved endpoint ownership checks, traffic inspection, and monthly transfer enforcement.

HTTP / HTTPS

HTTPS or custom domain to localhost

HTTP traffic enters through the HTTPS edge. Verified custom domains and Proxlane hosts route to the active tunnel through the agent connection.

  1. A browser sends an HTTP request to the HTTPS edge.
  2. Caddy terminates TLS; the Relay routes, protects and records the request.
  3. An outbound Agent connection carries the request to the local app; ConnectionLog records status, transfer and duration.
Detailed diagram

Scroll horizontally to read the full diagram. Arrow keys also work when this area is focused.

public internetTLS edgeGo relayagentlocalhostGET /appbrowser requestCaddyTLS terminatesGo relayroute, protect, logagentoutbound dataapp127.0.0.1:3000ConnectionLogstatus, bytes, duration
Caddy TLScustom domainsagent data connection

TCP / UDP

Public ports for non-HTTP services

TCP and UDP endpoints listen on public ports. Random ports skip reserved ranges, while fixed ports require the signed-in owner.

  1. TCP and UDP clients connect through a public port and Relay to the Agent and local service.
  2. TCP streams count bytes; UDP datagrams track flows and require Plus or Pro.
  3. Automatic ports are random and skip reserved fixed ports. Fixed ports belong to their reserving user.
Detailed diagram

Scroll horizontally to read the full diagram. Arrow keys also work when this area is focused.

clientspublic portrelayagentlocal serviceTCP clientSSH, DB, Java:10007fixed or randomstreambytes countedagentdata connlocal :22TCP serviceUDP clientBedrock, datagrams:22001Plus / Prodatagramflow trackedagentUDP datalocal :19132UDP serviceautomatic ports start randomlyreserved fixed ports are skipped
random portsfixed portsUDP Plus / Pro

Ownership

Reserved endpoint and DNS enforcement

Reserved hostnames, custom domains, and fixed ports live in Endpoint rows. The relay checks owner, plan, and DNS before accepting the tunnel.

  1. The dashboard saves a reserved HTTP host, custom domain or TCP/UDP port in Endpoint.
  2. The CLI requests it with --subdomain, --domain or --remote-port.
  3. The Relay starts the tunnel only for the matching owner and valid plan/DNS; unreserved or other-user endpoints return an error.
Detailed diagram

Scroll horizontally to read the full diagram. Arrow keys also work when this area is focused.

DashboardSQLite / PrismaRelay policyReserve endpointHTTP host / TCP / UDPEndpoint rowuserId + protocolCLI can reusesame ownerproxlane command--subdomain / --domain /--remote-portRelay checksame-user policyTunnel startsowner matchedError returnednot reserved / other user
Endpoint tableCNAME verifysame-user policy

Observability

Inspector, usage, and safety events

The relay records connection metadata, sampled request details, transfer usage, and blocked events for Logs, Billing, and Safety.

  1. The Relay meters incoming and outgoing HTTP/TCP/UDP traffic.
  2. ConnectionLog supplies request details to Logs; MonthlyUsage supplies transfer usage to Billing.
  3. Request bodies are sampled and sensitive headers are masked before display.
Detailed diagram

Scroll horizontally to read the full diagram. Arrow keys also work when this area is focused.

trafficrelay meterSQLitedashboardHTTP/TCP/UDPbytes flowmeterin + out bytesConnectionLogheaders + samplesLogsinspect detailsMonthlyUsagequota ledgerBilling5 / 50 / 200 GBrequest bodies are sampledsensitive headers are redacted before display
ConnectionLogMonthlyUsageSafety events

Practical guides for developers

Install Proxlane on Windows or Linux and publish your first local app

Install the Proxlane CLI, sign in with browser approval, check localhost, and create a public HTTPS URL on Windows or Linux.

Publish localhost with a custom domain and a stable HTTPS URL

Reserve a custom HTTP domain on Plus or Pro, prove ownership with TXT, configure CNAME or apex A records, and publish localhost with HTTPS.

Keep a localhost tunnel running after the terminal closes

Save a Proxlane background profile, check its Windows or Linux service, set a sharing deadline, and stop the tunnel when you are finished.

Protect a shared localhost URL with authentication and access rules

Use Free Basic Auth or Plus/Pro Bearer, IP and country policies to protect development tunnels, and verify that denied requests do not reach localhost.

Publish and verify localhost from Claude Code with Proxlane MCP

Authenticate Proxlane privately, register its local MCP server, publish a time-limited development tunnel, verify the public URL, and stop it from your AI agent.

An ngrok alternative for localhost, TCP, and UDP development

Compare Proxlane and ngrok for Windows/Linux development, stable URLs, endpoint limits and UDP, then migrate a local HTTP or TCP tunnel step by step.

Ready when your local app is

Open the dashboard, install the agent, publish a port.

Sign in