Skip to main content
Devin can connect to a VPN from inside its workspace, so sessions can reach internal services such as package registries, databases, and internal Git hosts.
For enterprise systems on private networks, see the deployment overview and Dedicated SaaS private networking.

​
Configure a client VPN in a blueprint

For a non-MFA OpenVPN or WireGuard connection, configure the client in a blueprint:
  1. Install the VPN client in initialize.
  2. Upload the VPN profile as a blueprint file attachment. Devin writes attachments to ~/.files/ and exposes each path through a $FILE_* variable.
  3. Store VPN credentials in Secrets, preferably using a service account rather than a personal account.
  4. Add a knowledge entry with the command Devin should use to connect or check the tunnel.
For complete OpenVPN and WireGuard blueprint examples, see the VPN connection templates. For blueprint structure and build behavior, see environment blueprints.
Client VPNs that require interactive MFA sign-in are not supported by this setup.