Skip to main content
OpenEduCat logo
solutionPage.moduleBadge

Open Source Library Management for K-12 Schools

An LGPLv3 catalog, circulation, and OPAC stack for librarians and IT directors who want source-code transparency, data sovereignty, and the freedom to host on their own infrastructure. MARC21 in, Z39.50 out, no vendor lock-in.

Open source library management for K-12 schools is library software whose source code is published under a recognized open-source license (LGPLv3, GPL, or AGPL), letting school districts read, modify, redistribute, and self-host the catalog, circulation, and OPAC modules on their own servers. Unlike free-as-in-price proprietary tools, open-source library systems give schools the legal right to inspect every line of code, audit how student circulation data is handled, and adapt the system to local policies. OpenEduCat ships its library module under LGPLv3 with MARC21 and Dublin Core support, Z39.50 and SIP2 interop, and the full source on GitHub.

LGPLv3License (read, modify, self-host, redistribute forever)$10-30/moTypical VPS hosting cost for a single-school or district library4,300+Institutions running the OpenEduCat library module worldwide

solutionPage.featuresTitle

solutionPage.featuresSubtitle

LGPLv3 source-code transparency

Every line of the cataloging, circulation, OPAC, and reservation engine is published on GitHub under LGPLv3. Your IT team or a contracted developer can read the access-log code, the patron-data handlers, the search index, and the API layer before installing. For districts answering to school-board IT audits or state data-privacy reviews, that auditability is what separates open source from free-but-closed alternatives.

MARC21 and Dublin Core open-standard catalog

Bibliographic records use MARC21 (Library of Congress standard) and Dublin Core metadata, so your catalog is portable. Export to a flat MARC file, walk away with your data, and import it into Koha, Evergreen, or any future system without paying a vendor for a data extract. No proprietary record format, no exit fees.

Self-hostable on any cloud (BYOC)

Run it on AWS, Azure, GCP, Hetzner, DigitalOcean, OVH, or a closet server in the district office. Typical hosting cost for a K-12 library serving 200 to 5,000 students is $10 to $30 per month on a small VPS. No mandatory SaaS, no per-patron pricing, no usage caps. Your circulation data lives on infrastructure you control.

Audit-friendly access and circulation logs

Every check-out, check-in, fine, hold, and patron record edit is timestamped with the staff user who made the change. Logs are queryable and exportable for FERPA inquiries, parent records requests, and state library-board audits. The schema is documented so a privacy officer can prove exactly what student data is captured and for how long.

School-specific customization (fields, reports, OPAC theme)

Because you have the source, you can add custom MARC fields for reading-level metadata (Lexile, AR, Fountas and Pinnell), build reports tuned to your state's library-program standards, brand the public OPAC in school colors, and add Spanish or other language OPAC translations. Customizations live in a child module so core upgrades do not overwrite them.

Interop with Koha, Follett Destiny, and other ILS via Z39.50 + SIP2

Z39.50 federated search lets staff pull MARC records from the Library of Congress, Koha co-op catalogs, or a sister district's Follett Destiny when cataloging new acquisitions. SIP2 integration connects to self-checkout kiosks, RFID gates, and consortium ILL workflows. Standard protocols, no proprietary bridges.

LGPLv3
License (read, modify, self-host, redistribute forever)
$10-30/mo
Typical VPS hosting cost for a single-school or district library
4,300+
Institutions running the OpenEduCat library module worldwide
MARC21 + Z39.50
Open-standard cataloging and federated search out of the box

solutionPage.faqTitle

solutionPage.faqSubtitle

What is the difference between open-source and free library management software?

Open-source means the source code is published under a recognized license (LGPLv3, GPL, AGPL) that legally guarantees four freedoms: read the code, modify it, run it, and redistribute it. Free can mean any of those things or none of them. Plenty of free-as-in-price K-12 library tools are closed-source SaaS with a $0 tier and proprietary code. If your reason for choosing open source is data sovereignty, audit transparency, or customization rights, those are only guaranteed by an OSI-approved license, not by a $0 price tag. OpenEduCat's library module is LGPLv3, which the Free Software Foundation and OSI both recognize.

