Batch configuration management for OpenVPN - test, inject, and deploy with ease.
Tired of deploying for dozens of configs one by one, or adding login credentials to each file by hand?
This tool automates both tasks, making bulk OpenVPN deployment simple and reliable.
Important
Project temporarily paused - planned to resume on 2027-01-10 (at the earliest)
Due to academic commitment, development is paused until early 2027.
During the pause:
- v2.5 and later releases are postponed until maintenance resumes.
- Bug reports and feature requests are still welcome, but responses may be delayed.
- Security issues will be reviewed as soon as possible, but non-critical issues may wait until maintenance resumes.
- The monthly release cadence is suspended, no RC or stable releases will be published on schedule during this period.
Resumption plan:
-
Maintenance is planned to resume on 2027-01-10 (at the earliest).
-
The
v2.5cycle will then follow the regular cadence:-
2027-01-24 : RC1
-
2027-02-01 : RC2 (if needed)
-
2027-02-04 : stable release
Dates above are subject to the weekend/holiday shift rule described in the cadence section.
All dates are in CST (UTC+8).
-
Thank you for your understanding.
Contributions, bug reports, and feature requests are all welcome.
If you're new to open source, look for issues tagged good first issue
Note: The cadence below is currently suspended and is planned to resume on 2027-01-10 (at the earliest).
This project follows a monthly release cycle with a defined feature freeze and release candidate phase:
| Phase | Date | Description |
|---|---|---|
| RC1 | 24th of each month | First release candidate: starts community testing and feedback collection |
| RC2 (Optional) | 1st of the following month | Second release candidate with new features frozen: only bug fixes and security fixes are accepted |
| Stable Release | 4th of the following month | Official stable release, containing accumulated features, fixes, and maintenance updates |
All release dates are specified in CST (UTC+8).
Each minor version is maintained for 4 months after its stable release, only receiving bug and security fixes during that period.
I aim to keep this schedule, but it is a best-effort commitment, not a legal guarantee.
If the release date falls on a weekend or holiday, it may be shifted by 1–2 days.
Critical bug fixes and security issues will always take priority over the regular cadence.
This tool is designed for educational and administrative purposes only. It is intended to help users manage OpenVPN configurations they are legally authorized to use. We guarantee that we will not collect, transmit or upload any information from the configuration files to any remote server.
Users are solely responsible for ensuring their use of this software and any associated VPN services complies with all applicable local laws and regulations. The author assumes no liability for any misuse of this tool.
For details on third-party components and their licenses, please refer to the NOTICE file.