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 two hundred kilometres away. By the time you'd be getting in the car, it's already fixed.
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
Kioskbase costs less than one drive to the tablet.
A tablet on site never breaks while you're in the next room. It breaks on Friday afternoon, two hours away from you. 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 €80 in Kioskbase
- 1 tablet at €3.00 a month
- 26 months of service
- a tablet in the €2.00 tier (21–50)
- 40 months of service
- a tablet in the €1.50 tier (151+)
- 53 months of service
- one drive not taken
- ≈ 2–4 years of service
Skip one call-out a year and Kioskbase has paid for itself.
- Updates without the drive. Push a new version from your desk; a device-owner tablet installs it by itself and reports how it went. Even without device owner it arrives remotely — someone at the tablet just taps to confirm.
- Remote desktop without handing out access. TeamViewer or AnyDesk starts on your command from the desk. Staff read you the code off the screen and confirm — no passwords to share, no unlocking the device for anyone.
- 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 Novak 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.
It runs on iOS, Windows, Mac, Linux and Android — anything that can display a web page.
- 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.
- Standalone customers get their portal at portal.kioskbase.com. Whoever takes Kioskbase together with the Modulo system manages tablets right inside their own admin — the same controls, one door closer to the rest of the company.
What runs on the tablet
The kiosk is the carrier. You choose the content.
Kioskbase displays any web address — your own system, someone else's booking form, anything. And if you don't have the content yet, we build two platforms of our own, each for a different kind of company.
Modulo CMS
A company system built from modules: attendance, meal serving, ordering, reservations, invoicing, helpdesk. The terminals (lunch counter, attendance gate, cash desk) are ready-made screens — you plug them in, you don't program them.
Setup: a six-digit code and you're done. Everything else — address, role and content — is driven from the server, remotely, any time. An attendance gate becomes an ordering terminal with one click from the office.
dochadzka.online
A proven, specialised attendance system for companies that want attendance and nothing else. It runs on hundreds of terminals in the field; operated by enexi s.r.o.
Setup: you sign in once right on the tablet and pick the terminal — just as attendance users are used to. Kioskbase handles the rest: it lets the Auth0 sign-in through the lock, keeps the device on the terminal and backs the sign-in up, so an outage doesn't mean a drive to the tablet.
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 labels (like “before the update”) 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
Why it exists
Built by an IT field technician — for IT field technicians.
Kioskbase was not born in a startup meeting. I have managed Android tablets for companies for years as a field technician — as a service partner of enexi s.r.o., who run the dochadzka.online attendance system, I look after more than 250 of them. Different Android versions, different screens, different hardware. On top of that, my own devices around the Modulo system — from vending terminals to my home.
I have tried every third-party kiosk app there is. Each one was missing something different, each one billed separately, and when something broke there was nobody to call. So I wrote the tool I need every day myself — and I maintain it the way I want someone to look after my own devices.
So you know who you are talking to. The person who answers wrote the code and runs his own fleet on it. A reasonable request makes it into the app when it makes sense and does not weaken security — not when it survives a product committee.
Contact
Tell us the count and the purpose.
We reply with a concrete number and what to prepare on the tablets. No ten-field form.