Koha vs Follett Destiny: Open Source vs School Library ILS

Follett Destiny is the dominant library automation system in K-12 schools across North America. Koha on AWS Cloud, deployed and managed via KohaSupport, is a compelling open-source alternative with flexible deployment, broad customization, and quick launch from AWS Marketplace. This comparison reflects what KohaSupport’s Koha actually delivers — not vanilla self-hosted Koha.

Quick Comparison

Where Destiny Has an Edge

School-specific workflows: Destiny is purpose-built for K-12 libraries. Features like textbook tracking (Destiny Resource Manager), student ID system integration, and Chromebook compatibility are built-in and require no additional configuration.

Ease of deployment: Follett handles setup, configuration, and training. For schools without a dedicated systems librarian, the all-in-one vendor model reduces burden on school IT.

North American K-12 ecosystem: Destiny integrates natively with common school infrastructure — Google Workspace, Clever, LDAP/Active Directory, most barcode systems, and Follett’s own content catalog.

District-level reporting: Multi-school reporting across a district is Destiny’s native use case.

Where Koha Has an Edge

Different district pricing structure: Destiny pricing is typically per-school, per-year. Koha deployments are usually scoped around the environment, support expectations, and implementation needs rather than a per-school vendor subscription.

No vendor lock-in: When a Destiny subscription lapses, access to the system and data can be restricted. Koha data is always portable — export your MARC records and patron CSV anytime.

Scalability: Koha handles libraries from 500 items (small school) to millions of records (large university) on the same platform. No feature tiers based on school size.

Full customization: School library workflows vary enormously. Koha’s open source nature allows custom reports, integrations, and workflow modifications that Destiny’s closed platform cannot accommodate.

International use: Outside North America, Destiny has limited presence. Koha is deployed in school libraries across every continent and supports multiple languages, character sets, and cataloging standards.

Cost Considerations for Schools

Destiny pricing varies by school size and contract type — contact Follett for current quotes.

For Koha via KohaSupport on AWS:

• Subscription and support scope: Depends on the KohaSupport plan and any implementation help required
• Setup: 5 minutes from AWS Marketplace — no Linux expertise, no IT involvement required
• Infrastructure: Runs in your own AWS account; you control costs, region, and data residency
• Training: Available from KohaSupport and community resources

For a single school or small district, compare the full implementation, subscription, support, and AWS costs against Destiny’s subscription model. For large districts where Destiny is already deeply embedded in infrastructure (SSO, Google, district reporting), the switching effort may outweigh the operational benefits of changing platforms.

See the full framework: Total Cost of Ownership for a Library ILS

When to Choose Koha for Your School

✅ School is outside North America
✅ District wants to eliminate per-school subscription fees
✅ Need full data ownership and export rights
✅ School library is part of a larger public or academic library that already uses Koha
✅ District wants cloud deployment without IT overhead — KohaSupport on AWS handles all infrastructure
✅ School needs customization beyond Destiny’s configuration options

When to Keep/Choose Destiny

✅ Already deeply integrated with Follett’s textbook management
✅ District relies on Google Workspace or Clever SSO that’s already configured with Destiny
✅ No IT resources for any self-managed component
✅ District-level reporting across many schools is a primary requirement
✅ Comfort with Follett’s support model is important to stakeholders

Koha via KohaSupport — As Easy to Deploy as SaaS

School libraries often choose Destiny because it “just works” — no server setup, no IT department involvement. KohaSupport gives you that same simplicity with Koha:

For a district with multiple schools, pricing should be scoped against the number of schools, integrations, support expectations, and AWS architecture rather than assumed from a per-school licensing model.

Pricing combines the KohaSupport subscription with your own AWS infrastructure costs — giving you full, granular control to right-size and optimize your infrastructure spend per school or district. See plans and pricing →

Want to evaluate Koha for your school library? Start free on AWS → — no installation required, running in minutes.

Related:

• Koha for Small Libraries
• Total Cost of Ownership for a Library ILS
• Popular Library Systems