Tunnelblick: a macOS OpenVPN front end whose documentation is rebuilt at each release
The official Tunnelblick website is at https://tunnelblick.net; the official Tunnelblick GitHub repository is at https://github.com/Tunnelblick
At a glance
- What is it?
- A free, open source graphical interface for OpenVPN on macOS, written in Objective-C and released under GPL version 2. The README is a signpost rather than a manual: it names the website, the security reporting path, the discussion group and the contribution rules, including the one category of pull request the project refuses.
- Who is it for?
- Tunnelblick suits a Mac user who wants a graphical way to run OpenVPN connections rather than a command line, and a contributor who reads the repository as a pointer system: the source is in one directory, vendored code in another, the website lives outside the repository with a snapshot copy refreshed at each release, and the policies for bugs, security and contributions are three separate documents.
- Can I use it commercially?
- Yes, with conditions. GPL-2.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 8 days ago.
- What is it written in?
- Mainly Objective-C, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- Tunnelblick/Tunnelblick3,303 ★ · +21
| Repository | 2026-09-24 | 2026-11-15 |
|---|---|---|
| Tunnelblick/Tunnelblick | 3.3k | 3.3k |
21 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
A macOS front end for OpenVPN, client and server connections both
The definition is one sentence and it is worth reading closely: Tunnelblick is a free, open source graphical user interface for OpenVPN on macOS, and it provides easy control of OpenVPN client and/or server connections. Two details hide in that phrasing. The first is the platform, which is not a preference but the whole scope of the project; there is no Windows or Linux build in this repository, and the question of what to use on those systems is not addressed here at all. The second is the slash in client and/or server, because a pure client front end is a different program from one that can also run a server connection, and the project claims both. The repository's primary language is Objective-C, and the licence is the GNU General Public License version 2, which the README states in the same terms the COPYING file in the root carries.
The website is the documentation, and a snapshot copy is rebuilt per release
Documentation is not in the repository, and the README is explicit about where it lives instead. The official website is tunnelblick.net, and a snapshot copy of that site is published at tunnelblick.github.io. The snapshot is recreated at each release and when significant changes are made to the website, which is the sentence that tells you how to read version numbers: documentation state is tied to releases, not to commits, so a commit between two builds has no documentation snapshot of its own. The repository metadata reflects that arrangement, since it carries no homepage field and instead puts both addresses in the description text. For anyone tracking behaviour across versions, the practical consequence is that the build number in a release name is the join between the binary you are running and the documentation snapshot that matches it.
Three 10.0 betas in September, with the build number inside the tag
The three most recent releases are all betas of the same version, and the naming carries more information than a version number usually does:
- v10.0beta02, named Tunnelblick 10.0beta02 (build 6510), published 4 September 2026 - v10.0beta03, named Tunnelblick 10.0beta03 (build 6520), published 27 September 2026 - v10.0beta04, named Tunnelblick 10.0beta04 (build 6530), published 29 September 2026
The build numbers run ten apart, so a build number increments for work that never becomes a release, and the gap between the second and third of these is two days while the gap before it is over three weeks. There is no stable 10.0 in this history, and no release notes file in the repository root, so what changed between two builds is not recorded in the tree itself. The last commit on the default branch is dated 29 September 2026, the same day as the newest of these releases.
Translations are the one pull request the project will not take
The contribution policy is unusually specific, and it draws a line most projects do not. Pull requests are welcomed for everything except translations and localization, and the project states twice, in both directions, that it does not accept them. Instead of taking the work, it points elsewhere: a page on the website about localizing and translating Tunnelblick explains the route for that work. The rest of the contribution process is delegated in the same fashion, to a contributing guide inside the .github directory, with a code of conduct beside it. So the repository's governance layer is three files in one directory plus a security policy in the root, and the one decision stated inline in the README is the exclusion, which reads as a deliberate protection of the localisation workflow rather than an oversight.
Bugs go to a discussion group first, vulnerabilities go somewhere else entirely
Two reporting paths are given, with a stated preference between them. For bugs and issues the project prefers the Tunnelblick Discussion Group, a Google Group whose address ends in tunnelblick-discuss, and it also accepts GitHub Issues on the official repository. Security vulnerabilities are not part of that flow: they are routed to a document titled Reporting a Tunnelblick Security Vulnerability, kept as SECURITY.md in the repository root. The split matters for anyone filing a report, because a flaw discussed in a public group or a public issue is no longer a private one, and the existence of a separate security document is the signal that the project expects people to notice the difference.
Two source directories, a vendored folder, and a build guide with spaces in its name
The repository root is short enough to read at a glance, and each entry has an obvious job. tunnelblick/ holds the application source, third_party/ holds vendored third-party code, and .github/ holds the community and contribution documents. Two files sit alongside them with the weight you would expect in a GPL project: COPYING, the licence text, and SECURITY.md, the vulnerability reporting path. The entry that tells you most about how the project works is a document named Building Tunnelblick from Source Code.markdown, sitting in the root with spaces in its filename and a .markdown extension rather than the .md used by the README. Its presence says that building from source is a supported route with its own instructions, and that those instructions were authored separately from the main readme rather than folded into it.
No install steps, no requirements, and no configuration file format
What the README does not contain is as informative as what it does. There is no installation section, no minimum macOS version, no statement about which OpenVPN versions are supported, and no description of how configuration files are organised, even though configuration file naming is the sort of detail a VPN front end usually advertises. There is also no feature list and no changelog. The compensating structure is the website and the source build document, so a first-time user is expected to leave the repository for both the binary and the documentation, and an evaluator comparing projects has to read tunnelblick.net to learn what the app does with a connection once it has one. Read that way, the README is a routing table: official site, snapshot site, security path, bug path, contribution path, and the two exclusions.
Editorial conclusion
Tunnelblick suits a Mac user who wants a graphical way to run OpenVPN connections rather than a command line, and a contributor who reads the repository as a pointer system: the source is in one directory, vendored code in another, the website lives outside the repository with a snapshot copy refreshed at each release, and the policies for bugs, security and contributions are three separate documents. It does not suit anyone shopping for a feature list or an install guide on the project's own page, because the README deliberately does not carry either, and the visible release history is a run of 10.0 betas rather than a stable line. Three things to check before you rely on it: where the documentation for your version actually lives, given that the snapshot site is regenerated per release rather than per commit; whether the OpenVPN side of your setup needs the server mode as well as the client, since the project describes controlling both; and which reporting door a problem belongs in, since ordinary bugs and security vulnerabilities go to different places by design.
Frequently asked questions
what is tunnelblick
Tunnelblick is a free, open source graphical user interface for OpenVPN on macOS, released under the GNU General Public License version 2. It is written primarily in Objective-C, and the official website is tunnelblick.net with the source in the Tunnelblick GitHub repository.
What is Tunnelblick used for?
It provides easy control of OpenVPN client and/or server connections from a graphical interface on macOS, which means it is aimed at people who want to manage those connections without working at a command line. The project is scoped to macOS.
how to install tunnelblick on mac
The README carries no installation steps, so the official website at tunnelblick.net is the place to start, with a snapshot copy of that site at tunnelblick.github.io recreated at each release. For building from source rather than installing a binary, the repository root holds a document titled Building Tunnelblick from Source Code.
how to use tunnelblick
The README does not include usage instructions; it points to the official website for documentation and describes the app only as providing easy control of OpenVPN client and/or server connections. The documentation snapshot at tunnelblick.github.io is regenerated at each release, so it matches a build rather than a commit.
Is Tunnelblick trustworthy?
It is released under GPL version 2 with the licence text in the repository root, its source is published in the official GitHub repository, security vulnerabilities have their own reporting document kept as SECURITY.md, and ordinary bugs go to a discussion group or to GitHub Issues. The project also states that it does not accept pull requests for translations or localization.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/tunnelblick-tunnelblick)Star history chart for your README
[](https://hysenlabs.com/projects/tunnelblick-tunnelblick)Was this useful?