Koha System

Koha Hosting Options — Self-Hosted, Cloud, and AWS

Overview of all options for hosting Koha library software. Covers self-hosted Linux, managed cloud hosting, and AWS deployment via KohaSupport — with pros, cons, and cost considerations for each.

May 08, 2026 5 min read

Koha is open-source software — but it needs somewhere to run. This guide covers every hosting option available to libraries, with honest pros and cons for each.

Your Hosting Options at a Glance

Option	Technical Skill Needed	Setup Time	Best For
Self-hosted Linux	High	Days–Weeks	IT-capable libraries
Third-party managed hosting	None	Days	Libraries wanting full vendor management
KohaSupport on AWS	None	Minutes	Libraries wanting cloud + data control
Consortium-hosted	None	Weeks–Months	Libraries in eligible consortia

Self-Hosted on Your Own Linux Server

You install and run Koha on a server you control — either physical hardware on-site or a virtual private server (VPS) in the cloud.

What it involves:

Installing Ubuntu or Debian Linux
Adding the Koha community repository and installing packages
Configuring Apache, MySQL/MariaDB, and Plack
Setting up SSL, backups, and monitoring
Managing all upgrades yourself (Koha releases quarterly)

Pros:

Full control over every aspect of the system
Lowest recurring cost (you pay only for infrastructure)
Data stays on servers you directly manage

Cons:

Requires Linux server administration knowledge
All maintenance, security patching, and upgrades are your responsibility
No support SLA unless you purchase a support contract separately
Downtime risk if your IT team is stretched

When it makes sense: Libraries with a capable systems librarian or IT department that wants maximum control and minimum recurring cost.

See: How to Install Koha on Ubuntu →

Third-Party Managed Hosting

Several companies offer managed Koha hosting where they run the servers and handle upgrades, backups, and monitoring on your behalf.

What it involves:

You sign up with a hosting provider
They provision and configure Koha for you
Ongoing maintenance is their responsibility
You access Koha via your browser

Pros:

No server knowledge required
Support SLA included
Upgrades handled for you

Cons:

Data lives on the provider’s servers (not your own infrastructure)
Provider lock-in — migrating away requires data export
Pricing varies widely; some providers are expensive
Less transparency into infrastructure

Notable providers: ByWater Solutions, Equinox, PTFS, Thirtybees, and many regional providers worldwide.

KohaSupport on AWS

KohaSupport deploys Koha on your own AWS account using pre-built AMIs. You get the simplicity of managed hosting with the data control of self-hosting.

What makes this different:

Koha runs in your AWS account — your data, your infrastructure
No Linux knowledge required — launches from AWS Marketplace in minutes
Koha Theme Builder included for OPAC customization
Automated daily backups to your own S3 bucket
You can terminate KohaSupport’s subscription and keep running Koha on your AWS account

Plans:

Plan	Records	Commercial model	Best For
Free	Up to 1,000	Evaluation listing on AWS Marketplace	Evaluation, testing, staff training
Standard	Unlimited	Public subscription pricing on AWS Marketplace	Most live libraries
Enterprise	Unlimited	Quote-based planning for larger environments	High availability, multi-AZ, auto-scaling

Compare full plan details →

What AWS costs separately: KohaSupport’s plans cover the software layer. AWS infrastructure (EC2 instance, storage, bandwidth) is billed directly by AWS to your account, and the exact amount depends on the AWS services and usage profile you choose.

Pros:

Simple setup — 5 minutes from AWS Marketplace to running Koha
Full data ownership (your AWS account)
Koha Theme Builder included
No vendor lock-in — you own the infrastructure

Cons:

Requires an AWS account
AWS infrastructure billed separately
Not a fully managed service — you own the AWS account and its costs

Consortium-Hosted

Many regional library consortia and state library agencies offer Koha hosting to member libraries, sometimes at no cost or reduced cost.

Examples: Some US state library agencies, regional library cooperatives (NELINET, Lyrasis, etc.), and international library networks provide consortium Koha instances.

Pros:

Often free or subsidized
Shared resource, community governance
May include a shared union catalog

Cons:

Availability varies by region
Less control over upgrade timing
Shared infrastructure — performance may be shared
Leaving the consortium may require data migration

How to find options: Check with your state library agency, regional library consortium, or national library association.

Choosing the Right Option

Your Situation	Recommended Path
Evaluating Koha for the first time	KohaSupport Free on AWS
Small-to-medium library, no IT staff	KohaSupport Standard on AWS
Library with capable IT department	Self-hosted Linux VPS
Large library needing high availability	KohaSupport Enterprise
Library in eligible consortium	Consortium hosting (check your region)
Need full vendor management + SLA	Third-party managed hosting provider