Client-initiated tunnel
The client creates the outbound connection to the control plane, avoiding the need to expose an inbound port to start.
SéCURITé
Designed to avoid unnecessary network exposure.
OpenPort.fr establishes an outbound tunnel from the client. Publish a URL when needed or limit access to a private alias and invitations.
Principes
Controls based on how you actually expose a service.
The right access level depends on the tunnel: a public URL for a callback or demo, a private alias and invitation for a team service.
QUIC transport
HTTP, TCP, and UDP tunnels use the same QUIC transport layer in the OpenPort.fr workflow.
Owner / consumer
An owner can define private access and control who joins the tunnel using an invitation.
Operational visibility
Clients, tunnels, sessions, traffic, and events remain visible in the control interfaces.
Accès privé
Private is not a hidden URL: it is explicit access.
Use an owner tunnel, invitation token, and OpenPort Connect to authorize a consumer to join a service without publishing that service on the Internet.
owner→invitation token→consumer