EVERYTHING XIAOMI
Get listed

OpenKiosk

OpenKiosk is open-source software for turning a machine into a remotely managed public browser terminal.

Place
#7 of 20
Score
6.6
OpenKiosk's website

What OpenKiosk is

OpenKiosk is open-source software for turning a machine into a remotely managed public browser terminal. The maker describes it as a system-integrated standalone browser based on Mozilla Firefox, with controls intended to limit public users to web browsing. Administrators can register devices with a token and manage settings through a web interface; the token is removed after registration, so a backup should be saved. Settings cover fullscreen mode, toolbar and URL-bar visibility, an on-screen keyboard, session timers, and whether cache, history, cookies, or bookmarks persist. URL allowlists and blocklists are available, with an optional strict mode that checks page resources and may disrupt pages if required resources are omitted. Current beta installation instructions require Debian 13 on x86_64 or aarch64 hardware and a system user named openkiosk; Raspberry Pi 5 instructions are included. The software is labeled Beta, is free under the Mozilla Public License, and is self-hosted. Documentation also labels downloads and uploads insecure when enabled, with uploads allowing pages access to the terminal filesystem.

Good

  • Remote settings can be managed through a web interface.
  • Supports URL allowlists and blocklists.
  • Administrators can control session timers and persistence.
  • Includes an on-screen keyboard setting.

Watch out

  • Current beta installation requires Debian 13.
  • Strict URL filtering may disrupt pages.
  • Downloads and uploads are labeled insecure when enabled.
  • The software is labeled Beta.

Who it suits

OpenKiosk suits organizations operating public browser terminals that need device management, URL controls, and session settings. Current beta installation is aimed at Debian 13 on x86_64 or aarch64 hardware.

Verdict

OpenKiosk provides remote management and configurable kiosk controls for public browsing. Its Debian 13 beta requirements and documented security cautions should be considered before deployment.

Plans and prices

From OpenKiosk's own pricing page, checked 8 Oct 2026.

All about pricing
PlanPriceWhat it gives you
OpenKioskFreeOpen source under MPL; donations accepted

The facts

Each one read from OpenKiosk's own pages, with the date it was checked.

What it does

Beta status and support
The maker labels the product Beta and asks users to test it and email bugs or issues.checked 8 Oct 2026
Content filtering
URL filtering supports whitelist and blacklist modes; strict mode checks URLs for resources within a page and the documentation says it may break pages when rules omit resources.checked 8 Oct 2026
Current beta
The maker’s current homepage describes OpenKiosk as a beta that turns a machine into a secure public browser.checked 8 Oct 2026
Current installation requirement
The current beta documentation requires Debian 13 on x86_64 or aarch64 hardware and says other Linux distributions are planned for future support.checked 8 Oct 2026
Current release
The documentation lists version 151.0.4 Beta as the latest release.checked 8 Oct 2026
Custom branding
A custom boot screen can use custom.svg and splash.png files placed in /etc as root.checked 8 Oct 2026
Deployment history
The maker says OpenKiosk has been deployed since 2005 in museums, schools, universities, libraries, hospitals, airports, hotels, governments, and businesses.checked 8 Oct 2026
Legacy desktop downloads
A separate download page lists Windows, macOS, and Linux packages for release 115.20.0 dated 2025-02-16.checked 8 Oct 2026
License
The maker says the software is open source and released under the Mozilla Public License.checked 8 Oct 2026
License and deployment
The software is open source under the MPL and the maker says it has been deployed since 2005 in public venues and businesses.checked 8 Oct 2026
Purpose
OpenKiosk is a remotely configurable secure public browser terminal.checked 8 Oct 2026
Remote management
A token can register devices for management through a web interface, where settings for one or all listed devices can be accessed.checked 8 Oct 2026
Security controls
Settings can disable local terminal access, enable a clean browser profile at startup, and restrict downloads and file uploads, which the maker labels insecure when enabled.checked 8 Oct 2026
Security-related limits
The settings documentation labels downloads and file uploads as insecure options, with uploads allowing web pages access to the terminal filesystem.checked 8 Oct 2026
Session controls
Administrators can set a session timer, show an ending countdown, and control whether cache, history, and cookies persist across sessions.checked 8 Oct 2026
Support contact
The contact page lists [email protected] for inquiries and [email protected] for bug reports.checked 8 Oct 2026
Supported hardware
The documentation specifies x86_64 and aarch64 devices and includes installation instructions for Raspberry Pi 5.checked 8 Oct 2026
System integration
The maker describes the current version as a system-integrated standalone public browser, with system-level controls intended to restrict public users to web browsing.checked 8 Oct 2026
System requirement
The current installation instructions require Debian 13 (trixie) and an existing system user named openkiosk.checked 8 Oct 2026
Text to speech
The installer offers an optional 555M PiperTTS package for website narration, with shipped languages da, de, en-US, es-ES, fr, and it.checked 8 Oct 2026
Token handling
After a device successfully registers for remote management, its token is automatically removed from the device; the maker instructs users to save a backup token for managing devices.checked 8 Oct 2026
Touchscreen and accessibility
Settings include an on-screen keyboard, and the documentation describes optional Piper text-to-speech narration with Danish, German, US English, Spanish, French, and Italian.checked 8 Oct 2026

