When we design a remote-access deployment, the first constraint we apply is the most mundane one: it has to work from whatever network the user happens to be on. Guest Wi-Fi, a hotel, a mobile hotspot, a client site with a strict firewall — all of them reliably allow outbound HTTPS on port 443, and comparatively little else.
That is why every Edgemere gateway presents itself as an ordinary encrypted web service. There is nothing exotic for a network to object to, nothing that needs a special firewall exception, and nothing for a user to configure. The connection looks and behaves like any other secure website, which is exactly what makes it dependable.
The trade-off
Running on standard ports means we invest more in how each gateway is operated — certificates, monitoring, capacity — because the protocol itself is deliberately unremarkable. We think that is the right place to spend the effort. The people relying on the connection should never have to think about ports or protocols at all.