Koha support services: what they include and how they work

Why free Koha does not mean zero-cost Koha

The confusion is understandable: Koha has no license, so it seems reasonable to think that once it is implemented, spending stops. In practice, three things keep happening every month, whether or not anyone is paying for them explicitly:

• Koha keeps releasing versions. The community publishes two major releases a year, in May and November, and monthly maintenance releases with bug fixes and security patches. It generally maintains two to three major versions at a time, each for an average of 18 months, so an instance that is not updated drops out of maintenance and becomes exposed.
• The server needs maintenance. The operating system, the database, HTTPS certificates and backups do not administer themselves, whether they live on your own server or in the cloud.
• Operational incidents happen. A report that stops returning the right result, a plugin that breaks, a misconfigured circulation rule, the OPAC down on the first Monday of the semester.

Koha support is therefore not a commercial whim layered on free software: it is the answer to something already happening in every production instance, under contract or not. If you have not implemented Koha yet, this is not the guide you need; start with our Koha implementation guide.

What Koha support services include

Contracts vary between providers, but serious Koha support covers at least these fronts:

• Incident resolution. A channel to report failures (the OPAC will not load, a loan is not recorded, a report gives a wrong result) and a commitment to handle them within an agreed time, prioritized by whether the library has stopped operating or the issue is a minor adjustment.
• Version upgrades. Applying maintenance releases with security patches and planning the move to major versions when appropriate, rather than the institution discovering it is out of date when that is already a problem. After a major upgrade, plan two weeks of reinforced support: most tickets in that period are not failures but questions about where an option moved. If your instance has not been touched in a while, read how to upgrade Koha without losing data first.
• Infrastructure administration, when the provider also hosts the system: server monitoring, automatic backups that are verified rather than merely scheduled, and HTTPS certificate renewal. Hosting options are compared in our Koha hosting guide.
• Configuration adjustments that arise from real use: new circulation rules, patron categories, notice templates, permissions by profile.
• A defined support channel, not a generic mailbox nobody reads: the library knows exactly whom to write to and what response to expect.

What serious support does not promise is what cannot be sustained. BiblioLabTech does not promise response times in exact minutes or 100% availability, because those are figures most providers fail to meet in practice. What can be committed, and what we offer, is a clear channel, priority according to the severity of each incident and response times agreed in the contract.

Community support vs contracted support

Koha has an active global community: mailing lists, chat channels, an extensive wiki and developers who answer technical questions voluntarily. It is a real resource, and every Koha library should know it. But it has limits that a library in production cannot always afford:

Contracted support does not replace the community. A good provider takes part in it and benefits from its technical discussions. What contracted support adds is what the community, by definition, cannot give: accountability, an agreed response time and continuity.

Why institutions pay for support when Koha is free

The question many libraries ask while budgeting is reasonable: if there is no license, why pay for support? The short answer is that you do not pay for the software; you pay for the software to keep working well over time. Three concrete reasons:

1. The OPAC is a public service exposed to the internet. An unpatched vulnerability is not an abstract problem: it is an open door to a system that holds patron data.
2. The cost of an unresolved incident far exceeds the cost of support. A catalog down during enrollment week, or a loan that cannot be recorded on the day textbooks are handed out, carries an operational and reputational cost that an annual support contract does not come close to.
3. Library staff are not there to run servers. A librarian trained in cataloging and reference does not need, and usually does not want, to learn how to patch Debian or debug a MariaDB log. That time is worth more applied to their own role.

What Koha support usually does not cover

It is just as important to say what is excluded, because that is where most misunderstandings between library and provider arise. Unless contracted as a separate service, Koha support does not usually include:

• Development of new features that do not exist in the base software.
• Integrations with external systems the institution decides to add later, such as a remote-access proxy, an institutional ERP or a payment system.
• The initial data migration from another platform, which is an implementation project, not maintenance; see how to migrate to Koha.
• Extensive training for staff who join long after go-live, although many providers, BiblioLabTech included, offer refresher sessions within the relationship.

Making this clear in the contract avoids the most common conflict: a library that assumes "support" means "anything we need" and a provider that reads the contract more narrowly.

Time zone and language matter in support

When the OPAC fails on a Monday morning, the provider's time zone decides whether someone answers that morning or the next day. BiblioLabTech works from UTC−5, which overlaps the full working day across the Americas and the afternoon in Europe and Africa, and answers in English, Spanish, Portuguese and French. That matters for multilingual institutions and for libraries whose staff prefer to describe a circulation problem in their own language. It also matters that whoever answers understands what an academic term is, what pressure an enrollment calendar puts on a library and how urgent an incident really is. BiblioLabTech already supports institutions remotely in Colombia, Peru, Paraguay and El Salvador under the same service standard.

What Koha support costs

Koha support is priced by service level, not by number of users or records. As a reference, BiblioLabTech's university projects place an annual support contract at USD 500 to 2,000. Three variables move the figure: the response time committed for critical incidents, the hours of coverage and the bank of hours included for configuration changes and functional help. An SLA with response in hours and extended coverage costs more than one with response in business days, so match the level to how critical your OPAC really is. Hosting, when the provider also runs the server, is a separate line; the full breakdown is in our guide to Koha implementation cost.

Questions to ask before you sign a Koha support contract

1. Does support include server administration, or only the Koha software?
2. How is an incident reported, and who receives it?
3. Does the provider apply version upgrades, or is that the institution's job?
4. Are backups verified periodically, or only scheduled?
5. In which language and during which hours does the support team respond?
6. What happens if the institution wants to change provider later? Because Koha is open source, the data and the system must remain fully portable.

One more check: be wary of anyone presenting themselves as the "official" Koha provider. The community's paid-support directory at koha-community.org states that any organization claiming to be an official Koha support provider is misrepresenting its relationship with the project.

Koha support from BiblioLabTech

BiblioLabTech provides annual Koha support for libraries in any country: incident response with response times agreed by severity, functional help for library staff, maintenance of the server and backups when we host the system, and planned upgrades tested in a staging environment before they reach production. It applies whether your library implemented Koha with us or with another provider. Libraries that implement Koha with BiblioLabTech also receive BiblioScan AI, our AI-assisted MARC21 cataloging tool, at no extra cost. The Escuela Colombiana de Ingeniería Julio Garavito runs its Koha catalog with BiblioScan AI on a dedicated server administered by our team; see the case study.

If your library already runs Koha and has no clear support today, that is exactly the gap we close. Review our Koha service or tell us about your instance: your Koha version, where it is hosted and what is not working.