Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

OpenKiosk

openkiosk.tech

  • Free plan
  • Windows
  • macOS
  • Linux
7.7 Club score Visit openkiosk.tech

What OpenKiosk is

OpenKiosk is an open-source browser for turning a computer into a remotely configurable public terminal. It is based on Mozilla Firefox and is described as a system-integrated standalone browser, with controls intended to limit public use to web browsing. Administrators can register devices with a token and manage settings through a web interface. The token is removed from the device after registration, so a backup token is needed for later device management. Settings cover fullscreen display, visible browser bars, an on-screen keyboard, session timers, and whether bookmarks, cache, history, and cookies persist. URL allowlists and blocklists are available; strict filtering also checks resources within pages and may disrupt pages if rules omit resources. The current beta installation instructions require Debian 13 on x86_64 or aarch64 hardware, with an existing system user named openkiosk. Raspberry Pi 5 installation instructions are included. The software is free under the Mozilla Public License and is labeled Beta.

Who it suits

OpenKiosk suits organizations setting up public browsing terminals that need remote configuration, session controls, and URL restrictions. Its current beta installation instructions are for Debian 13 on x86_64 or aarch64 devices.

Good to know, and what to watch

  • Remote settings can be managed through a web interface
  • Supports URL allowlists and blocklists
  • Can control session timers and browser data persistence
  • Includes an on-screen keyboard
  • Free and open source under the MPL
  • Current beta instructions require Debian 13
  • Strict URL filtering may disrupt pages
  • The maker labels the product Beta
  • Downloads and uploads are labeled insecure when enabled

OpenKiosk

Free

Open source

Getting started

  1. Open the OpenKiosk website
  2. Prepare Debian 13 on x86_64 or aarch64 hardware
  3. Create the system user named openkiosk
  4. Install OpenKiosk using the current instructions
  5. Register the device with a management token
  6. Save a backup token for future device management

Limits to check

The current beta documentation requires Debian 13 on x86_64 or aarch64 hardware; other Linux distributions are planned for future support. OpenKiosk is free and open source, with no paid-plan quota stated.

The Club's review

OpenKiosk is a self-hosted Firefox-based browser for public terminals. It is best for organizations able to manage Linux devices and tune their kiosk settings. Its control set is substantial for free software, though the current beta’s Debian requirement limits deployment choices.

Overview

OpenKiosk turns a computer into a standalone public browser, with system-level controls intended to keep users within web browsing. The maker says it has been deployed since 2005 in places such as libraries, schools, museums, hospitals, airports, hotels, and businesses. That record gives the project useful context, but the current release is still labeled beta, and the maker invites users to test it and report issues.

The software is open source under the Mozilla Public License (MPL), self-hosted, and free; donations are accepted. The current release is 151.0.4 Beta. Installation instructions require Debian 13 (trixie) and a system user named openkiosk. The documentation covers x86_64 and aarch64 hardware, including Raspberry Pi 5, while support for other Linux distributions is planned. This makes the current version a poor fit for organizations that need to deploy across an existing mix of Linux distributions.

Key features

Devices can register for remote management with a token, after which administrators can access settings for an individual device or all listed devices through a web interface. Registration removes the token from the device, so administrators should save a backup token for future device management.

Kiosk settings cover fullscreen mode, toolbar and URL-bar visibility, and an on-screen keyboard. Administrators can retain bookmarks between sessions or set a timer and ending countdown, and choose whether cache, history, and cookies persist. These options help tailor a terminal to short public visits, but they also require deliberate configuration: retained data may not suit a shared device.

URL rules support allowlists and blocklists. Strict mode checks resources loaded within each page, which can enforce tighter limits but may break pages if the rules omit required resources. Administrators can disable local terminal access, start with a clean browser profile, and control downloads and uploads. The documentation labels downloads and file uploads insecure when enabled; uploads can expose the terminal filesystem to web pages, so those options deserve particular caution.

Custom boot branding uses custom.svg and splash.png files placed in /etc as root. An optional 555M PiperTTS package adds website narration in Danish, German, US English, Spanish, French, and Italian. The language choices and on-screen keyboard offer practical accessibility options, though the large optional package adds a notable installation cost in storage.

Pricing

OpenKiosk has one free plan: OpenKiosk costs nothing and includes the open-source software under MPL. There are no paid tiers or stated seat limits. Donations are accepted. The trade-off is operational rather than financial: teams must host and manage their own deployment, and the current beta requires Debian 13.

Platforms

The current installation path is Linux-only, specifically Debian 13 on x86_64 or aarch64 hardware. Although separate legacy downloads list Windows, macOS, and Linux packages for version 115.20.0 dated 2025-02-16, they are distinct from the current beta instructions. Teams choosing a platform should not assume those older packages provide the current release’s deployment path.

Who it's for

OpenKiosk is a strong candidate for libraries, schools, museums, and other organizations that need controlled public browsing and can standardize on Debian 13. Its URL rules, session controls, and remote device settings give administrators meaningful ways to shape public access without a license fee. It is less suitable for teams that need a production-ready release, broad current-OS compatibility, or minimal system administration.

