Total Cost of Ownership for a Library ILS

When comparing library systems, the sticker price is rarely the real price. This guide helps librarians, directors, and board members build a complete picture of what an ILS actually costs over time — and what to watch out for.

This framework applies whether you are evaluating a new system, justifying a migration, or preparing a budget request.

The Five Cost Categories

A complete ILS cost assessment covers five areas:

1. Licensing or subscription fees
2. Hosting and infrastructure
3. Support and maintenance contracts
4. Staff time (setup, ongoing operations, training)
5. Hidden and variable costs

Skipping any one of these gives an incomplete picture.

1. Licensing or Subscription Fees

This is the most visible cost — and the one most commonly used in vendor comparisons.

Commercial systems (Sierra, Alma, Polaris, Destiny, Follett) charge:

• An annual license or subscription fee
• Sometimes a per-seat or per-branch fee on top of the base price
• Module add-on fees (acquisitions, serials, ILL may be separate)

Open-source systems (Koha, Evergreen) are usually budgeted differently:

• Costs may shift away from a single bundled vendor subscription and into hosting, support, implementation, and staffing
• The exact mix depends on the hosting model, service scope, and internal technical capacity

What to ask your vendor:

• Is this fee fixed, or does it scale with collection size, patron count, or branches?
• What happens if we add a branch mid-contract?
• Are future version upgrades included?
• What modules are included vs. extra cost?

Watch out for: Multi-year contracts with built-in escalation clauses. A contract that seems reasonable in Year 1 may increase 5–8% annually.

2. Hosting and Infrastructure

Where your ILS runs has a significant cost — whether you see it as a line item or not.

Cloud-hosted (vendor or third-party managed)

The vendor or a hosting provider runs the servers. You pay a recurring fee.

Pros: No IT overhead, automatic updates, managed backups, predictable cost
Cons: Recurring cost, dependency on vendor uptime SLA, may have data residency restrictions

What to factor in: Monthly or annual hosting fee, data storage limits, bandwidth, disaster recovery terms.

Self-hosted (on-premises or self-managed VPS)

Your library runs the servers — either physical hardware on-site or a virtual server you provision.

Pros: Full control, no ongoing licensing for hosting, data stays in-house
Cons: IT staff time required, hardware depreciation, backup responsibility, higher upfront setup

What to factor in: Server hardware (amortized over 4–5 years), electricity, cooling, IT staff time for maintenance and upgrades, backup storage costs.

Consortium-hosted

A library consortium or regional network hosts the ILS for member libraries.

Pros: Shared cost, community governance, built-in support network
Cons: Less control over upgrade timing, shared resources may slow response

What to factor in: Annual consortium membership fee, any per-library surcharges, and what happens if you leave the consortium.

3. Support and Maintenance

Even open-source systems need someone to maintain and support them.

Vendor support (commercial ILS):

• Usually bundled into the annual fee, but verify what’s included
• Is 24/7 support included, or only business hours?
• What is the typical response time for critical issues?
• Is training included, or billed separately?

Community support (open-source):

• Free: community forums, mailing lists, IRC/Matrix, documentation
• Appropriate for: technically capable staff who can troubleshoot independently
• Not appropriate for: libraries without any technical staff

Professional support contracts (open-source):

• Third-party support providers offer SLAs, phone/email support, patch management
• Priced per library, per branch, or by service tier
• KohaSupport, ByWater, Equinox, and others offer this for Koha

What to compare: Don’t compare vendor license (which includes support) against open-source software (no license, no built-in support) as if they are equivalent. Compare the total package: license + support for commercial vs. support contract for open-source.

4. Staff Time

Staff time is often the largest cost in an ILS budget, and the one most frequently underestimated.

Initial Setup and Migration

Any new ILS requires a setup period. Factor in:

• Project coordination: Who manages the migration? At what % of their time?
• Data work: Exporting, cleaning, mapping, and importing MARC records and patron data
• Configuration: Setting up branches, circulation rules, item types, patron categories
• Integrations: Self-checkout, RFID, payment processors, discovery layers
• Testing: Staff time to verify data quality and test workflows before go-live

See Migrate to Koha from Other ILS Systems for a phase-by-phase staff time breakdown.

Ongoing Operations

After go-live, your ILS requires ongoing staff attention:

