Two decades of distributed storage
MooseFS began as an internal storage platform at Gemius, a European internet-measurement company operating across more than 20 countries. It was released as open-source software soon after, and has been in continuous production ever since — carrying real workloads at Gemius and at customers around the world. Today it is developed and maintained by Saglabs SA in Warsaw, Poland.
Milestones
A short, chronological view of how MooseFS got to where it is today. For the full release log — every version, every bug fix — see the changelog.
-
2005
In production at Gemius
MooseFS goes into production as the storage layer for Gemius’ internet-measurement platform, processing more than 300,000 events per second around the clock. It has been running there ever since.
-
2008
Released as open source
After several years of real-world use inside Gemius, MooseFS is spun off and released to the public under GPLv2, available for anyone to deploy on commodity hardware.
-
2010s
The Pro edition
A commercial Pro edition is introduced for organizations that need automatic master failover, multi-location clusters, and 24/7 support direct from the engineers who write the code. The two editions share one codebase.
-
2017
MooseFS 4.0 — erasure coding
Version 4.0.0 ships in February with the first erasure-coding implementation, giving clusters space-efficient durability alongside the existing goal-based replication.
-
2023
Community and Pro re-aligned
Version 4.50.0 reorganises the build so the Community and Pro editions share a single codebase the way earlier 3.x releases did — cleaner upgrades, simpler operations, fewer surprises moving between editions.
-
2024
Storage class priority and grouping
Version 4.57.0 introduces storage class priority and grouping — finer-grained control over where data lands across mixed-tier hardware.
-
2026
MooseFS 5 Pro — multi-location clusters and I/O security
MooseFS 5 Pro is released with two flagship additions: native multi-location cluster support for geographically distributed deployments, and enhanced I/O security hardening the data path against unauthorized access at the storage layer.
See the full changelog
The milestones above are the headline moments. For the complete version-by-version detail — every release on the 4.x line and before — the changelog is the source of truth.