- C++ 54.2%
- CMake 18.4%
- PHP 9.8%
- Shell 8.1%
- CSS 5.1%
- Other 4.4%
| actions | ||
| cmake | ||
| data | ||
| debian | ||
| desktop | ||
| fedora_rpm | ||
| locale | ||
| mageia | ||
| openmandriva | ||
| opensuse_leap16 | ||
| opensuse_rpm | ||
| pkgbuild | ||
| src | ||
| thirdparty | ||
| webui | ||
| CHANGELOG.md | ||
| CMakeLists.txt | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| GOVERNANCE.md | ||
| LICENSE | ||
| PROJECT_MANIFEST.md | ||
| README.md | ||
| ROADMAP.md | ||
| sanitize_po_keep_last.py | ||
| SECURITY.md | ||
| TRADEMARK.md | ||
BastionGuard
BastionGuard is a Linux security platform designed for users who want deterministic behavior, explicit policies, and visible decisions — not opaque “trust us” protection.
Release Status
BastionGuard 2.0 was officially released on July 15, 2026.
Version 2.0 is the current stable production-ready release. It builds on the original 1.0 release of February 27, 2026 and follows extensive development, production use, and testing.
Build and Installation
Detailed instructions for compiling and installing BastionGuard are available in the official documentation.
Please refer to:
https://bastionguard.eu/documentation/
Section: BastionGuard - Technical Documentation – Application Install
Supported Distributions
When compiling BastionGuard from source, you need to use the CMake file specific to your Linux distribution, as each configuration has been prepared specifically for the corresponding distro.
BastionGuard officially supports the following Linux distributions:
- Debian
- Ubuntu
- openSUSE
- Fedora
- Arch Linux
- OpenMandriva Lx
- Mageia 10
In general, BastionGuard is compatible with all modern Linux distributions that use systemd as their init system.
Other distributions may work but are not officially tested.
Development and Release Process
BastionGuard is used in production and is therefore developed with a stability-first approach.
Development changes are tested extensively before being published. Commits are pushed to the public repository only when the corresponding functionality is complete, operational, and considered stable enough for release.
The main branch is not used to publish intentionally broken, incomplete, or untested development snapshots. Repository activity may therefore be less frequent than in projects that expose every intermediate development step.
This release model prioritizes reliability, deterministic behavior, and production safety.
License
This project is licensed under the GNU GPLv3. See the LICENSE file for details.
Trademark
"BastionGuard" and related branding are protected. See TRADEMARK.md for details.
Issue Tracking
This project does not use the built-in Forgejo issue tracker.
Please report bugs and feature requests at:
https://bastionguard.eu/issues