Ways to reach your ESP32 from outside, side by side.
Each approach solves one problem well. This page tells you which, so you can pick the right one, even if it is not ours.
| Port forwarding + DDNS | Tunnel to the board's server | VPN | Widget dashboard | Your own backend | ThingFace | |
|---|---|---|---|---|---|---|
| No port opened on the router | no | yes | yes | yes | yes | yes |
| Works behind CGNAT and 4G | no | yes | depends | yes | yes | yes |
| Nothing to install for whoever opens it | yes | yes | no | app | depends | yes |
| Individual logins, with roles | you build it | no | per network | yes | you build it | yes |
| The interface is yours | yes | yes | yes | no | yes | yes |
| No server for you to maintain | yes | depends | depends | yes | no | yes |
| Opens with the board off | no | no | no | yes | depends | yes, with the last state |
Port forwarding + DDNS
Works when you have a public IP, control the router, and accept the board being exposed to the internet. Behind CGNAT or 4G, it does not work.
Tunnel to the board's server
Works when only you open it and the board's own page is enough. It brings no individual logins or roles.
VPN
If you already run a VPN on every device and nobody else needs access, a VPN is enough. To give a client access, it gives them the entire network.
Widget dashboard
Works when a ready-made dashboard will do, without an interface of your own. The screen belongs to the service, not to you.
Your own backend
Solves everything, if you have a team to maintain the server, security, and app for years.
ThingFace
For those who want their own interface for the device, opened with individual logins, without maintaining a server. Not a fit if you need history, charts, or alerts computed in the cloud.
