Ossus

Ossus is aiming at a real gap. Public and school libraries run on ILS platforms that were designed decades before anyone thought a phone camera could read a shelf, and the recurring work — annual inventory, vendor-by-vendor order splitting, grant deadlines — is exactly the kind of repetitive, rules-plus-judgment task that AI handles well today. The product strategy reflects that: rather than bolting a chat box onto a catalogue, Ossus sells named agents that each replace a documented chore. Inventory is the clearest example. Photographing up to 30 spines still on the shelf, in place, means staff do not have to pull and scan every item, and the same pass surfaces misplaced books. The vendor claims 80% time savings; even a partial realisation of that is material for a library that loses weeks a year to shelf reading. The Vendor Comparison Agent is the one with a hard dollar figure attached — 5-10% off book orders by weighing title price against MARC records and processing fees, which many libraries never model explicitly. The Grant Agent scans funding sources and drafts applications from collection and community data, which is the sort of writing-heavy work where library staff are chronically short of hours. The privacy design deserves credit for being specific rather than aspirational. Ossus states it reads catalogue metadata and never borrower records, does not train on or sell data, stores data in-region, and handles student records under applicable student privacy rules — with ISO 27001 certified, GDPR compliant, and SOC 2 in audit. For a director who has to get a system past an IT review, that documentation is the difference between a short conversation and a six-month one. The included resource manager is a quiet win: Chromebooks, tablets, and instruments get their own records, checkout history, and condition notes, and the vendor notes this often replaces a separate asset-management subscription. Migration, training, and support at no extra cost, with most switches done in one to three weeks, addresses the main reason libraries stay on software they dislike. Where the picture narrows: Ossus is built for physical collections. The vendor is direct that e-book and digital lending is not its job — libraries on Sora keep using Sora. That is a defensible scope decision, but it means Ossus is one piece of a library's stack rather than a single replacement. The company is also young and openly describes itself as a start-up answering support questions "almost 24/7," which cuts both ways: responsive, but a smaller organisation than the incumbents it is pitching against. And because pricing is only available by booking a meeting, you cannot model total cost of ownership from the website — you will need a scoped quote before you can compare it to a legacy renewal. If you run a tiny collection where manual inventory takes one afternoon a year, the agents have little to bite on. If you run a public or school library with real shelf counts, real book