Why do K-12 school districts specifically choose open-source library systems?

Four reasons come up repeatedly in district RFPs and library-tech-committee minutes. First, data sovereignty: student circulation records are FERPA-protected, and many districts want that data on their own servers rather than a vendor's cloud. Second, FERPA and state privacy compliance: open source lets the district's privacy officer inspect exactly what fields are logged and how long they are retained, which the American Library Association (ALA) Code of Ethics on patron privacy explicitly encourages. Third, customization for state library-program standards (Texas TLA, California CSLA, AASL national standards) without paying vendor change-orders. Fourth, exit insurance: if the vendor relationship ends, the district still has the code and the data in open formats.

How does OpenEduCat compare to Koha, the most established open-source library system?

Koha (koha-community.org) is the gold standard for standalone open-source library management and has 20+ years of cataloging-depth, advanced acquisitions, and serials handling. If your district is library-only and you want the deepest pure-ILS feature set, Koha is the safer pick. OpenEduCat is different: it ships the library module inside a full school ERP that also handles admissions, attendance, exams, fees, and HR. K-12 districts that want a single source of truth (patron records auto-sync from enrollment, fines flow into the fees ledger, lost-book holds appear on the parent portal) pick OpenEduCat. Districts that already run a separate SIS and only need an ILS often pick Koha. Both are LGPL/GPL, both export MARC21, and both speak Z39.50 and SIP2.

How does it compare to Follett Destiny, the proprietary K-12 standard?

Follett Destiny is the incumbent in US K-12 libraries with strong vendor support, large reading-program integrations (Accelerated Reader, Lexile), and tight integrations with Follett Titlewave for acquisitions. The trade-offs: per-school annual licensing, closed source code, vendor-controlled hosting, and limited customization without professional services. OpenEduCat is LGPLv3, zero license fees, self-hostable, and fully customizable, but you take on hosting and integration work yourself or pay a partner. Districts that prioritize vendor hand-holding and out-of-the-box AR/Lexile integration often stay on Destiny. Districts that prioritize data ownership, license-cost elimination across multiple campuses, and source-code control move to open source.

Can we migrate from Follett Destiny or another proprietary ILS without losing our catalog?

Yes, because MARC21 is the universal export format. Follett Destiny, Alexandria, Mandarin, and most other K-12 ILS systems can export a full MARC bibliographic file plus separate patron and circulation-history files in standard formats. OpenEduCat imports MARC21 natively, and patron records map to its student/contact model via CSV. A typical district migration runs four to eight weeks: export from incumbent, clean MARC records, import to OpenEduCat staging, reconcile circulation status, train staff, cut over. The open-source community has documented migration guides for Destiny-to-Koha and Destiny-to-Evergreen that apply almost identically to OpenEduCat.

What support is available if our IT team is not Python or Linux fluent?

Three tiers. (1) DIY: GitHub issues, community forum, OpenEduCat docs, plus the wider Odoo ecosystem since OpenEduCat is built on Odoo. Free, but you own the outcome. (2) Implementation partners: regional Odoo/OpenEduCat partner agencies offer paid hosting, setup, migration, training, and SLA-backed support. Pricing varies, but typically replaces what districts already pay incumbent ILS vendors. (3) OpenEduCat Enterprise: direct paid support from the OpenEduCat team with guaranteed response times, custom development, and managed hosting. The honest take: if your district has zero Linux capacity and zero budget for a partner, a proprietary SaaS may be the right call. Open source is most valuable when you have either in-house tech capacity or partner budget.

Bereit, Ihre Institution zu transformieren?

Erfahren Sie, wie OpenEduCat Zeit freisetzt, damit jeder Studierende die Aufmerksamkeit erhält, die er verdient.

15 Tage kostenlos testen. Keine Kreditkarte erforderlich.