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.

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

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 allowlists before traffic reaches your local service.

Safety guard

Suspicious paths, oversized bodies, rate spikes, allowlist misses, 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 allowlists 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.

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 allowlists are checked by the relay before traffic reaches localhost.

Fig. 1 - traffic through Proxlane

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.

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.

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.

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.

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

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

1 tunnel

random HTTP host

Plus

¥390/month

3 tunnels

1 HTTP host/domain + fixed TCP/UDP

Pro

¥980/month

10 tunnels

5 HTTP hosts/domains + fixed TCP/UDP

Stack

Go CLI/RelayNext.jsAuth.jsSQLitePrismaStripeCaddy edge
Ready when your local app is

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

Sign in