Proxlane
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, fixed port reservations, metadata logs, and Basic/Bearer protection for HTTP traffic.

Support
HTTPS

TLS edge for HTTP tunnels

HTTP

callbacks and web apps

TCP

random or fixed ports

UDP

Bedrock and datagrams

proxlane
relay ready

$

DoctorHTTPSTCPUDP

Doctor

checks

Subdomain

reserved

Logs

inspect

Protection

edge

Built-in workflow

The parts developers reach for after the first tunnel.

Start from dashboard

Doctor-grade CLI checks

Config, token, relay, DNS, and local service checks point at the broken link before you start guessing.

Reserved endpoints

Plus and Pro users can reserve HTTP hostnames plus fixed TCP/UDP ports, then the relay enforces ownership.

Traffic Inspector

HTTP, TCP, and UDP logs split cleanly, with timing, bytes, tunnel, and endpoint metadata.

Endpoint Protection

Basic Auth and Bearer tokens are checked at the relay before HTTP requests reach your local service.

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

Basic Auth and Bearer tokens are checked by the relay before a request 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 URL to localhost

HTTP traffic enters through the HTTPS edge, then the relay chooses the active tunnel and sends the request through the agent connection.

public internetTLS edgeGo relayagentlocalhostGET /appbrowser requestCaddyTLS terminatesGo relayroute, protect, logagentoutbound dataapp127.0.0.1:3000ConnectionLogstatus, bytes, duration
Caddy TLSGo relayagent 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 enforcement

Reserved hostnames and fixed ports live in Endpoint rows. The relay rejects unreserved or other-user endpoints before the tunnel starts.

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

Observability

Traffic Inspector and usage ledger

The relay records connection metadata and transfer usage as traffic closes, giving Logs and Billing the same source of truth.

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

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.

Connect CLI

Share previews

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

Manage endpoints

Debug traffic

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

Open logs

Test TCP and UDP services

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

Run tunnel

Keep endpoints stable

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

Reserve endpoint

Find broken setup

Run doctor before support: token, relay, DNS, and local reachability are checked together.

View commands

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, fixed TCP/UDP ports, and monthly transfer for regular development work.

Free

0円/月

1 tunnel

5GB transfer

Plus

390円/月

3 tunnels

1 host + TCP/UDP ports

Pro

980円/月

10 tunnels

5 hosts + TCP/UDP ports

Stack

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

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

Sign in with GitHub