An open-source web application for managing organizations and communities with complex group hierarchies, members, events, and communication.
Hitobito is an open-source web application for managing organizations and communities with complex group hierarchies. It provides tools for handling members, events, courses, mailings, and communication within a structured, role-based permission system. The platform is designed to be extended via plugins to match specific organizational needs.
Organizations, associations, clubs, and non-profits with hierarchical structures, such as youth groups, political parties, sports federations, and community organizations that need to manage members, events, and communications.
Developers choose Hitobito for its flexible plugin architecture and powerful group hierarchy model, which allows customizing group and role types to fit complex organizational structures without rebuilding core functionality from scratch.
A web application to manage complex group hierarchies with members, events and a lot more.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
The meta-model allows defining custom group types in a tree with layer-based permissions, as shown in the Group::Layer example, enabling precise organizational mapping without rebuilding core logic.
Built on the Wagons framework, Hitobito supports custom extensions and group type definitions, which is necessary since no default types are provided, ensuring adaptability to specific needs.
Permissions are tied to role types with fine-grained control, such as :layer_full or :group_read, allowing precise user ability management across groups, as described in the architecture section.
Includes integrated tools for managing members, events, courses, mailings, and communication, making it an all-in-one platform for structured organizations, as per the key features list.
Hitobito requires creating a Wagons plugin to define group and role types before use, as stated in the architecture, adding significant upfront development effort and making it unusable without coding.
The primary user guide and architecture documentation are in German, as linked in the README, which may hinder adoption and troubleshooting for non-German speaking teams.
Tied to the Ruby on Rails ecosystem and Wagons framework, necessitating specific technical expertise and limiting flexibility for teams using other tech stacks or preferring lighter solutions.