Self-managed Koha hosting runs roughly USD 10–40 per month for a small library, 40–120 for a mid-size one, and 150–500+ for a large multi-branch institution. Managed hosting typically runs three to eight times those figures, because it includes labour rather than only infrastructure.
Indicative USD. Below is what drives each number, so you can judge whether a quote is reasonable. If you are still deciding whether Koha is the right system at all, start with what Koha is and what it does.
This article covers recurring cost. One-time implementation is separate — see Koha installation cost.
What you are actually paying for
- Compute — vCPU and RAM, the largest infrastructure line
- Storage — the database, uploaded files and covers
- Bandwidth — usually generous enough not to matter for a library
- Backup storage — separate from server storage, and routinely forgotten
- Monitoring — free at a basic level, paid when you want to be told before patrons notice
- Labour — only in managed plans, and it is the entire difference
That last line explains the gap between a USD 15 virtual server and a managed quote, and it is worth stating plainly: you are not being overcharged for the same server. You are buying somebody's time to keep it patched, upgraded, backed up and answered.
Self-managed VPS cost
A mid-size library on a mainstream provider: around USD 24–48/month for 4 vCPU and 8 GB RAM with 80–160 GB storage.
Add the lines people omit:
- Backup storage or snapshots — USD 2–10/month
- Monitoring, if paid — USD 0–15/month
- Domain — USD 10–20/year
- TLS certificates — free
Realistic all-in for a mid-size library: USD 30–70/month, plus your own staff time, which is the real cost and does not appear on any invoice.
Managed Koha hosting cost
Priced by library size and by what is included. A quote should state explicitly:
- Whether Koha application upgrades are included, or only OS patching
- Backup frequency, retention, and whether restores are tested
- Whether you can hold your own backup copy
- Support response time, and support hours
- Whether mail deliverability and notice templates are covered
- What happens if you leave, and how you get your data
Two managed quotes that look similar can differ enormously on those points. Compare the list, not the number.
Cost by library size
| Library | Self-managed /month | Managed /month | Self-managed /year |
|---|---|---|---|
| School, under 10k items | 10–25 | 60–150 | 120–300 |
| College, 20k–60k items | 25–60 | 150–400 | 300–720 |
| University, 100k–300k | 80–200 | 400–1,200 | 960–2,400 |
| Large / multi-branch | 200–500+ | 1,000–3,000+ | 2,400–6,000+ |
Self-managed figures exclude staff time entirely. If you cost even four hours a month of a technical salary, the two columns move much closer together than they first appear.
The recurring costs quotes leave out
- Koha upgrades — twice a year, and each needs testing
- Support hours — either a retainer, or a scramble when something breaks
- Restore testing — the only thing that turns a backup into insurance
- Retraining — every time staff turn over; see our hosting guide
The setup you pay for once — and then again at every upgrade
Mail configuration and deliverability records. Notice templates. Z39.50 targets. The backup job and its restore drill. TLS renewal and patching. Keeping the catalog crawlable.
Each is cheap in isolation and expensive as a habit, because every one has to be re-verified after a major upgrade. This is the line item that separates a hosting bill from a total cost of ownership.
Hosting cost versus total cost
Hosting is one line. Over three years the full picture also carries implementation, migration, training and support. A library that compares only monthly hosting figures will pick the cheapest option and discover the rest in year one — see the installation cost breakdown.
How to lower your hosting bill
- Right-size instead of over-provisioning. Most libraries buy more server than they use, once, at the start.
- Pay annually where a discount is offered.
- Archive old circulation history. It grows the database and the backup, and is rarely queried.
- Consolidate branches onto one instance rather than running several.
- Do not run a dedicated server per library if you are a group. This is the big one.
That last point deserves expanding, because it is where the real money is. Running one dedicated server per library is the expensive way to do it — every library pays for its own idle capacity, its own backup regime and its own maintenance. Shared, professionally-run infrastructure costs less per library and removes the sysadmin line from the budget entirely. That is the structural reason a hosted setup at a fixed annual cost comes in under a self-managed equivalent once staff time is counted honestly.
Figures reviewed August 2026. Indicative USD; cloud pricing changes.
Want a real figure? Tell us your collection size and branch count and we will quote hosting with everything included — upgrades, backups you keep your own copy of, and someone to answer when you write.