About us
Libraries should be looking after students, not servers
Koha Solutions builds and runs library technology — the hosted catalog, the training that goes with it, and the websites around it.
Why we exist
Koha is excellent. Running it is somebody's job.
Almost every problem we are called about is not a problem with Koha.
Koha is used by thousands of libraries because it does what a library actually needs — cataloging, circulation, acquisitions, serials, holds, reports and a public catalog — and because nobody can take it away from you. That part works.
What does not work is the assumption underneath it: that every library has someone whose job is the server. Most do not. So the install finishes, the notices never send because nobody added the DNS records, the scheduled jobs were never checked, the person who set it up moves on, and two years later the catalog is running a version nobody supports. None of that is a software failure. It is an ownership failure.
We take that ownership. The server, the backups, the patches, the upgrades and the monitoring are ours; the catalog, the records and the decisions stay yours.
Our mission is to modernize libraries with secure, scalable, and intelligent technology solutions that improve accessibility, automation, and user experience.
What we build
One company, three products
Everything else we do — installation, migration, RFID, customization, support — is a service around the first of them, not a product of its own.
Koha Cloud
Hosted Koha, without the server room
A complete library management system on our infrastructure. Cataloging, circulation, acquisitions, serials, reports and a public catalog — running the day you sign up, with backups, updates and support handled for you.
Explore Koha CloudKoha Certificate
Learn Koha properly, on a live system
A structured certification course for librarians and LIS students. Every week is hands-on work on a real library system — not slides — with your assignments tracked automatically and a certificate at the end.
See the courseCustom Website Solutions
Sites and portals built around your institution
Institutional websites, department portals and integrations built to fit how your organisation actually works — designed, built and maintained by the same team that runs your library system.
Discuss a projectHow we work
Four things we will not trade away
Each of these costs us something, which is the only reason it is worth writing down.
We run what we sell
Koha Cloud is not a reseller arrangement. The platform is ours, the servers are ours, and the same team that builds it is the team that answers when something breaks. Nothing gets escalated to a vendor we do not control.
Set up, not shipped
A library system is not finished when it installs. Mail with its DNS records, notice templates, copy-cataloging targets, scheduled jobs and a tested backup are the difference between software that runs and a library that can open — so they are part of the work, not an upsell.
Built for any language, anywhere
Koha runs in roughly 20,000 libraries on every continent, and the problem we solve — nobody to run the server — is the same everywhere. Catalogs in non-Latin scripts and right-to-left languages are a supported case, not a special project.
Your data stays yours
Records export in MARC21 and CSV whenever you want them, and you keep your own copy of the backups. A catalog you cannot leave with is a catalog you do not really own — so leaving is a documented process rather than a negotiation.
What you can check
Claims worth making are claims you can verify
Every line below is either a published standard or something visible in a system we run.
MARC21, ISO 2709 and MARCXML
Import and export both ways, with matching rules and a staging step — the same formats every other library system speaks.
Z39.50 and SRU copy cataloging
Search remote catalogs and pull a full record in, rather than typing it. Configured with working targets before handover.
SIP2 for hardware you already own
Self-check units, RFID pads and gates connect over SIP2, so existing equipment is not a reason to stay where you are.
Koha's own schema and column names
Our data model follows Koha table for table and column for column, so records move across one-to-one rather than being approximated.
Backups you keep your own copy of
Automated, and yours to download without asking. A backup you cannot get at is not a backup.
Scheduled jobs with a readable run history
Fines, overdues and the message queue leave a record per library, so "why did this change?" has an answer that is not a shell login.
Two things we are careful never to claim: Koha Cloud is our own platform built on the same library workflows, not the Koha codebase itself; and we hold no endorsement or certification from the Koha community. Both are checkable, so both are worth stating plainly.
Who we work with
Institutions that would rather not run a server
College, university, school and special libraries — single-site and multi-branch, in any language or script.
Some come to us with no system at all, some with a catalog in spreadsheets, and some with a Koha install that has been running for years and needs someone to take it over. All three are ordinary starting points.
We do not name customers without written permission, so this page has no logo wall. If you would like to speak to a library running what you are considering, ask — we will ask them first.
Get a quote
Tell us what your library needs
A couple of sentences is enough to start. We reply by email with a quote and a realistic timeline — no call required first.