We\u2019re excited to share an update about the BeeGFS Community Edition as we look further ahead into 2026. From February, the Community Edition will transition from the current End User License Agreement (EULA) to a new BeeGFS License Agreement, designed to better support our users.<\/p>\n
This change is a deliberate step toward greater clarity and fairness in how BeeGFS is used across today\u2019s increasingly complex AI & HPC and related high-performance storage landscapes. It preserves the spirit of openness that has always defined BeeGFS, while introducing clear, transparent boundaries that distinguish community use from enterprise-scale and commercial deployments.<\/p>\n
The result is a future-proof licensing framework: one that supports genuine community adoption and contribution, and ensures that large-scale, production-grade environments are backed by appropriate Enterprise licensing.<\/p>\n
Important<\/em><\/strong>:<\/em> If you are already using BeeGFS Enterprise (including Hive Enterprise) under a commercial agreement, nothing for you changes. Your contracts, rights, deployments, and support terms remain fully intact.<\/p>\n Why the EULA no longer fits<\/em><\/strong><\/p>\n The EULA served BeeGFS well in its early years, helping it become the world\u2019s leading parallel file system for small and medium-sized AI and HPC clusters. It enabled broad access, supported increasing academic and research use, and helped build a strong global community.<\/p>\n However, the environment in which BeeGFS is deployed has evolved significantly.<\/p>\n Today, we operate in a world of:<\/p>\n Over time, we observed an increasing number of cases where BeeGFS Community was deployed in clearly commercial and production-scale contexts, often operated and supported by third parties while the EULA was accepted by end users rather than by the commercial entities providing services around BeeGFS.<\/p>\n This created legal ambiguity for everyone involved:<\/p>\n The EULA was never designed to clearly address modern service-based delivery models or large-capacity production usage. As a result, it no longer provided the legal certainty that users and partners need.<\/p>\n So, what is the BeeGFS License Agreement?<\/em><\/strong><\/p>\n The BeeGFS License Agreement is designed to remove that ambiguity.<\/p>\n It provides a clear, modern framework for users who deploy BeeGFS as a high-performance scratch file system for internal use, without third-party commercial involvement while defining transparent thresholds for when an Enterprise license is required.<\/p>\n What stays open<\/em><\/strong><\/p>\n Under the BeeGFS License Agreement, you can:<\/p>\n This ensures that scratch usage, experimentation, and internal innovation remain fully supported.<\/p>\n Clear Boundaries for Fair Use<\/em><\/strong><\/p>\n To ensure fairness and long-term sustainability, the new license introduces explicit safeguards.<\/p>\n BeeGFS Community may not be used for commercial services involving BeeGFS, including:<\/p>\n Capacity-based thresholds now apply:<\/p>\n Once these thresholds are exceeded\u00a0 or Enterprise features are required,\u00a0 a BeeGFS Enterprise license is needed. The transition path is straightforward and designed to support growth, not block it.<\/p>\n Community Registration key for clear license acceptance<\/em><\/strong><\/p>\n Starting with upcoming BeeGFS releases, we will introduce a simple registration step as part of the installation process of BeeGFS Community. This lightweight registration step ensures a clean and transparent legal framework by clearly identifying who accepts the BeeGFS License Agreement.<\/p>\n The registration step is not a technical limitation. Instead, it provides clarity and accountability by ensuring that the user deploying BeeGFS Community explicitly agrees to the license terms. This approach protects both users and ThinkParQ, reduces legal ambiguity, and helps preserve the integrity of the Community Edition as BeeGFS continues to scale.<\/p>\n Still open, still community-powered<\/em><\/strong><\/p>\n The team behind BeeGFS and I want to be absolutely clear: BeeGFS remains source-available and community-driven.<\/p>\n Nothing changes in how the community collaborates, which remains at the core of BeeGFS:<\/p>\n What has<\/em> changed is the legal framework around the Community Edition, designed to give both users and ThinkParQ greater confidence as BeeGFS continues to scale into new domains.<\/p>\n What if you\u2019ve already exceeded the threshold?<\/em><\/strong><\/p>\n If you previously deployed BeeGFS Community under the EULA and your existing installation exceeds the new capacity thresholds:<\/p>\n Our goal is continuity and transparency,\u00a0not disruption.<\/p>\n Looking ahead<\/em><\/strong><\/p>\n The\u00a0 BeeGFS License Agreement ensures that BeeGFS can remain:<\/p>\n
\nThis change affects only<\/em> users of the free-of-charge BeeGFS Community Edition previously licensed under the EULA.<\/p>\n\n
\n
\n
\n
\n
\n
\n