Where it runs

Browser basis
The maker describes OpenKiosk as a web browser based on Mozilla Firefox, designed for public terminals.checked 8 Oct 2026
Kiosk controls
Settings include fullscreen mode, toolbar and URL bar visibility, an on-screen keyboard, and options to retain bookmarks across sessions.checked 8 Oct 2026
The full review of OpenKiosk

OpenKiosk is a free, open-source browser terminal for turning shared machines into managed public browsing stations. It is best suited to organizations prepared to administer Linux devices and tune their browsing and session rules. Its control set is substantial for a no-cost tool, but the current beta’s Debian 13 requirement sharply limits where it fits.

Overview

Built on Mozilla Firefox, OpenKiosk runs as a system-integrated standalone browser, with controls intended to keep public users within web browsing rather than local terminal access. The maker says it has been deployed in public venues and businesses since 2005, including libraries, schools, museums, hospitals, airports, hotels, and government settings. That breadth of use is encouraging, but it does not remove the need to account for the current beta status: the maker asks users to test the software and send bug reports.

OpenKiosk is self-hosted and open source under the Mozilla Public License. Its current release is 151.0.4 Beta, and current installation instructions require Debian 13 (trixie) plus an existing system user named openkiosk. The combination favors teams with Linux administration capacity, not organizations seeking a broadly compatible desktop installer for the latest release.

Key features

Remote management lets administrators register devices with a token, then reach settings for an individual device or all listed devices through a web interface. A successful registration removes the token from the device, so administrators need to preserve a backup token for device management. That process supports centralized configuration, but token handling deserves care during setup.

Kiosk settings cover fullscreen display, toolbar and URL-bar visibility, and an on-screen keyboard. Administrators can also configure session timers and an ending countdown, choose whether bookmarks survive sessions, and determine whether cache, history, and cookies persist. These controls let a venue shape the browsing experience and clean up user data between sessions without treating every public terminal as an unrestricted desktop.

URL rules can allow or block sites. Strict filtering also checks resources loaded within a page, which can tighten restrictions but may break pages when rules omit required resources. The software can disable local terminal access and start with a clean browser profile. Downloads and uploads are options the maker labels insecure; uploads can give web pages access to the terminal filesystem, so enabling them carries a meaningful security trade-off.

Organizations can customize the boot screen with custom.svg and splash.png files placed in /etc as root. The installer also offers an optional 555M PiperTTS package for website narration, with Danish, German, US English, Spanish, French, and Italian languages. These additions are useful for branded or narrated terminals, though the TTS package is a substantial optional install.

Pricing

OpenKiosk costs nothing. The OpenKiosk plan includes the open-source software under MPL, with donations accepted; there is no paid tier or subscription term to weigh. Its zero price does not eliminate operating costs: deployment is self-hosted and requires compatible hardware, Debian 13, and system administration.

Platforms

The current beta installation path is for Linux on x86_64 or aarch64 hardware, with installation instructions for Raspberry Pi 5. Debian 13 is required; support for other Linux distributions is planned for the future. Although separate downloads list Windows, macOS, and Linux packages for version 115.20.0 dated 2025-02-16, those are distinct legacy desktop packages rather than the current beta installation path.

Who it's for

OpenKiosk makes sense for libraries, schools, museums, and other public-facing organizations that can manage Debian-based terminals and want fine-grained control over sessions, URLs, and device settings without a license fee. It is a weaker fit for teams that require a stable release, support for their existing non-Debian Linux setup, or an uncomplicated cross-platform installation. Organizations should also be comfortable managing self-hosted devices and making deliberate security choices around downloads and uploads.

