Access templates for HTTP and TCP services
Private access to local apps and internal services without VPN or inbound ports
DevProxy lets developers and small teams reach selected HTTP and TCP services from anywhere: local apps, webhooks, databases, AI tools, admin panels, media servers, devices, SSH, and RDP. Host and connector clients authenticate with workspace-scoped tokens, while data can go directly from computer to computer when networks allow.
Selected service access
devproxy client host tcp --transport auto --name service --local 127.0.0.1:5432Security model for private developer access
Use DevProxy when a service must be reachable by the right person, but closed to the public internet.
What can you access with DevProxy?
Start from ready templates for common developer and home lab jobs instead of memorizing ports and command flags.
Local apps and webhooks
Expose Vite, Next.js, ASP.NET, Django, Flask, webhook receivers, and API callbacks from a local machine.
Databases and TCP services
Reach Postgres, MySQL, Redis, MongoDB, SSH, RDP, and custom TCP services through scoped private access.
AI tools and workstations
Share Ollama, Jupyter, ComfyUI, Stable Diffusion WebUI, and local model dashboards without opening your GPU box.
Home lab and admin panels
Access Home Assistant, NAS panels, Grafana, Prometheus, media servers, router UIs, and device dashboards when needed.
Built for the access workflows teams actually need
Share localhost, test webhooks, give teammates private service access, and reach TCP services without deploying a VPN or opening firewall rules.
Developers
Share localhost, test webhooks, and demo work-in-progress without deploying.
Small teams
Give teammates access through workspace tokens instead of sharing SSH or VPN credentials.
Private TCP access
Reach Windows RDP, SSH, databases, admin tools, game servers, and custom TCP services without exposing service ports to the internet.
Managed workspaces
Start with a hosted workspace; dedicated or private deployments can be handled as an advanced plan when needed.
Security
Private TCP access without public service ports
In private TCP mode the relay accepts only authenticated WebSocket control traffic. Connectors are validated by workspace, tunnel name and grant, then DevProxy relays bytes without inspecting RDP, SSH, databases, media servers, or your custom application protocol.
- Scoped API tokens are hashed and workspace-bound.
- Private TCP connector access requires an explicit grant or workspace admin scope.
- When networks allow, data goes directly from computer to computer. If not, DevProxy keeps access available through a secure backup path.
- Audit events track account, token and tunnel lifecycle actions.
Manage tunnels, tokens, grants, and audit in one workspace
The cabinet gives teams one place to see active tunnels, create scoped CLI tokens, grant connector access, and review security events.
Start free. Upgrade when tunnels become team infrastructure.
Begin with private tunnels for one workspace, then upgrade when you need custom workspace names, public TCP approval, higher limits, and team controls.
Free
$0Solo workspace for localhost, webhooks, and private TCP access experiments.
Start freePro
$12 / workspace / monthTeam tunnel sharing, custom workspace slug, connector grants, and higher private relay limits.
Request Pro accessBusiness
$49 / workspace / monthAudit, member roles, public TCP approval, and higher relay capacity for production-like access workflows.
Talk to usQuestions
Is DevProxy only for RDP?
No. RDP is one template. DevProxy can expose selected HTTP apps and private TCP services such as SSH, databases, admin panels, media servers, AI tools, device UIs, and custom ports.
Does TCP traffic go through HTTP?
No. DevProxy carries it as a plain byte stream. When possible, data goes directly from computer to computer; if not, DevProxy uses a secure backup path.
Can the server start my local tunnel?
No. The local DevProxy client owns local ports and must be running or reconnecting.
Can every user deploy the full stack on their own VPS?
Not as the default product flow. The main path is a managed workspace; dedicated or private deployments are an advanced option for teams that need infrastructure isolation.