Where the configs come from

The only source for this version is the official VPN Gate CSV for clients. The VPN Gate homepage invites developers to use the CSV for their own client app: “you can use CSV List to make your own VPN Gate client app”. This supports public-client integration; it is not a claim of an unrestricted commercial licence.

Current snapshot

Retrieved 2026-09-30T11:07:05.454495+00:00. CSV records: 100. Catalogue: 81 original files after selection and deduplication. Records excluded for source restrictions: 19. The catalogue is not the total server count shown on the VPN Gate website; it uses only this API snapshot.

Updates occur on a new build. This is not continuous monitoring. Files may become outdated immediately after retrieval; the snapshot time does not confirm availability. Every published file is marked “Connection not tested”.

Selection rules

Academic Use Only markers and other detected usage restrictions are excluded before deduplication. A restriction on one record applies to all records with the same IP. Remaining files pass a limited syntax parser. Duplicate profiles and address/port/transport combinations are not repeated.

Downloads are the original files, byte for byte, from the OpenVPN_ConfigData_Base64 field of the official CSV, without test modifications. Embedded client keys are part of the client profiles intentionally published by VPN Gate, not private keys collected from GitHub. Metadata and SHA-256 hashes for every file are available in the JSON catalogue.

Terms and trust

There is no advertising or paid access. The absence of a restrictive marker does not establish commercial rights; monetisation requires a separate terms review. We do not represent VPN Gate or claim that its operators endorse this catalogue. Follow the VPN Gate rules and applicable law.

VPN Gate describes log retention in its project policy. Individual volunteers may have different terms. We do not confirm a no-logs policy or guarantee privacy on public servers.

Visit counter

If the counter is enabled, pages send a random UUID from sessionStorage and the page path to this same website. The counter does not store IP addresses or User-Agent strings; the hosting provider processes network requests under its own policy. The server hashes the identifier separately for each UTC day. On subsequent visits, session receipts are cleaned up while retaining the current and two preceding UTC dates; deletion exactly after 72 hours is not guaranteed. DNT disables sending; ?qa=1 excludes the current session from counting. The .ovpn downloads contain no scripts. Sessions are counted by day and are not unique people: a new day or browser session may produce a new count. Bots and spoofed events may affect the figures. Pages use no third-party analytics.