FEATURES
Concrete building blocks to expose, control, and observe your services.
HTTP, TCP, and UDP share the same QUIC control plane. Choose a public URL, private access, or an inspection view depending on the need.
Produit
A tunnel is useful only when the complete path is controlled.
Choose the right mechanism: publishing, private access, routing, inspection, or local operation.
Public tunnels
Publish a local service without opening your router.
A public URL or endpoint for HTTP, TCP, or UDP.
openport-fr tunnel http --local-port 3000See how it works →Private tunnelsShare a service without publishing it on the Internet.
Owner, consumer, internal alias, and invitation token.
openport-fr tunnel tcp --local-port 22 --private ssh-prodSee how it works →HTTP InspectorUnderstand a request before replaying it.
HTTP capture, request/response details, filters, curl, and Replay.
POST /stripe/webhook → 200 · 88 msSee how it works →HTTP routingRoute multiple services through one HTTP tunnel.
Path or hostname rules for a multi-service tunnel.
/web01=127.0.0.1:80See how it works →Desktop applicationCreate, operate, and observe tunnels from the workstation.
Local dashboard, runtime actions, logs, stats, and profiles.
/tunnel start 1See how it works →OpenPort ConnectJoin a private tunnel without managing the whole platform.
A focused Windows client for the private_consumer role.
pit1_••••••••••••••••See how it works →HTTP authenticationPut the right control in front of an HTTP tunnel.
Off, CIDR, password, Google OIDC, or Microsoft OIDC.
auth_http_mode = google_oidcSee how it works →OPENPORT.FR
Create your first QUIC tunnel.
Publish a local service or open private access in seconds, without opening an inbound port.