Compare
Bookleaf vs. cloud library systems
Hosted subscription systems do several things Bookleaf genuinely cannot. They also make two assumptions — reliable internet and permanent budget — that a lot of schools cannot honestly make.
| Capability | Bookleaf | A cloud library system |
|---|---|---|
| Cost structure | ₱1,499 one-time software license, for the institution. | A subscription, renewed every year, usually scaled by size. |
| When the internet is down | Everything works. It never needed the connection. | The library cannot circulate. Checkout goes back to paper until it returns. |
| When the budget is not renewed | Nothing happens. The software keeps running. | Access ends. Your catalog is behind a login you no longer have. |
| Where patron data lives | A file on your own computer, in your building. | The vendor's servers, often in another country. |
| Access from home | No. Same Wi-Fi as the library only. | Yes. This is the genuine advantage. |
| Automatic overdue notices | In-app and on the dashboard. No SMS or email. | Email and often SMS, sent automatically. |
| Setup | Run an installer. | Procurement, contract, onboarding, data migration by the vendor. |
| Upgrades | You install them, when you choose to. | Done for you, whether or not you wanted the change. |
| Multiple branches or campuses | No. | Yes, usually well. |
| If the vendor shuts down | Your installation is unaffected. It does not phone anyone. | A migration under time pressure, at best. |
The dependency
A library that stops working when the line drops
In a school with a solid connection, this is a footnote. In a school where the internet drops for an afternoon most weeks — or for a week after a typhoon — it is the whole decision.
A cloud system that is unreachable does not degrade gracefully. Circulation stops. The librarian writes borrowings on paper and re-keys them later, which is both the old system and the new one at the same time.
Bookleaf runs on the librarian's own computer, so an outage outside the building is not an event inside it. This is the single reason the product is shaped the way it is.
The other dependency
The renewal that has to be won every year
A subscription asks your library to win a budget argument every single year, forever. Most years it will. The year it does not, the catalog does not become read-only — it becomes inaccessible, along with the borrowing history behind it.
Ask any prospective vendor one question before signing: if we stop paying, what exactly can we take with us, in what format, and how? A good vendor answers immediately. The answer should be MARC records you can load somewhere else.
For the same question about us
Bookleaf's answer: your catalog is a file on your computer that you already have, and the app exports MARCXML that Koha and other systems import. There is no step where you have to ask our permission, and nothing stops working if you stop talking to us.
The Koha comparison covers what moving up to a bigger system looks like.
Try it on your own catalog this week.
Download Bookleaf and run the full system free for 7 days — every feature, no card, no account needed. If it fits, the software license is ₱1,499, one time.