Pros and cons

  • Pros: The MPL-licensed software is free, and remote management can expose settings for one or all registered devices.
  • Pros: Session timers, data-persistence controls, URL allowlists or blocklists, and terminal-access restrictions give administrators practical ways to shape public use.
  • Pros: x86_64 and aarch64 support, including Raspberry Pi 5 instructions, gives Linux deployments a choice of hardware.
  • Cons: The current release is beta and requires Debian 13, limiting suitability for organizations that need a mature release or another Linux distribution.
  • Cons: Strict URL filtering can break pages when their required resources are not allowed, so tighter rules may require careful maintenance.
  • Cons: Enabling uploads can expose the terminal filesystem to web pages, and the maker likewise flags downloads as insecure.

Alternatives

For a device-management need rather than a public browser, SureAsset is a free option with asset lifecycle management, hardware and software license tracking, and API access and automation across desktop, mobile, and web platforms.

Kiosk is a free open-source PDF reader, making it a better match when reading PDFs—not configuring public browser terminals—is the goal. FreeKiosk is worth comparing for Android and cloud kiosk deployments; its first cloud device is free forever, while its Android app supports Android 8.0 and later.

For iOS, KioskFrame offers a free core kiosk browser with no time limit, plus a paid plan with a 14-day trial. UniKiosk is an Android and web alternative with a free plan per screen that includes unlimited screens and full kiosk lockdown.

Organizations seeking paid, multi-platform management could consider Hexnode Kiosk Browser, whose paid plans start at $2.20 a month and include a 15-device starting allocation. Kiosker is another paid-subscription option for Android and iOS, with monthly and yearly plans and a seven-day trial. For Windows-focused deployments, SiteKiosk is a paid alternative with an annual maintenance renewal option for its Windows Classic license.

Browse more options in Kiosk Browsers and Kiosk Management Software.

Verdict

Choose OpenKiosk if your organization can run Debian 13 terminals and wants a free, open-source public browser with remote configuration and meaningful session controls. The main reason to choose it is the breadth of kiosk restrictions without a license charge; the main reason to look elsewhere is the beta release and narrow current installation requirement.

Getting started

  1. Open the OpenKiosk website and review the current installation documentation
  2. Prepare x86_64 or aarch64 hardware running Debian 13
  3. Create the existing system user named openkiosk
  4. Install the current beta and configure kiosk settings
  5. Register each device with a management token and save a backup token
  6. Set URL rules, session behavior, display controls, and optional narration

Limits worth knowing

The current installation path requires Debian 13 on x86_64 or aarch64 hardware, while other Linux distributions are planned for future support. OpenKiosk is a free, open-source plan under MPL, and the maker labels the current product beta.

Questions

Is OpenKiosk free?

Yes. The listed OpenKiosk plan costs nothing and is open source under the Mozilla Public License; donations are accepted.

Which platforms are supported?

The current installation documentation supports Linux through Debian 13 on x86_64 or aarch64 hardware. A separate legacy download page lists Windows, macOS, and Linux packages for release 115.20.0.

Can devices be managed remotely?

Yes. A registration token connects devices to a web interface where settings can be managed for individual devices or all listed devices.

Does it support URL allowlisting?

Yes. Administrators can use URL allowlists or blocklists, with an optional strict mode that checks resources within each page.

What browser engine does it use?

OpenKiosk is based on Mozilla Firefox and uses the Gecko browser engine.

Is OpenKiosk self-hosted?

Yes. Its deployment mode is self-hosted.

Alternatives to OpenKiosk

All alternatives
  1. 1

    Kiosk

    Free planOpen sourceAndroidiOSWebExtension
    8.0Free plan
  2. 2

    Kiosk Browser

    AndroidWebAPI
    7.2From $1.60 a month
  3. 3

    FreeKiosk

    Free planAndroidWebAPI
    7.1From €0.80 a month
  4. 4

    SiteKiosk

    AndroidWebSelf-hostedWindows
    6.9From $239 a year
  5. 5Hexnode Kiosk Browser logo

    Hexnode Kiosk Browser

    AndroidiOSWindows
    6.8From $2.20 a month
  6. 6Kiosker logo

    Kiosker

    AndroidiOS
    6.7From $24.99 a year