Free Library Management for K-12 Schools

The Community Edition is genuinely free under LGPLv3 — you can download the source, install it on your own server, and run it forever without paying us. There is no user cap, no title cap, no time-limited trial. What's NOT free: the advanced analytics module, single sign-on with Google Workspace or Microsoft 365, and white-glove support contracts. Those are paid add-ons in our Enterprise edition. For a single-school K-12 deployment with a librarian who's comfortable with basic IT (or a friendly district tech), the Community Edition alone covers cataloging, circulation, OPAC, fines, multi-branch, and basic reports — and that's the package most small schools actually need.

Honest number: $10-30/month for a small VPS that runs the whole stack for a single K-12 school. DigitalOcean's $12 droplet, Hetzner's CX22 at about €5, Linode's $12 Nanode — any of those handles a few thousand students and a few thousand titles without breaking a sweat. If your district already has on-prem servers, the cost is just the storage and a few hours of IT time. The two costs you absolutely should not skip: nightly backups (typically $2-5/month on top of the VPS) and a domain name (~$15/year). Anyone claiming a self-hosted library system costs zero dollars is hand-waving the hosting bill — we'd rather you walk in with a realistic budget.

Honestly, sometimes yes. If you're a single-classroom Montessori with 60 kids and a teacher who manages the bookshelf, a spreadsheet and a $0 LibraryThing TinyCat account might serve you better than a self-hosted ILS. Where the Community Edition starts to pay off: when you have a dedicated librarian (even part-time) who is tired of the spreadsheet, when you have over ~1,000 active titles, when you have multiple lending points (main library + classroom libraries), or when you're trying to get off an expiring trial of a proprietary system. Under 100 students with a single shelf — try a free hosted tool first.

Follett Destiny is the dominant K-12 ILS in the US — it's polished, deeply integrated with major US textbook vendors, and has district-wide federation that's been hardened over twenty years. It also costs roughly $1,200-$3,500/year per school depending on edition and district size, plus per-school setup. The Community Edition trades that vendor relationship for self-reliance: you get MARC21, barcode circulation, OPAC, multi-branch, and basic reports for the cost of a VPS — but you do not get Follett's Lightbox content library, their built-in eBook platform contracts, or their phone-support help desk. If your district can afford Destiny and uses Follett's content ecosystem, stay there. If you can't afford Destiny and a $25,000 ILS contract is permanently off the table, the Community Edition is the most honest alternative.

Two paths. If you have a spreadsheet with title, author, ISBN, and barcode, we have an ISBN-bulk-import workflow: paste the ISBN column, the platform pulls bibliographic records from open MARC sources (Library of Congress, OpenLibrary), and you confirm matches. A 2,000-title collection takes a librarian roughly two afternoons of clicking through matches, mostly because covers and editions need eyeballing. If you're on paper-only, the realistic migration is a one-time barcoding sprint: print Code 128 barcode labels from the platform, walk the shelves with a student helper, scan each book, and let the platform's ISBN lookup do the cataloging in real time. Plan a week of evenings, not a weekend.

Three honest answers, in increasing order of cost. (1) The community forum and documentation are free and active — most issues a single-school librarian hits have already been answered. (2) Your district IT department can usually handle the OS-level stuff (Ubuntu updates, backups, certificate renewals) in less than two hours a month once the system is running. (3) If neither of those works, we sell a paid support contract — but we will tell you up front it's priced for districts, not single schools. The realistic small-school setup is: install on a managed VPS with automatic OS patches, set up automated nightly backups to S3 or Backblaze, and budget two hours a quarter for your IT person to log in and check logs. That's it.