byro is a membership administration tool for small and medium sized clubs/NGOs/associations of all kinds, with a focus on the DACH region. While it is still a work in progress, it is already usable and in active use.
Development and Production Setup
Please refer to the development or the production documentation. The recommended way to run byro is byroctl, which installs and updates a Docker based deployment with one command; Docker Compose by hand and a plain installation from PyPI are documented as well.
Features
Planned features
Plugins
byro provides a rich API for plugins. See our developer documentation if you want to write a plugin.
Plugins that work with the current byro release are listed in the plugin catalog that ships with every release; administrators install them with byroctl plugin add <name> (see the plugin documentation). To get a plugin listed, publish a GitHub release and open a pull request against the catalog.
byro-finance-import-bank-files imports file-based bank statements, currently CAMT.053.
byro-mailman (mailing list integration) and byro-gemeinnuetzigkeit (receipts for German non-profits) exist, but are not yet compatible with byro 2026.x.
Community plugins are encouraged to add the byro-plugin tag if they are on GitHub. You can see all byro plugins on GitHub here; byroctl never installs anything from that list on its own. byro-shackspace is an example for how a group can extend or modify byro to fit their purpose, e.g. add custom mechanisms and save additional data.
License
byro is licensed under the GNU Affero General Public License, version 3.0 only (AGPL-3.0-only). Older versions of byro were released under the Apache License 2.0. The documentation in docs/ is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License (CC-BY-SA-4.0). See the LICENSE file for details, including the licensing history and the licenses of bundled third-party components.
Metadata
Release files for byro 2026.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| byro-2026.3.1.tar.gz | 1.3 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| byro-2026.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.8 MB
Release files / byro-2026.3.1.tar.gz
| Download URL | byro-2026.3.1.tar.gz |
|---|---|
| Size | 1.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ad2689f6d68250b0078cdf31dbc9d76397f6fe8399c187fc766c3252a5983ae6
|
|
BLAKE2b-256 checksum How to use checksums |
af418e7c9f6356d613dc166f29c7b46c0f8610e31f68f34c073d0fe434d956e3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 6, 2026.
Transparency logRelease files / byro-2026.3.1-py3-none-any.whl
| Download URL | byro-2026.3.1-py3-none-any.whl |
|---|---|
| Size | 1.5 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b6bb3a16b9ed622a63b70288155d6b3e32de6a3de47aaa6c5b9a20c1a07695c8
|
|
BLAKE2b-256 checksum How to use checksums |
1ff59f219c10ec01b998aa25b71cacc8bc7cd74498f685b5b179a7f865efa759
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 6, 2026.
Transparency log