This is slightly different, as far as I can tell. You're essentially paying for a layer that does the work of setting up Algo[1] on a [digitalocean, EC2, azure,

This is slightly different, as far as I can tell. You're essentially paying for a layer that does the work of setting up Algo[1] on a [digitalocean, EC2, azure, GCE] instance for you before sending you the certificates. You pay them, then they pay the VPS instance, an 'admin fee' of sorts and a donation to Algo's ongoing development. The FAQ-cited difficulty of 'setting up your own VPN' basically relies on the end user not realising or feeling comfortable that they could provision Algo directly. You're paying for that, essentially. One thing I'm curious about (and I could be missing the details) is how you guarantee privacy of the certificates generated by Algo being sent to me, the consumer? Do I just have to trust you that you don't keep a copy? [1]: https://github.com/trailofbits/algo https://github.com/trailofbits/algo