Although their setup is kinda wacky (you provide their GUI app SSH credentials, it connects and installs packages, set up firewall rules, and spawns some containers), I walked through everything on a throwaway VPS and everything was above board (as of the most recent release about a month ago).
A private vpn is only good for punching through firewalls
netsharc•1mo ago
I exported the config (they offer this to share the connection with others), the export is a Base64 of a JSON, inside which are several strings which are JSON but as escaped strings (so { "someKey": "{\"hello\":\"world\"}" }), and sometimes the nesting happened 2-3 layers deep! I had to write an encoder/decoder for my own setup.
Then I noticed in the JSON was also the private key that I used to setup the server! Wow, great work!
parliament32•1mo ago
> hidden and not visible to me
Everything it runs is blasted out to the terminal you launched the app from.
> in the JSON was also the private key
Yes, because you asked for this. There are two types of shared connections, connection-only (VPN user) and "server management". If you shared for management, of course they shipped the SSH credentials.. how else would the receiver manage your server? Their services don't expose any kind of control plane, all management is through SSH.
Agreed on all your other points though. I strongly disliked the "wizard" interface, and it clobbered a good amount of the baseline settings I deploy to servers. I would much prefer it if they had a more manual mode, but I didn't find anything other than the wizard in their docs.