Hacker News Reader

> - internal network only with edge nodes (i.e tail scale out the box, + some edge nodes)

Can you help me understand that?

> - option to deploy on multiple servers to scale with super simple non k8s approach.

I'm working on that, allowing you to manage remote nodes from a single /dev/push instance.

> Can you help me understand that?

Like 10 nodes behind tailscale/wireguard in a private network, with only 2 nodes where you have a port open on 80/443, those are exposed to the public network. The rest of the nodes are all private like db, redis, etc etc.

Still figuring it out. Routing the traffic is the annoying bit.

Guess that is why there isn't an easy go to solution yet. But it's well needed.

Check out https://github.com/psviderski/uncloud I'm building. Multi-machine deployments and a private WireGuard network spanning locations (even behind a NAT) are its core capabilities.

Reply on news.ycombinator.com