OpenVPN just launched Access Server Link, and the detail worth paying attention to isn’t the setup speed the company is marketing. It’s what the tool deliberately doesn’t do. Access Server Link deploys OpenVPN’s Access Server software directly into a customer’s own AWS, Azure or Google Cloud environment, but according to the company, the actual VPN traffic never routes through OpenVPN’s own infrastructure at any point.
That distinction matters more than it might sound. Plenty of vendor-hosted VPN services simplify deployment by taking on more of the underlying infrastructure themselves, which usually means customer traffic passes through systems the vendor controls. OpenVPN’s pitch here runs the opposite direction. Administrators pick a hostname, a cloud provider, a region and an admin password, and a prepared cloud template handles the rest, including DNS and SSL certificate configuration.
Once it’s running, OpenVPN says connections go straight to the customer’s own Access Server instance, with configuration data and logs staying there too. The portal handles orchestration and gives administrators a management interface instead of forcing them into SSH for routine tasks, but OpenVPN maintains it never carries the tunnel traffic itself.
Companies evaluating that setup shouldn’t just take the traffic-separation claim at face value, though. It’s worth checking exactly what data the management portal itself handles, how access to that portal gets secured, and which operational responsibilities still sit with the customer’s own team rather than OpenVPN’s.
The launch also pairs with OpenVPN’s application broker, which grants access to specific applications based on user and device attributes rather than handing out broad network access once someone connects. OpenVPN frames this as limiting how far a user can move laterally after authenticating. That’s a reasonable design goal, but whether lateral movement actually becomes impossible in practice depends heavily on how an organization configures the broker and secures everything around it, not just on the feature existing.
For teams running infrastructure across multiple clouds, the real appeal here is consistency: a more standardized way to stand up VPN servers without shifting that infrastructure into a fully vendor-hosted service. What Access Server Link doesn’t remove is the underlying work. Someone still has to select cloud capacity, set access policies, monitor the instance and plan for what happens if it fails. Access Server Link is available now through Access Server Hub.
