Before I'd use something like this, I'd like to see a privacy policy and at least a simplified topology of the networking, where and if encryption is terminated, what information is sent or stored, etc.

Looks cool, though! Are you running a standardized kernel for the images, or are the kernel builds board specific and thus different versions?

I can understand your concern if there is no privacy policy nor documentation and whole thing seems like a black box. To be honest, the post on CNX-SOFTWARE was published a bit faster than we expected so we are catching a running train now :) Anyway, PP, ToS and documentation is the priority now. We would like to be as transparent as possible, most likely the whole solution will be open source in future. To your question about kernels: to simplify it for now, we are just modifying standard Armbian and Raspbian images available on their websites. Complete build process on our side is something we are considering to implement.

> openconnect

Any special reason? The main advantage that I would expect over ex. Wireguard is maybe better (pre-existing) authentication integration but I'd be curious about your reasons.

The reason was easy integration with PostgreSQL over PAM. I will check if the same could be achieved with Wireguard. Technically, already deployed devices can switch to other VPN tunnel, so there is nothing preventing us from the change.