> ## Documentation Index
> Fetch the complete documentation index at: https://docs.devin.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Devin VPN configuration

> Configure a non-MFA VPN for Devin workspaces with blueprints, file attachments, Secrets, and connection knowledge.

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.

<Note>
  For enterprise systems on private networks, see the [deployment overview](/enterprise/deployment/overview) and [Dedicated SaaS private networking](/enterprise/deployment/dedicated_saas_private_networking).
</Note>

## 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](/onboard-devin/environment/blueprint-reference#file-attachments). Devin writes attachments to `~/.files/` and exposes each path through a `$FILE_*` variable.
3. Store VPN credentials in [Secrets](/product-guides/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](/onboard-devin/environment/templates). For blueprint structure and build behavior, see [environment blueprints](/onboard-devin/environment/blueprints).

<Warning>
  Client VPNs that require interactive MFA sign-in are not supported by this setup.
</Warning>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.