outline-server VS fly-tailscale-exit

The same thing, waiting for solution. The one way is to watch for updates on github.

Doesn't seem to exist natively according to https://github.com/Jigsaw-Code/outline-server/issues/214 and https://github.com/Jigsaw-Code/outline-server/issues/257

It's private in that it's your own VM you're running the VPN on. No one else has access to it. Whether you trust Google or not, it's all open source[1].

[1] https://github.com/Jigsaw-Code/outline-server

Unless https://github.com/Jigsaw-Code/outline-server/issues/161 has changed, each access key only uses one core at the most.

https://github.com/Jigsaw-Code/outline-server/pull/415 but see https://github.com/Jigsaw-Code/outline-server/issues/44#issuecomment-451459926

Here is the CHANGELOG: https://github.com/Jigsaw-Code/outline-server/blob/master/src/shadowbox/CHANGELOG.md

We're currently adding a changelog to the server! It's in review now.

For connecting to a homelab, pick whichever of your servers can handle an another service and set up either Wireguard (ligthweight, common choice) or Outline (if you intend to connect often from a network that tends to block VPN traffic otherwise).

I used to do Algo with a VM on GCP. But fly.io and tailscale has made this really simple. Try this if you are looking for an easier alternative https://github.com/patte/fly-tailscale-exit

Yes, fly.io allows you to expose a UDP port. See the [fly.toml](https://github.com/patte/fly-tailscale-exit/blob/main/fly.to...) in the repo. To make, the tailscale port [is pinned](https://github.com/patte/fly-tailscale-exit/blob/main/start....) to the exposed port (41641 in that case).

I just tested it again and the connections are made directly (after the first 2,3 go via DERP):