Why we built SuperDMZ

SuperDMZ started in late 2024 from a boring internal pain: our team needed to reach an IP camera, a PostgreSQL server and a Windows RDP across three different networks, all behind NAT, none with a public IP. The existing tools all suffered from one or more of:

• Server too far away — every packet had to travel to Virginia or Frankfurt and back, adding 200 ms to everything.
• Random URLs — every reconnect produced a new endpoint, useless for services that need a stable DNS.
• Open-ended pricing — US$ 20/month plans that turned into US$ 200 once traffic grew.
• English-only or bot support — hours spent on what a human resolves in 5 minutes.

We decided to build our own with 4 hard principles:

1. A node in Brazil. You cannot keep latency low for Brazilian customers without a São Paulo presence.
2. Stable URL. You pick the subdomain. It's yours until you cancel.
3. Predictable price. Known traffic ceiling. If you go over, we tell you before we charge.
4. Support in Portuguese, no bot. A real technical person answers.

Today we run nodes in São Paulo, Atlanta, Frankfurt and Tokyo, have 200+ active customers, and the Windows client remains our main focus — that's where our user base's pain is concentrated.

Upcoming posts will go deeper into the technical side: how the tunnel actually works, how to expose RDP and IP cameras, comparisons with traditional VPN, and why we shipped a complete Linux and macOS client instead of just a wrapper.