vopono
0.10.22 open-sourceThe section your link pointed to isn't on vopono's page any more, so we've brought you to the top.
vopono runs applications through VPNVPNA virtual private network, an encrypted tunnel between devices or networks. It carries traffic across another network as though the endpoints had a private connection. tunnels via temporary network namespaces, letting you route select apps through different VPNsVPNsA virtual private network, an encrypted tunnel between devices or networks. It carries traffic across another network as though the endpoints had a private connection. simultaneously.
vopono daemon vopono --allow-host-access --port-forwarding 8080:8080 # Inside namespace: echo $VOPONO_FORWARDED_PORT # outputs '8080' vopono --custom-port-forwarding protonvpn up vopono --port-forwarding-callback /usr/local/bin/my_callback.sh up vopono --create-netns-only vopono connect --protonvpn-port-forwarding vopono --allow-host-access vopono --custom-netns-name my-vpn-ns echo "Container IP: $VOPONO_NS_IP" && curl -s http://$VOPONO_HOST_IP/api/status vopono --open-hosts 127.0.0.53 vopono --hosts 'internal.local 192.168.1.10' vopono -A /usr/bin/your_askpass exec ifconfig vopono run --keep-alive transmission-daemon vopono run --config /path/to/custom.conf vopono servers protonvpn vopono sync --provider=mullvad --protocol=shadowsocks
Summary
vopono is an open-source command-line tool that runs individual applications through VPN tunnels using temporary network namespaces, so a handful of programs can each use a different VPN while the rest of the machine stays on the normal connection. It ships killswitches for both WireGuardWireGuardA modern VPN protocol and Linux kernel module, maintained as an open-source project, that establishes encrypted tunnels using minimal code and fast cryptography, giving cyber tools a lightweight, high-performance transport layer. and OpenVPN, and it targets people managing their own multi-VPN setups rather than teams provisioning access for others, supporting providers like Mullvad, ProtonVPN, NordVPN and AirVPN directly, plus custom OpenVPN, WireGuard, OpenConnect and SSH-based configs. It sits in the secure-access space alongside general namespace-based VPN routing setups rather than any named competitor. First committed in 2020, it has 30 contributors and a release 26 days ago, showing active maintenance.
vopono runs applications through VPN tunnels via temporary network namespaces, letting you route select apps through different VPNs simultaneously.
How vopono helps
Which of my applications are actually going out through which VPN right now?
lists each running namespace with its assigned provider and exit connection, so a browser on one VPN and a chat client on another can be confirmed at a glance instead of assumed
Can my other traffic keep going out my normal connection while a couple of programs use a different exit point?
isolates each wrapped application in its own network namespace, so only the processes launched inside it are rerouted while everything else on the machine stays on the default route
Will my traffic actually stop if one of these tunnels drops?
holds the killswitch on that namespace so its applications lose connectivity entirely rather than falling back to the normal route when a WireGuard or OpenVPN link goes down
Which provider and region is a given running application actually exiting through?
records the connection each namespace was launched with, so a browser session can be traced back to the exact provider and location it was assigned instead of guessed from memory
Did a network drop leave one of my tunnels stuck instead of reconnecting?
sets a keepalive on WireGuard connections by default so a lapsed link is more likely to recover on its own rather than sit silently disconnected
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for vopono, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail vopono puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
23 entries
No entries match these filters.
- August 20262
- July 20261
- May 20261
- April 20261
- September 20251
- December 20241
- March 20242
- January 20241
- November 20231
- July 20221
- May 20221
- April 20221
- December 20212
- May 20211
- April 20212
- October 20202
- August 20202
Project health
Issue, contributor and maintainer activity in jamesmcm/vopono, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 8 +4 vs prior 12 months
- Maintainers 2 +1 joined · −1 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 83% of issues opened, last 12 months
- Median time to close 2.1 days first maintainer reply 21 hours
- Open backlog 84 of 248 issues ever filed
- Issues opened / month 3 · 2 communitymaintainers
- Open backlog 84
- Contributors / month 3
- Commits / month 6
- Stars 1,339
- bugs 4%
- features 8%
- other 88%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.