> For the complete documentation index, see [llms.txt](https://docs.engma.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.engma.io/built-on-enigma/epn.md).
# EPN
*Comparison of a traditional VPN architecture and an EPN deployment built on Enigma.*
The Enigma Private Network (EPN) is an application that provides secure, private connectivity for distributed systems. EPN uses Enigma’s identity layer and dynamic network layer to establish encrypted sessions and manage access without relying on fixed network endpoints. This enables teams and services to connect in environments where traditional static VPNs or centralized gateways are vulnerable. EPN illustrates how scoped identity and coordination can be used to enforce access permissions.\
\
**EPN demonstrates:**
* Identity-scoped access without shared network visibility
* Dynamic routing without long-lived tunnels
* Access enforcement independent of network topology
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.engma.io/built-on-enigma/epn.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.