I'm a library technician. What is the best integrated library system (ILS) for a small academic library?
Data as of Sep 21, 2026 · Based on 347 AI responses from ChatGPT Search and Google AI Mode · See how Parse measures this
Data as of Sep 21, 2026 · Based on 347 AI responses from ChatGPT Search and Google AI Mode · See how Parse measures this
For most small academic libraries, Koha is the practical best fit: it’s low-cost, flexible, and has vendor/community support options. Choose Ex Libris Alma only if you have the budget and need strong cloud-based management for mixed digital and print collections. For very small or highly specialized collections, consider TinyCat or Libib for a simple, inexpensive setup.
Brands AI recommends here
Named in 81% of answers
Named in 36% of answers
Named in 35% of answers
Best when budget and consortium needs allow: strong cloud-based management for digital+print and reduced local IT, but it’s a premium option that may be overkill for tiny libraries.
Named in 26% of answers
For a **small academic library, I’d put Koha at the top of the shortlist**. It is a mature open-source ILS with cataloging, circulation, acquisitions, serials, course reserves, ILL, reporting, and electronic-resource management. [Koha Community](https://koha-community.org/about/?utm_source=chatgpt.com) [Koha…
For a small academic library, I’d put Koha at the top of the shortlist. It is a mature open-source ILS with cataloging, circulation, acquisitions, serials, course reserves, ILL, reporting, and electronic-resource management.
The 2025 Library Perceptions data show small academic libraries reporting strong satisfaction with Koha, while WorldShare Management Services and Alma are also substantial alternatives.
For a small college library, I’d specifically investigate hosted Koha rather than self-hosting.
For a **small academic library**, I’d put **Koha, FOLIO, and Alma** at the top of the shortlist—but the right choice depends heavily on your staffing, electronic-resource workload, and appetite for managing technology. ### My practical shortlist System | Best fit | Main strength | Main trade-off
For a small academic library, I’d put Koha, FOLIO, and Alma at the top of the shortlist—but the right choice depends heavily on your staffing, electronic-resource workload, and appetite for managing technology.
| System | Best fit | Main strength | Main trade-off |
|---|---|---|---|
| Koha | Small library with limited budget | Full-featured, open-source ILS with relatively low licensing costs | E-resource management and some integrations may require more work |
| FOLIO | Small-to-medium academic library wanting a modern platform | Modular architecture, strong e-resource functionality, open ecosystem | More complex than a traditional ILS and potentially heavier implementation |
| Alma | Academic library heavily dependent on electronic resources | Excellent integrated management of print, electronic and digital resources | Commercial system and potentially substantial cost/complexity |
Koha would be the first system I'd investigate. It is a genuinely full-featured ILS: acquisitions, circulation, cataloging, serials, authorities, reporting, notices, offline circulation, and more. It is open source and is used by libraries of different sizes and types.
That makes it particularly interesting when you have a small staff and a constrained budget, provided you choose a good hosting/support provider rather than assuming your library has to administer everything itself.
FOLIO is the more interesting option if your academic library has a substantial electronic-resource operation. It isn't simply a traditional ILS; it's a modular library services platform covering circulation, acquisitions, cataloging, ERM, reporting, and other functions. It's open source and can be hosted by a service provider.
FOLIO has also continued active development—the project announced its Trillium release in July 2026—so it's worth considering if you're looking for a platform rather than a conventional ILS.
Alma becomes particularly compelling when electronic resources are central to the library. It brings print, electronic, and digital-resource management together and integrates with discovery and campus systems. Ex Libris also documents extensive API and SIS/ERP integration capabilities.
The important caveat is that "small" doesn't automatically mean Koha. A small liberal-arts college with 30,000 mostly print volumes has very different requirements from a small graduate institution with 10,000 e-journal packages and complex license management.
I'd score the vendors against these requirements rather than choosing based on feature count:
One particularly important distinction is ILS vs. LSP. Koha is closer to the traditional ILS model, while FOLIO and Alma are designed around broader management of modern print/electronic/digital collections. FOLIO itself explicitly describes its LSP as including traditional LMS/ILS functionality plus additional capabilities.
Bottom line: for a genuinely small academic library, I'd start with Koha vs. FOLIO, and add Alma if your electronic-resource and campus-integration requirements are substantial. I wouldn't choose solely on acquisition/circulation/cataloging features—they're table stakes; implementation effort, e-resource workflows, support, integrations, and total cost over 5–10 years are likely to matter much more.
If you tell me roughly (1) number of FTE library staff, (2) collection size, (3) print vs. electronic mix, (4) annual budget, and (5) whether you're currently on another ILS, I can give you a much more concrete comparison of Koha vs. FOLIO vs. Alma for your situation.
FOLIO is the more interesting option if your academic library has a substantial electronic-resource operation. It isn't simply a traditional ILS; it's a modular library services platform covering circulation, acquisitions, cataloging, ERM, reporting, and other functions. It's open source and can be hosted by a service provider.
FOLIO has also continued active development—the project announced its Trillium release in July 2026—so it's worth considering if you're looking for a platform rather than a conventional ILS.
Alma becomes particularly compelling when electronic resources are central to the library. It brings print, electronic, and digital-resource management together and integrates with discovery and campus systems. Ex Libris also documents extensive API and SIS/ERP integration capabilities.
The important caveat is that "small" doesn't automatically mean Koha. A small liberal-arts college with 30,000 mostly print volumes has very different requirements from a small graduate institution with 10,000 e-journal packages and complex license management.
I'd score the vendors against these requirements rather than choosing based on feature count:
For a small academic library, the "best" ILS (Integrated Library System) or modern **LSP (Library Services Platform)** depends heavily on your budget, IT support, and whether your collection is heavily print-based or hybrid/electronic.[[1]](https://americanlibrariesmagazine.org/2024/05/01/2024-library-systems-report/)…
For a small academic library, the "best" ILS (Integrated Library System) or modern LSP (Library Services Platform) depends heavily on your budget, IT support, and whether your collection is heavily print-based or hybrid/electronic.
As a library technician handling day-to-day workflows like circulation, serials, and routine cataloging, you need a system that isn't overly bloated for a massive research institution, yet robust enough to handle student course reserves and academic databases.
The top contenders for a small academic library break down into three distinct categories:
Community discussions often highlight the stark contrast between managing an open-source system versus paying for a streamlined commercial product:
Koha is great! Our libraries use KOHA. It's a little bare-bones, but very nice for our small library system with a correspondingly small budget.
EOS.web from Sirsi Dynix... it's simple and user friendly, with communicative and helpful support.
To help narrow down which system fits your floor plan, could you tell me:
For a **small academic library**, I’d put **Koha** at the top of the list—especially if you want good functionality without locking the library into a large commercial platform. A useful 2025 survey of library automation systems backs that up: among **small academic libraries**, Koha scored **7.43/10 for overall ILS…
For a small academic library, I’d put Koha at the top of the list—especially if you want good functionality without locking the library into a large commercial platform.
A useful 2025 survey of library automation systems backs that up: among small academic libraries, Koha scored 7.43/10 for overall ILS functionality, essentially level with Alma (7.50) and WorldShare (7.52). Koha also scored well for overall satisfaction among academic libraries.
| System | Best fit | My take |
|---|---|---|
| Koha | Small, independent academic library | Best overall value |
| OCLC WorldShare Management Services | Small library wanting a fully managed cloud service | Best commercial/managed option |
| Ex Libris Alma | E-resource-heavy or research-oriented institution | Best enterprise option, but potentially overkill |
| FOLIO | Library with technical expertise and desire for extensibility | Best open platform alternative |
| SirsiDynix Symphony | Library wanting a conventional mature ILS | Solid, but not my first choice for a new small installation |
Koha is unusually well suited to small libraries because it is open source, mature, and doesn't artificially restrict you to a particular size of institution. It includes cataloging, circulation, acquisitions, serials, authorities, reporting, notices, offline circulation, and other core ILS functions.
The important caveat is that Koha is software, not a turnkey service. You'll need to decide who provides hosting, implementation, upgrades, backups, and technical support. For a small library without IT staff, I'd strongly favor a reputable Koha service provider rather than self-hosting.
I'd choose Koha if: your collection is predominantly print, you have a modest e-resource footprint, your budget matters, and you value control and flexibility.
OCLC's WorldShare Management Services is attractive if your priority is minimizing the technical burden on library staff. In the 2025 survey, WorldShare had the highest overall functionality score among small academic libraries in the reported data (7.52), and it was particularly well regarded for support.
The tradeoff is cost and greater dependence on a commercial ecosystem.
I'd choose WorldShare if: you're already deeply invested in OCLC, participate in OCLC-based resource sharing, or simply don't want your technician/library staff worrying about servers and system administration.
Alma is extremely capable. It brings print, electronic, and digital resources together and has sophisticated acquisitions, electronic-resource management, analytics, integrations, and discovery capabilities.
That's precisely why I wouldn't automatically recommend it to a small academic library. If you're managing a lot of databases, e-journals, licenses, digital collections, consortial workflows, or research-support services, Alma becomes much more compelling.
I'd choose Alma if: you're small in headcount but not simple in collection complexity.
FOLIO is another open-source option. It's a modern, cloud-oriented library services platform with apps covering circulation, cataloging, acquisitions, e-resources, users, reporting, and more.
Its flexibility is appealing, but for a small library with limited technical resources, I'd generally take Koha over FOLIO unless there's a specific institutional reason to choose FOLIO.
If you told me only:
"We're a small academic library, have a limited budget, and need a dependable ILS." I'd rank them:
1. Koha 🥇 2. WorldShare 3. Alma 4. FOLIO 5. Symphony
But the answer changes considerably depending on collection size, number of staff, annual ILS budget, proportion of e-resources, consortium membership, and whether you need an integrated discovery layer.
If you give me those 5–6 details, I can make you a much more practical Koha vs. WorldShare vs. Alma comparison, including likely costs, implementation difficulty, cataloging/circulation workflows, e-resource management, reporting, and what the day-to-day experience would be for a library technician.
For a small academic library, the "best" Integrated Library System (ILS) or Library Services Platform (LSP) depends heavily on your budget, IT support, and how heavily your collection leans into electronic resources (e-journals, databases) versus physical books. Small academic libraries generally choose from three…
For a small academic library, the "best" Integrated Library System (ILS) or Library Services Platform (LSP) depends heavily on your budget, IT support, and how heavily your collection leans into electronic resources (e-journals, databases) versus physical books.
Small academic libraries generally choose from three tiers of systems:
To help narrow down the best fit, could you share:
For a small academic library, the "best" ILS (or modern Library Services Platform, LSP) `depends heavily on your budget` , whether you have an IT department to support local hosting, and how heavily your collection leans into electronic resources versus traditional print. Unlike large universities that require massive…
For a small academic library, the "best" ILS (or modern Library Services Platform, LSP) depends heavily on your budget , whether you have an IT department to support local hosting, and how heavily your collection leans into electronic resources versus traditional print.
Unlike large universities that require massive enterprise systems like Ex Libris Alma or Clarivate Primo, small academic libraries need a sweet spot: affordable, strong in MARC cataloging, and capable of handling student/faculty workflows without requiring a systems librarian on a 24/7 retainer.
The top contenders for a small academic library break down as follows:
To help narrow down which system would actually make your daily work life easier, tell me a bit more about your library:
For a **small academic library**, my first choice in 2026 would be **Koha**—especially if you have a small staff, a limited technology budget, and want to avoid being locked into a large commercial platform. ### My shortlist ILS / LSP | Best fit | My take
For a small academic library, my first choice in 2026 would be Koha—especially if you have a small staff, a limited technology budget, and want to avoid being locked into a large commercial platform.
| ILS / LSP | Best fit | My take |
|---|---|---|
| Koha | Small, budget-conscious academic library | 🥇 Best overall |
| WorldShare Management Services | Libraries already invested in OCLC/WorldCat | 🥈 Excellent managed option |
| Alma | E-resource-heavy academic libraries | 🥉 Powerful, but potentially overkill |
| FOLIO | Technically sophisticated libraries wanting an open platform | Worth considering, but more complex |
Koha gives you a remarkably complete ILS without proprietary licensing fees. It supports cataloging, circulation, acquisitions, serials, authorities, reporting, notices, labels, offline circulation, and more. It's used by libraries ranging from single-branch organizations to large consortia.
The important distinction is that free software doesn't necessarily mean free to operate. For a small academic library, I'd strongly consider having a commercial provider host and support Koha rather than maintaining the server yourself.
There's also some encouraging current evidence: in the 2025 Library Perceptions survey, small academic libraries gave Koha an 8.14/10 mean satisfaction score, compared with 7.52 for WorldShare and 7.26 for Alma. The Koha sample was much smaller, however, so I wouldn't interpret that as a definitive statistical ranking.
Alma becomes much more attractive if your library has a large electronic-resource collection, complicated licenses, substantial digital collections, or extensive scholarly-resource workflows.
Alma is designed to bring print, electronic, and digital resources together and provides extensive academic-library workflows.
If your institution already belongs to an Alma consortium, I'd also give Alma considerably more weight. The benefits of fitting into an existing institutional/consortial infrastructure can outweigh the disadvantages of using a larger system.
FOLIO is very interesting if you have someone with substantial technical expertise. It's open source, cloud-oriented, modular, and covers circulation, acquisitions, cataloging, electronic-resource management, reporting, and other workflows.
But for a small library with one or two technicians and little dedicated IT support, I'd generally choose Koha first. FOLIO's flexibility and modern architecture are advantages, but they can also mean more implementation and administration complexity.
I'd use this:
If you tell me roughly how many FTE staff you have, collection size, annual materials budget, whether you manage many e-resources, and what ILS you're using now, I can narrow this down to a specific recommendation—and include estimated implementation/hosting costs and migration difficulty.
Koha gives you a remarkably complete ILS without proprietary licensing fees. It supports cataloging, circulation, acquisitions, serials, authorities, reporting, notices, labels, offline circulation, and more. It's used by libraries ranging from single-branch organizations to large consortia.
The important distinction is that free software doesn't necessarily mean free to operate. For a small academic library, I'd strongly consider having a commercial provider host and support Koha rather than maintaining the server yourself.
There's also some encouraging current evidence: in the 2025 Library Perceptions survey, small academic libraries gave Koha an 8.14/10 mean satisfaction score, compared with 7.52 for WorldShare and 7.26 for Alma. The Koha sample was much smaller, however, so I wouldn't interpret that as a definitive statistical ranking.
Alma becomes much more attractive if your library has a large electronic-resource collection, complicated licenses, substantial digital collections, or extensive scholarly-resource workflows.
Alma is designed to bring print, electronic, and digital resources together and provides extensive academic-library workflows.
If your institution already belongs to an Alma consortium, I'd also give Alma considerably more weight. The benefits of fitting into an existing institutional/consortial infrastructure can outweigh the disadvantages of using a larger system.
FOLIO is very interesting if you have someone with substantial technical expertise. It's open source, cloud-oriented, modular, and covers circulation, acquisitions, cataloging, electronic-resource management, reporting, and other workflows.
But for a small library with one or two technicians and little dedicated IT support, I'd generally choose Koha first. FOLIO's flexibility and modern architecture are advantages, but they can also mean more implementation and administration complexity.
I'd use this:
For a **small academic library**, my default recommendation in 2026 would be **Koha**—unless your library has unusually complex electronic-resource needs or is already deeply tied to OCLC or Ex Libris. ### My shortlist System | Best fit | My take
For a small academic library, my default recommendation in 2026 would be Koha—unless your library has unusually complex electronic-resource needs or is already deeply tied to OCLC or Ex Libris.
| System | Best fit | My take |
|---|---|---|
| Koha | Small, independent academic libraries | Best overall value |
| WorldShare Management Services (WMS) | Libraries heavily using OCLC/WorldCat | Best commercial choice |
| Alma | E-resource-heavy or research-oriented institutions | Excellent, but often more system than a small library needs |
| FOLIO | Technically capable libraries wanting an extensible/open platform | Powerful, but higher complexity |
| Evergreen | Consortial/shared-catalog environments | Worth considering if you're in a consortium |
Koha is unusually well suited to a small academic operation. It's genuinely open source, has no software licensing fee, and provides the core functionality you'd expect: cataloging, circulation, acquisitions, serials, authorities, reporting, notices, and more. It's used by libraries ranging from single-branch operations to large consortia.
The big advantage for a small library is proportionate complexity. You can have a full-featured ILS without adopting an enterprise platform designed around hundreds of thousands or millions of records and elaborate e-resource workflows.
You also don't necessarily need to maintain the server yourself. Commercial Koha providers can handle hosting, upgrades, backups, and support while you retain the benefits of an open-source system.
OCLC's WorldShare Management Services is particularly attractive if your library already depends heavily on WorldCat, OCLC cataloging, interlibrary loan, or a consortium.
WMS combines acquisitions, cataloging/metadata, e-resource management, discovery, circulation, resource sharing, and reporting in a cloud platform, with WorldCat at its foundation. OCLC OCLC OCLC has also continued to add academic libraries to WMS during 2026.
I'd choose WMS over Koha if reducing local systems administration and maximizing integration with OCLC are more important to you than minimizing cost and vendor dependence.
Ex Libris Alma becomes compelling if you have a relatively small physical collection but a large and complicated electronic collection—lots of databases, licenses, packages, electronic journals, resource sharing, or sophisticated discovery requirements.
For a traditional small college library where most of your work is cataloging, circulation, acquisitions, reserves, and basic e-resource management, though, I'd be reluctant to pay for that level of enterprise functionality.
FOLIO is worth serious consideration if your institution has good technical support and wants an open, modern, highly extensible platform. It covers circulation, acquisitions, cataloging, e-resources, users, reporting, and more.
Its architecture is considerably more sophisticated than a traditional ILS, however. FOLIO itself describes its platform as modular, cloud-oriented, API-driven, and microservices-based. FOLIO | folio.org That is an advantage for an institution with technical resources, but potentially a disadvantage for a two-person library where "I need this thing to just work" is the priority.
If I were evaluating systems for a small academic library with, say, 10,000–150,000 volumes and a small staff, my starting order would be:
The most important caveat is that "best ILS" depends heavily on your library's workflow. For a library technician, I'd pay particular attention to the day-to-day staff experience: batch cataloging, importing MARC records, barcode/item creation, holds, renewals, notices, inventory, acquisitions, reporting, and how easy it is to correct mistakes.
If you tell me roughly (1) collection size, (2) number of staff, (3) annual acquisitions, (4) print vs. electronic mix, (5) whether you're already an OCLC customer, and (6) your approximate budget, I can narrow this to a specific recommendation and give you a Koha vs. Alma vs. WMS comparison tailored to your library.
The big advantage for a small library is proportionate complexity. You can have a full-featured ILS without adopting an enterprise platform designed around hundreds of thousands or millions of records and elaborate e-resource workflows.
You also don't necessarily need to maintain the server yourself. Commercial Koha providers can handle hosting, upgrades, backups, and support while you retain the benefits of an open-source system.
OCLC's WorldShare Management Services is particularly attractive if your library already depends heavily on WorldCat, OCLC cataloging, interlibrary loan, or a consortium.
WMS combines acquisitions, cataloging/metadata, e-resource management, discovery, circulation, resource sharing, and reporting in a cloud platform, with WorldCat at its foundation. OCLC OCLC OCLC has also continued to add academic libraries to WMS during 2026.
I'd choose WMS over Koha if reducing local systems administration and maximizing integration with OCLC are more important to you than minimizing cost and vendor dependence.
Ex Libris Alma becomes compelling if you have a relatively small physical collection but a large and complicated electronic collection—lots of databases, licenses, packages, electronic journals, resource sharing, or sophisticated discovery requirements.
For a traditional small college library where most of your work is cataloging, circulation, acquisitions, reserves, and basic e-resource management, though, I'd be reluctant to pay for that level of enterprise functionality.
FOLIO is worth serious consideration if your institution has good technical support and wants an open, modern, highly extensible platform. It covers circulation, acquisitions, cataloging, e-resources, users, reporting, and more.
Its architecture is considerably more sophisticated than a traditional ILS, however. FOLIO itself describes its platform as modular, cloud-oriented, API-driven, and microservices-based. That is an advantage for an institution with technical resources, but potentially a disadvantage for a two-person library where "I need this thing to just work" is the priority.
For a small academic library, **OCLC WorldShare Management Services (WMS)** and **Koha** (via a support vendor like ByWater Solutions) are generally considered the best options, balancing academic needs, electronic resource handling, and modest budgets. While enterprise platforms like Ex Libris Alma are powerful, they…
For a small academic library, OCLC WorldShare Management Services (WMS) and Koha (via a support vendor like ByWater Solutions) are generally considered the best options, balancing academic needs, electronic resource handling, and modest budgets.
While enterprise platforms like Ex Libris Alma are powerful, they are often overkill and too expensive for smaller footprints.
Top Recommendations for Small Academic Libraries
Key Features a Library Technician Should Look For
As someone handling the day-to-day configuration, circulation, and cataloging, prioritize an ILS that offers:
To help narrow down the ideal choice, could you tell me:
I can provide a more tailored vendor comparison.
For a **small academic library**, my first choice would generally be **Koha**—but there are a few important exceptions depending on your institution's size, e-resource workload, consortium relationships, and IT support. ## My shortlist System | Best fit | My take
For a small academic library, my first choice would generally be Koha—but there are a few important exceptions depending on your institution's size, e-resource workload, consortium relationships, and IT support.
| System | Best fit | My take |
|---|---|---|
| Koha | Small independent academic library | Best overall |
| WorldShare Management Services | OCLC/WorldCat-heavy libraries | Best commercial choice |
| Alma | E-resource-heavy/research libraries | Excellent, but potentially overkill |
| FOLIO | Technically sophisticated libraries | Powerful, but more complex |
Koha hits a particularly good sweet spot for a small college library: it's open source, full-featured, scalable, and doesn't require you to buy into a large proprietary ecosystem. It supports cataloging, circulation, acquisitions, serials, authorities, reporting, notices, and other standard ILS functions.
The big advantage for a small staff is that you don't necessarily have to administer the software yourself. Commercial organizations can provide hosting, implementation, support, and other services while you retain the advantages of an open-source system.
There's also some encouraging recent satisfaction data. In the 2026 Library Perceptions survey, Koha received an 8.10/10 mean satisfaction score among academic libraries, versus 7.34 for WorldShare and 7.26 for Alma. The Koha sample was much smaller, however, so I wouldn't interpret that as a definitive ranking.
I'd pick Koha if your library:
If your library already depends heavily on OCLC, WorldCat, resource sharing, and interlibrary loan, I'd give WorldShare Management Services serious consideration.
The appeal is less about raw ILS functionality and more about the integration with the OCLC ecosystem. For a library that's already deeply invested there, the additional convenience can outweigh Koha's cost and flexibility advantages.
Alma becomes much more compelling if you're managing lots of databases, electronic journals, licenses, packages, digital resources, and other complex scholarly materials.
It's particularly attractive if your institution is already part of an Alma/Primo consortium. Alma and Primo are designed to work together, with unified management and discovery workflows and extensive integration capabilities.
For a small liberal-arts college with, say, 50,000–150,000 physical volumes and relatively straightforward electronic resources, though, I'd be cautious about buying an enterprise-scale platform simply because it's popular in academic libraries.
FOLIO is an open-source Library Services Platform rather than a conventional ILS. It has modules for cataloging, circulation, acquisitions, electronic-resource management, reporting, etc., and its API-driven, modular architecture is designed for extensibility.
That's exciting—but for a small library with limited technical resources, I'd generally choose Koha first. FOLIO makes more sense when you have good technical support, sophisticated workflows, or a vendor/consortium handling much of the implementation and infrastructure.
I'd narrow the evaluation to Koha vs. WorldShare vs. Alma, with FOLIO as a fourth option if your institution has strong technical support.
The deciding questions I'd ask are:
If you give me those details, I can make a much more specific recommendation—down to which system I'd choose and why, plus a practical comparison of cost, cataloging, acquisitions, circulation, serials, e-resource management, reporting, discovery, migration, and staff usability.
Alma becomes much more compelling if you're managing lots of databases, electronic journals, licenses, packages, digital resources, and other complex scholarly materials.
It's particularly attractive if your institution is already part of an Alma/Primo consortium. Alma and Primo are designed to work together, with unified management and discovery workflows and extensive integration capabilities.
For a small liberal-arts college with, say, 50,000–150,000 physical volumes and relatively straightforward electronic resources, though, I'd be cautious about buying an enterprise-scale platform simply because it's popular in academic libraries.
FOLIO is an open-source Library Services Platform rather than a conventional ILS. It has modules for cataloging, circulation, acquisitions, electronic-resource management, reporting, etc., and its API-driven, modular architecture is designed for extensibility.
That's exciting—but for a small library with limited technical resources, I'd generally choose Koha first. FOLIO makes more sense when you have good technical support, sophisticated workflows, or a vendor/consortium handling much of the implementation and infrastructure.
I'd narrow the evaluation to Koha vs. WorldShare vs. Alma, with FOLIO as a fourth option if your institution has strong technical support.