Android kiosk software
The tablet stays where you put it.
Kioskbase holds an Android tablet on a single address and won't let it wander. You run it from a browser — including the one standing two hundred kilometres away with nobody next to it.
Android 7 and newer · six-digit setup · part of Modulo CMS
Anchoring to one address
- device
- SOTEN K70 · Android 13
- ip
- 10.0.4.37
- battery
- 84 % · charging
- lock
- device owner
- ›connection ✓ 200
128
meals served today
- Menu 162
- Menu 241
- Diet25
07:14
hold your card to the reader
- Clocked in34
- Clocked out2
- On site32
adrift · not anchored yet
- IP address
- MAC address
- Wi-Fi name
- gateway
- mobile carrier
- battery
- battery temperature
- model
- Android version
- app version
- free memory
- free storage
- clock drift
- kiosk state
- device owner
Why it pays
You're not paying for a licence. You're paying to skip the drive.
A tablet on site never breaks while you're in the next room. It breaks on Friday afternoon, two hours away. Most of what a kiosk really costs is not in the software — it's in the car.
One call-out
- 200 km round trip
- 14 l
- diesel at €2.10/l
- €29.40
- depreciation, tyres, servicing
- ≈ €50
- total
- ≈ €80
And a day spent driving cannot be billed to anyone else.
The same money buys
- at €1.50 per device
- 53 devices for a month
- at €2.00 per device
- 40 devices for a month
- at €3.00 per device
- 26 devices for a month
- one drive not taken
- months of service
Skip one call-out a year and the software has paid for itself.
- Updates without the drive. A new version is pushed remotely; on a device-owner tablet it installs silently, with nobody there to tap Accept.
- Frozen page without the drive. Restarting the app, or the whole tablet, is one click.
- Network faults without guesswork. Diagnostics walk DNS, port 443, the TLS handshake and the actual server response, then tell you which step failed.
What makes it different
Kioskbase knows what the device is for.
An ordinary kiosk knows one thing: show this address. A year later you have twenty rows of URLs and nobody remembers which tablet hangs in the kitchen and which one sits at reception.
Kioskbase works with purpose instead. A device is not https://…/pickup, it is the meal pickup terminal at Novák Ltd., kitchen site. Switching purpose is one click, and the server assembles the address — nobody retypes anything on the tablet.
That is also why devices are grouped by company and site. A customer can be given access to their own devices only, at one of three levels: from a read-only view to full control.
Where it all runs
Nothing gets installed on your computer.
The management console is a web page. You open it in whatever browser is in front of you — a laptop, a phone on the road, someone else's computer at a customer site. Nothing to download, no Windows build and a separate Mac one, no client to keep updated.
- Kioskbase on the tablet, a browser on your side. Between them a single connection the site's network has to allow outbound: HTTPS on port 443.
- The device listens on no port. It opens the connection itself. Nothing can reach it from outside, so nothing has to be opened inbound.
- It works from a phone. Restarting a tablet in another city can be done from a car park — which is rather the point.
What it does
Eleven reasons not to get in the car.
Holds one address
Full screen, no address bar. A link outside the allowed domains opens nowhere — not even in the browser.
A hard lock
As device owner it uses the system Lock Task mode. It takes over the home-screen role while locked and hands it back when unlocked.
Six digits to set up
One number is typed on the tablet. Address, allowed domains, purpose and mode all arrive from the server.
Remote update
Silent on a device-owner tablet. The installer's answer is reported back, so you can see whether it really went through without a prompt.
Remote restart
The app or the whole tablet. The command is acknowledged before it runs — otherwise the device would find it again after booting and loop.
Window screenshot
It captures the app's own window only, never the Android screen. It shows what the terminal is displaying, not what a person is doing.
Network diagnostics
DNS → port 443 → TLS handshake → actual server response, in the order things fail. The result is a sentence, not a log.
Device telemetry
IP, MAC, Wi-Fi name, mobile carrier, battery and its temperature, model, Android and app version, free memory and storage, clock drift.
Sign-in backups
Named and automatic. The contents never leave the device — only backup names and dates are sent.
Slideshow mode
Images from an album on a loop. The same tablet becomes a display surface without any extra software.
Remote desktop
TeamViewer or AnyDesk can be launched by command when a screenshot of the window is not enough.
Rollout
Three steps while the tablet is still in the box.
-
Install and type the code
The app asks for one number, six digits long. Everything else it fetches from the server.
-
Make it device owner
Optional, but worth it at a customer site. One command over USB, on a factory-reset tablet with no account added.
-
Run the rest from the console
Purpose, address, allowed domains, version and mode all change in the browser. Nothing is retyped on the tablet again.
What never leaves the device
A kiosk is no reason to watch people.
Tablet management tools tend to double as surveillance tools. This one does not, and that is a decision rather than an omission.
- Screenshots capture the app window only. Not the Android screen, not other apps, not notifications.
- Sign-in backups stay on the device. Names and dates go to the server; the contents never do.
- Telemetry describes the device, not a person. Location is never read; the permission Android requires for the Wi-Fi name is used for the network name and nothing else.
- No camera, microphone, contacts or storage permissions. Unencrypted connections are blocked at system level, debug builds included.
Pricing
From €1.50 per device per month.
The price falls as the fleet grows, and a year costs ten months — two are on us. No lock-in, no setup fee.