What it is
A secure private "tunnel" over the internet: it connects your devices and servers as if they were on one local network, even when they are physically in different cities.
How we apply it
We build private VPN networks for secure access to work services and for bypassing blocks โ with no public exposure of your infrastructure to the internet.
Where a VPN helps a business
- A team has lost access to Canva, Notion, Jira and AI tools, and public workarounds break the security policy.
- Staff need to reach internal servers and services without exposing them to the internet.
- You sell VPN access by subscription and want sales, key issuing and renewals to run without manual work.
- Staff and customers are not technical: they need one button, not protocol settings.
Types
- WireGuard: a fast private network for a team, linking staff with the office and servers. A good fit when nobody is deliberately cutting the connection.
- OpenVPN: an older, proven protocol we use for compatibility with old equipment and policies.
- Xray / VLESS: for when VPNs get blocked. Traffic is disguised as ordinary HTTPS (Reality, WebSocket+TLS, XHTTP). Our VPN services and the corporate gateway run on it.
How we use it
- Corporate gateway. For an IT company we deployed a gateway on its Linux servers: Xray encrypts and routes, nginx sits at the entrance, access depends on the employee's role, and connecting takes one click. Case.
- A Russia โ Europe route. An entry node in Russia, a persistent frp tunnel to an exit abroad and a standalone node in the Netherlands with VLESS Reality: VPN route.
- Selling subscriptions. The Tech Poly VPN bot takes payment, issues keys in the Marzban panel, reminds about renewal and delivers a config through a backup VKontakte bot when Telegram is unavailable.
- Our own client. OshaVPN for Android, Windows 10/11 and Windows 7: one button, the entry point chosen by a race, local sites going direct.
- Setup guides. Five pages, one per platform, open from the bot inside Telegram so a beginner does not have to contact support: guides.
We set up team VPNs and routes under Infrastructure, and client apps under Apps.
Common problems
- Connections cut at the border. Measurements on 20 August 2026 showed 35โ60% of TCP handshakes to the exit server lost while ping had no loss. One persistent connection instead of a new one per client solved it.
- A domain gets blocked. Domains are split by role: traffic, subscriptions, admin. If the traffic domain is blocked, the client refreshes its subscription through the second one and gets a new address. The limit: if every domain points to one IP, a block by address takes them all down.
- Hosting complaints about torrents. On the Netherlands node, torrents and AI-service domains exit through Cloudflare WARP.
- Users cannot cope with setup. Every config step turns into a support question. Hence our own client with one button, or at least step-by-step guides.
When you do not need it
If all your work tools open directly and internal systems are reachable only from the office, a VPN is just another point of failure. And a business does not need a VPN on everything "for privacy": HTTPS on your own services is enough.