FOLIO is an open-source library services platform (LSP) designed, developed, and governed by a global community of libraries, vendors, developers, and consortia. Built from the ground up with a modern microservices architecture, FOLIO provides libraries with a modular, extensible system for managing core library operations including circulation, cataloging, acquisitions, electronic resource management, and reporting.
Key Features
- Modular microservices architecture: FOLIO uses an API gateway called Okapi to route requests between independently deployable modules, allowing libraries to choose only the functionality they need and add capabilities over time.
- Modern web-based interface: The user interface is built on Stripes, a single-page application toolkit, providing a responsive and accessible experience across devices for library staff and patrons.
- Comprehensive library workflows: Features cover inventory management, cataloging and bibliographic control, vendor and budget management, ordering and invoicing, electronic resource licensing, user management, circulation policies, fines and fees, recalls and holds, and data import and export.
- Multi-tenant cloud-ready design: The platform is designed for cloud deployment with native multi-tenancy, enabling consortia and library networks to share infrastructure while maintaining isolated configurations.
- Community-driven roadmap: Features and priorities are determined by the FOLIO community through special interest groups and a product council, with regular flower-named releases delivered on a predictable calendar.
Architecture and Technology
FOLIO was designed from the ground up as an API-driven system. The Okapi API gateway handles module and tenant management and proxies endpoints for business-logic interfaces such as patron management and circulation. Backend modules are primarily written in Java, while frontend modules use JavaScript with the Stripes UI toolkit. The platform leverages message queues, containerization, and continuous integration and delivery pipelines maintained by the community.
Community and Governance
The FOLIO community is open to libraries, developers, vendors, networks, and consortia of all sizes. Member organizations contribute resources including development work, cloud infrastructure for CI/CD and community testing, and software licenses. Multiple vendors offer hosting, support, and development services, giving libraries choice in how they deploy and maintain the platform. Governance is managed through councils and special interest groups that guide the roadmap, feature priorities, and technical direction.
Use Cases
- Academic and research libraries: Manage circulation, course reserves, interlibrary loan, and electronic resource subscriptions across multiple departments and patron types.
- Public libraries: Handle patron management, lending policies, fines, and reporting for diverse community populations.
- Library consortia and networks: Deploy shared infrastructure with multi-tenant isolation while enabling resource sharing and unified reporting across member institutions.
- Special libraries: Configure the modular platform to support domain-specific workflows in corporate, government, or museum libraries.
Hosting and Deployment Options
Libraries can choose from multiple hosting and support options, including self-hosting the open-source platform, working with vendor partners for managed hosting, or using community-operated environments for testing and development. This flexibility is a core principle of the project, giving libraries protection from vendor lock-in while still offering professional support options when needed.
