Stable public node
Receive a ClearNAT node, allocated public port and DNS name for the service you choose to expose.
Public edge for private infrastructure
Private services.
Public reachability.
ClearNAT gives services behind NAT a stable public endpoint through a controlled edge, while your application stays on your own machine.
IPv4 RAW TCP presentation•Fail-closed controller design
route / raw-tcpEDGE READY
ClearNAT edgelis1.clearnat.net:61344
Your serviceclient :8080
Built for controlled exposure
One public route. Your infrastructure stays yours.
ClearNAT separates public reachability from workload hosting. The edge owns exposure; your client machine owns the application.
Small client footprint
Download the agent configuration for your route, keep the app on your own host, and bind only the intended client port.
Fail-closed lifecycle
Exposure is modeled as durable state. Suspension and recovery prioritize removing reachability before reporting a safe terminal state.
Three steps
From private port to public endpoint.
Create your account
Sign in to the client portal and view the routes assigned to your ClearNAT account.
Download agent config
Install the ClearNAT agent on the private host and use the route-specific configuration from your dashboard.
Serve the client port
Your public ClearNAT node forwards approved traffic through the overlay to the configured client port.
Ready to present ClearNAT?
Open the client portal and walk through the complete customer experience.