• Cataloging: Time spent adding new items (copy cataloging vs. original cataloging)
• System administration: User management, system preferences, plugin/module updates
• Reporting: Generating statistics, annual reports, circulation reports
• Troubleshooting: Resolving patron and staff issues with the system
• Upgrades: Time to read release notes, test in staging, and deploy new versions

A common mistake: Libraries calculate software costs carefully but forget to account for the staff time that shifts when moving from a system with lots of vendor hand-holding to one that requires more in-house technical skill — or vice versa.

Training

• Initial training for all staff at go-live (reduced productivity for 2–4 weeks)
• Ongoing training as staff turn over (new hires need to learn the system)
• Advanced training for power users (catalogers, systems librarians)
• Training materials development (documenting your local workflows)

5. Hidden and Variable Costs

These are the costs that commonly surprise libraries in budget preparation.

Data Extraction Fees

Some commercial ILS vendors charge a fee to export your own data when you leave. This is worth confirming in writing before signing a contract.

Ask: “If we choose not to renew, what is the process and cost for us to receive a full export of our bibliographic, patron, and circulation data in standard formats?”

Add-On Module Costs

Some ILS products have a core module that looks affordable, but key functionality is separate:

• Acquisitions module (ordering, invoicing)
• Serials management
• ILL (interlibrary loan) integration
• Patron self-service portal
• Discovery layer / OPAC customization

Koha makes these capabilities available within the broader Koha platform. Some commercial systems package similar capabilities as separate modules or service tiers.

API and Integration Fees

If you need to connect your ILS to other systems (a payment processor, a digital asset management system, a self-checkout machine, a learning management system), some vendors charge:

• API access fees
• Per-call transaction fees
• Certified vendor fees (only certain third-party integrations are permitted)

Koha has an open REST API with no per-call or certification fees.

Upgrade and Version Change Costs

For self-hosted open-source systems: major version upgrades require staff time but no additional license cost.

For commercial systems: some vendors charge separately for major version upgrades, or require you to upgrade to a new product entirely (e.g., III’s transition from Millennium to Sierra).

Downtime and Service Interruption

Unplanned downtime has a cost — staff can’t check out items, patrons can’t access the catalog, reports can’t be run. Evaluate:

• What is the vendor’s uptime SLA?
• What is the compensation if SLA is missed?
• Does your library have a manual backup process for circulation if the system is unavailable?

Building Your TCO Comparison

When evaluating systems side by side, build a spreadsheet with these rows for each option:

Category                          Year 1      Year 2      Year 3      Year 4      Year 5
────────────────────────────────────────────────────────────────────────────────────────
Licensing / subscription
Hosting (vendor, VPS, or IT labor)
Support contract
Migration / setup (one-time)
Staff time: setup & migration
Staff time: training
Staff time: ongoing operations (delta)
Add-on modules
Data extraction fee (when leaving)
Infrastructure (hardware, depreciation)
────────────────────────────────────────────────────────────────────────────────────────
TOTAL

Fill in what you know. Leave cells blank rather than guessing. Where you don’t know a number, contact the vendor — or contact libraries using the system you’re evaluating to ask what they actually pay.

Questions to Ask Any ILS Vendor

Before signing:

1. What is included in the annual fee, and what costs extra?
2. What is the process and cost to export our data if we don’t renew?
3. What is your uptime SLA, and what is the remedy if it’s missed?
4. Are API integrations included, or is there a fee?
5. What does a major version upgrade cost?
6. Is training included, or billed separately?
7. Can you provide references from libraries of similar size and type?

Open-Source vs. Commercial: What the Comparison Actually Is

A fair comparison is not “commercial subscription versus a supposedly free alternative.” It is:

The genuine trade-off is: commercial systems offer more hand-holding; open-source systems offer more control and lower long-term cost at the expense of more internal technical responsibility.

How KohaSupport Fits Into This Framework

KohaSupport deploys Koha on your own AWS account — you own your data and infrastructure, with no per-seat fees or vendor lock-in.

Unlike traditional hosted Koha providers, KohaSupport uses your AWS account — so when you compare TCO, there’s no recurring markup on AWS infrastructure costs. See full plan details →

Related Resources

• Migrate to Koha from Other ILS Systems — Phase-by-phase migration guide for Sierra, Evergreen, Millennium, Alma
• Koha for Small Libraries — How Koha fits small and solo library situations
• Copy Cataloging Workflow — Advanced Guide — How to reduce per-item cataloging costs with Koha
• What Is Koha? — Overview of Koha for librarians new to the system