How it works: looking inside the unique AdGuard VPN protocol

> ... We use the HTTP/2 transport protocol ...

> ... AdGuard VPN protocol operates with data and not with packets. This means that AdGuard VPN establishes a separate "tunnel" for each connection, each HTTP/2 stream corresponds to one connection.

so this is a proxy. Did you ever use SOCKS5 proxy provided by some universities, or "-D" / "DynamicForward" option in ssh? This uses the same approach.

I suspect the innovative part is that they could get it working with mobile devices. I am not vary familiar with Android/iOS VPN hooks, but if the AdAguard only gets TCP packets, it'll need local TCP stack in userspace to terminate. OTOH, quick googling shows there are some SOCKS proxy apps for mobile devices, so maybe that's solved as well?

My eyebrows raised at “proprietary vpn protocol”, but I’m too much of a normie to understand if it’s really just a novel combination of standard things.