Pros and cons

  • Pros: Free, open-source MPL software avoids per-device licensing costs.
  • Pros: URL filtering, session timers, and controls over browser data persistence let administrators adapt terminals to public-use policies.
  • Pros: Remote settings can be managed through a web interface for one device or all listed devices.
  • Pros: x86_64 and aarch64 support includes installation guidance for Raspberry Pi 5.
  • Cons: The current beta requires Debian 13, restricting use on other Linux distributions for now.
  • Cons: Strict URL filtering can break pages when required resources are not allowed.
  • Cons: The maker warns that downloads and uploads are insecure when enabled, with uploads granting web pages access to the terminal filesystem.
  • Cons: The optional PiperTTS package is 555M, a material addition for deployments with limited storage.

Alternatives

For a comparison of kiosk browsers or kiosk management software, consider what matters most: OpenKiosk focuses on public browsing controls, while some alternatives emphasize device management or other platforms.

KioskCore is worth considering if you want a freemium management platform across Android, iOS, self-hosted, web, and Windows. Its free plan covers up to two devices, seven-day metric history, on-demand screen captures with 24-hour retention, three email alerts per device per day, and community support.

SureAsset is a better match if asset lifecycle management, hardware and software license tracking, or API access and automation are the priority; its free plan spans Android, macOS, Linux, web, Windows, and iOS.

Quantem Kiosk Software may suit teams willing to pay for a broader cross-platform option. It has no free plan, offers a free trial, and lists its Essential plan at $2.40 a month, billed per device per month.

Kiosk is a free, open-source PDF reader with no paid plans, and may be preferable when the need is specifically a PDF-reading kiosk.

Trio Kiosk Management offers paid plans and a free trial across Android, iOS, Linux, macOS, web, and Windows; consider it if you prefer a paid management product rather than OpenKiosk’s self-hosted browser approach.

Inteset Secure Lockdown is Windows-only and has free and paid options, making it an alternative for organizations committed to Windows terminals.

Kiosker is a freemium option for Android and iOS, with monthly and yearly subscriptions and a seven-day trial; it is a better platform match for mobile kiosk devices.

Moki is a paid option with a free trial for Android and iOS device management. Its MDM plan uses per-device monthly pricing, limits API calls to 500 per hour per account, and allows up to 10 users per account before charging $15 per additional user per month.

Verdict

Choose OpenKiosk if you need a no-cost, configurable public browser and can standardize on Debian 13 while accepting beta software. Its strongest case is the combination of URL, session, and device controls under an open-source license. Look elsewhere if you need a stable release or current support for other operating systems and Linux distributions.

The verdict

OpenKiosk provides browser, session, and URL controls for public terminals, along with remote device management. Check the Debian 13 requirement and beta status against your deployment needs.

Questions people ask

Is OpenKiosk free?

Yes. The OpenKiosk plan is free, and the software is open source under the Mozilla Public License; donations are accepted.

Which platforms does OpenKiosk support?

The listed platforms are Linux, macOS, and Windows. Current beta installation documentation requires Debian 13 on x86_64 or aarch64 hardware.

Can administrators manage devices remotely?

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

Can OpenKiosk restrict websites?

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

Is OpenKiosk open source?

Yes. The maker releases it under the Mozilla Public License.

What the maker publishes

Beta status and support
The maker labels the product Beta and asks users to test it and email bugs or issues. source
Browser basis
The maker describes OpenKiosk as a web browser based on Mozilla Firefox, designed for public terminals. source
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. source
Current beta
The maker’s current homepage describes OpenKiosk as a beta that turns a machine into a secure public browser. source
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. source
Current release
The documentation lists version 151.0.4 Beta as the latest release. source
Custom branding
A custom boot screen can use custom.svg and splash.png files placed in /etc as root. source
Deployment history
The maker says OpenKiosk has been deployed since 2005 in museums, schools, universities, libraries, hospitals, airports, hotels, governments, and businesses. source
Kiosk controls
Settings include fullscreen mode, toolbar and URL bar visibility, an on-screen keyboard, and options to retain bookmarks across sessions. source
Legacy desktop downloads
A separate download page lists Windows, macOS, and Linux packages for release 115.20.0 dated 2025-02-16. source
License
The maker says the software is open source and released under the Mozilla Public License. source
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. source
Purpose
OpenKiosk is a remotely configurable secure public browser terminal. source
Purpose
OpenKiosk is a Firefox-based web browser designed as a public terminal and kiosk solution. source
Remote management
A token can register devices for management through a web interface, where settings for one or all listed devices can be accessed. source
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. source
Security-related limits
The settings documentation labels downloads and file uploads as insecure options, with uploads allowing web pages access to the terminal filesystem. source
Session controls
Administrators can set a session timer, show an ending countdown, and control whether cache, history, and cookies persist across sessions. source
Support contact
The contact page lists [email protected] for inquiries and [email protected] for bug reports. source
Supported hardware
The documentation specifies x86_64 and aarch64 devices and includes installation instructions for Raspberry Pi 5. source
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. source
System requirement
The current installation instructions require Debian 13 (trixie) and an existing system user named openkiosk. source
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. source
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. source

Checked against the maker's pages on 8 Oct 2026.