Skip to content
ThingFace

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 + DDNSTunnel to the board's serverVPNWidget dashboardYour own backendThingFace
No port opened on the routernoyesyesyesyesyes
Works behind CGNAT and 4Gnoyesdependsyesyesyes
Nothing to install for whoever opens ityesyesnoappdependsyes
Individual logins, with rolesyou build itnoper networkyesyou build ityes
The interface is yoursyesyesyesnoyesyes
No server for you to maintainyesdependsdependsyesnoyes
Opens with the board offnononoyesdependsyes, 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.