[dsiddharth]

I'm not too familiar with Steam Networking, but at a glance here are some differences:

- Steam Networking seems mostly for peer-to-peer messaging, so it's closer to a STUN server (used by WebRTC for sending UDP datagrams). It's excellent for sending messages over high-quality links, but if you want to run server side logic, it doesn't seem like Steam Networking will help much.

- On the flip side Hathora is a server-authoritative framework, which can run arbitrary game code on our infrastructure. This is closer to a cloud provider. The difference between us and just using AWS or DO is that we're providing the "Steam Networking"-like edge network out of the box and tailoring our use case to the needs of game devs.

- Lastly, we can actually spin up compute infra at the edge if enough of your users are originating from a location far from the rest of your servers. Let's say your game starts to go popular in Asia today, our routing layer is smart enough to launch a server in Singapore instead of connecting users to far away game servers.