Libki

Libki is a workstation-access system for organizations that lend networked computers to the public, especially libraries and school labs. It is a strong fit when staff need reservation and patron controls alongside timed sessions; it is less suitable for teams that do not want to host and secure a server.

Overview

A web interface lets administrators manage users and session time, message or ban users, and check which client computers are in use or available. That central view is useful when staff oversee multiple shared workstations. The client-based setup and self-hosted server, however, mean the organization must take responsibility for deployment and upkeep.

Key features

Libki can offer access on a first-come-first-served basis, by reservation, or through both approaches. That gives libraries and labs room to match access to local demand. Users can see their remaining session time and log off early; at session end, the client can log off the operating system or reboot. The latter options help control how shared machines are left between sessions, but require the client to be installed on each workstation.

SIP2 and LDAP single sign-on support connection to identity systems. With SIP2, access can be restricted using patron status flags, fees, age groups, and other configured fields. The manual also describes SIP2 configuration for Koha and Evergreen hold notifications. Those library-oriented controls make Libki more relevant to patron computing than a basic kiosk lock-down tool. It can also provide print management for controlled clients or accept print jobs through file uploads to the server.

Administrators can configure history anonymization and retention, as well as automatic deletion of inactive users. This allows a site to set its own data lifecycle, but empty retention settings keep data indefinitely, so administrators need to configure them deliberately.

Pricing

Libki is free open-source software. Its Libki plan costs nothing and includes the ability to download, install, and use the system freely. There is no free trial because there is no paid plan to trial. The absence of a software fee is a clear advantage for public institutions, but it does not remove the work of running the server and client deployment.

The maker says support or development services may be purchased, but gives no price; those services therefore have custom pricing. The maker directs users to mailing lists, documentation, and GitHub issue trackers for community support.

Platforms

The server is self-hosted, with Debian Linux, Ubuntu Server, or Docker recommended in the manual. Docker still requires a separate database server. The client runs on Windows and Linux: Windows has an installer, while other operating systems require compiling from source. The web interface provides the administrative view, but it does not make Libki a hosted service.

Security needs attention during deployment. The server has no native SSL support, and the manual recommends a reverse proxy that supports SSL termination. Organizations without the capacity to configure and maintain that layer should look for a managed alternative.

Who it's for

Libki suits libraries and school computer laboratories that need to manage public access, session time, and reservations, particularly where SIP2, LDAP, or patron-based restrictions matter. It is a weaker choice for a small team seeking a turnkey hosted kiosk product or a client that installs without technical administration.

Pros and cons

Pros

• No software charge: The open-source plan is free to download, install, and use.
• Flexible access: Sites can combine reservations with first-come-first-served sessions.
• Library controls: SIP2 can apply patron-related access rules, and Koha and Evergreen hold notifications are covered in the manual.
• Session cleanup options: The client can log off the operating system or reboot when time expires.

Cons

• Self-hosting is required: The organization must run the server and manage client installations.
• Security configuration is external: SSL requires a reverse proxy, adding deployment work.
• Linux client setup is less direct: Operating systems other than Windows require compiling the client from source.
• Retention needs deliberate setup: Leaving retention settings empty keeps data indefinitely.

Alternatives

Kiosk Management Software is the broader category for comparing tools in this area. Consider Kiosk for an open-source PDF reader rather than Libki's public-workstation management. SureAsset is a better fit for asset lifecycle management, hardware and software license tracking, and API access or automation. KioskCore offers a free tier capped at two devices, with seven-day metric history, on-demand screen capture retained for 24 hours, three email alerts per device per day, and community support.

OpenKiosk is another free option for Linux, macOS, and Windows. KioskSide is a paid alternative for Android, Linux, web, and Windows. Atashi Kiosk Management Platform uses custom deployment pricing quoted after scoping, with scope depending on terminal and site count, estate ownership, alert rules, integrations, hosting, and support. Kiosker is a freemium option for Android and iOS, with a seven-day trial for its subscription versions: $6.99 a month or $24.99 a year. Moki is a paid Android, iOS, API, and web option with a free trial; its MDM plan is priced per device per month, caps API calls at 500 per hour per account, and includes up to 10 users, with additional users billed $15 per user per month.

Verdict

Choose Libki if your library or school lab needs patron-aware access, reservations, and session controls and can operate its own server and workstations. Its strongest case is the combination of free use and library-oriented controls. Look elsewhere if self-hosting, client compilation, or arranging SSL through a reverse proxy is beyond your team's capacity.