Bring a local service online without exposing the machine.
TunnelForge links a future desktop executable to this server, then gives users a managed public route for demos, webhooks, previews, and private tools.
browser -> TunnelForge -> desktop executable -> local appWhat is inside
The service is planned around secure routing, operational visibility, and admin control from one dashboard.
Create stable public entry points for local services without opening router ports.
Observe requests, responses, timings, and replay traffic during debugging.
Use a protected dashboard for service status, routing policy, analytics, and audit history.
The future executable will keep a controlled connection from the user's device to TunnelForge.
The website and auth screens remember the user's preferred theme.
Registration is prepared now while actual tunnel usage stays marked as coming soon.
How normal users will use it
This is the customer journey once an administrator publishes the executable client.
Register, choose a username, and sign in to the install page.
Open Install Agent, pick the package for your operating system, and verify the displayed SHA-256.
Run tf init-config, then set your local service port, host, label, and TunnelForge server URL.
Run tf login or use an endpoint key generated by an administrator.
Run tf up --config ~/.tunnelforge/client.json to pair the endpoint and publish your public URL.