FAQ
Frequently asked questions.
Straight answers to the questions library directors, IT teams, and procurement ask most — about integration, tags, hosting, deployment, and licensing.
Does AtēnaOs work with our existing library system?
Yes. AtēnaOs integrates with your library system. Your catalog, patron records, and loans stay where they are — there is no data migration and no parallel records. AtēnaOs adds self-service, staff tools, and RFID security on top of the system you already run.
Can we keep the RFID tags already on our books?
AtēnaOs uses standard RFID tags that carry the item's identifier — the same value as its barcode and catalog record. If your existing tags follow common library standards and can be encoded with that identifier, they can be used; tags encoded differently are re-encoded with Tag Studio, which also lets you produce new labels in-house. The right approach for your collection is assessed during deployment planning.
What happens if the network goes down?
Devices are designed to recover gracefully from network interruptions, and every device reports its status centrally — outages are visible in the Admin console rather than discovered by patrons. Live operations such as loans depend on a connection to your library system, as with any integrated circulation setup.
Is AtēnaOs hosted in the cloud or on-premises?
AtēnaOs is hosted in the EU and managed centrally — updates reach every device automatically, with no software rollouts to individual machines. Your catalog and patron data remain in your library system; AtēnaOs holds only the operational data it needs.
Who installs the system?
AtēnaOs is delivered through local implementation partners, or directly by us where no partner is available. Delivery covers installation, item tagging, staff training, and go-live support.
Can it serve multiple branches or a consortium?
Yes. AtēnaOs is multi-tenant by design: institutions and branches are isolated from each other, and every record, permission, and gate authorization is scoped to its organization and branch. One platform can serve a single-site library, a multi-branch system, or several institutions side by side.
Which languages does the interface support?
As many as your community needs. Interface languages are managed centrally and switch instantly on screen — on the kiosk, at the desk, everywhere — so a reader who arrived from another country can use the library in their own language from day one. Adding a new language is a central change; the devices themselves are never touched.
What patron data does AtēnaOs store?
As little as possible. Patron records stay in your library system; AtēnaOs minimizes the data it handles and personal identifiers never appear in URLs. Staff access is per-operator with a PIN and bound to a specific device, and every administrative change is recorded in an audit log. More detail is on the Security & data page.
How is AtēnaOs priced?
AtēnaOs is licensed annually per institution. Because every library differs in size, branches, and module selection, we prepare an individual quote — contact us and we will put one together for your setup.
How long does deployment take?
It depends mainly on the size of the collection to tag and the number of devices and branches. Deployment follows a defined sequence — integration, tagging, installation, training, go-live — described on the Deployment page. A concrete timeline is part of every quote.
What hardware do we need?
Hardware is specified in consultation with your implementation partner. The partner assesses your spaces and workflows and delivers equipment that is proven to work with AtēnaOs — self-service kiosks, staff-desk readers, security gates, mobile terminals for inventory, label printers for tagging, and signage displays for announcements. Suitable equipment you already own can often stay in service; the assessment confirms what fits.
How do we get a demo?
Request a demonstration through our contact page. We will connect you with the nearest implementation partner for an on-site demo, or demonstrate the platform ourselves — remotely or with a working setup in your library — where no partner is available.