Tokora — Queue & Token Display System (PHP + MySQL, Self-Hosted)
Self-hosted queue & token display — issue numbers, call them to counters, run the waiting-room board.
The problem it solves
Clinics, pharmacies, service desks, and council offices still run their waiting rooms on a paper pad and a raised voice — visitors don't know their place in line, staff lose track of who's next, and there's no record of how long anyone actually waited. Cloud queue systems fix it, but they charge per branch every month and often want a special ticket printer or display appliance.
- No fair, visible order — just names called across a noisy room
- No idea which counter is free or how long the queue really is
- A monthly per-branch fee (and vendor hardware) for what is a numbered list
What you get
Services with daily-reset tokens
Each service issues its own prefixed numbers (A-001, B-014) that reset automatically every day — no cron job, computed on view.
Staffed counters
Bind a counter to one service or set it to 'any service' and it pulls the oldest waiter first — call next, mark served, no-show, or recall.
Public ticket kiosk
Visitors take their own number from a self-serve kiosk page, protected by a honeypot and per-IP rate limiting — no staff needed to issue tickets.
Live waiting-room display board
A now-serving-per-counter board with queue lengths that any screen can show, auto-refreshing with an offline meta-refresh plus a tiny polling script — no CDN, no appliance.
Per-ticket status page
Each visitor gets a public page they can watch on their phone to see their number approach — so they don't have to hover at the counter.
Daily report + hardened exports
Issued, served, no-shows, still-waiting, and average wait per service, exported as a dependency-free PDF and a formula-injection-hardened CSV.
Pricing — one-time, yours forever
Available soon — get notified
Checkout isn't open yet. Leave your email and we'll send one note the moment Tokora — Queue & Token Display System (PHP + MySQL, Self-Hosted) can be purchased — nothing else.
Screenshots
Honest limitations
- The display board is a web page you put on your own screen — no dedicated hardware, ticket printer, or digital-signage driver is included
- No SMS or push notifications — visitors watch the board or their own status page
- Not an appointment-booking or scheduling system — it manages a live walk-in queue
- Single-tenant: one organisation, one admin login per installation
2-minute web installer, plain PHP 8 + MySQL (or SQLite for a trial), no Composer or build step — Docker image included.
Frequently asked questions
Do I need special hardware or a ticket printer?
No — the kiosk, the counter console, and the display board are all just web pages. Put the board on any spare screen or TV with a browser; visitors take a number on their own phone or a shared tablet.
How do the numbers reset?
Per service, automatically each day, computed on view — there is no cron job to schedule and nothing to reset by hand.
Does it store any patient or personal health data?
No — Tokora tracks tokens, services, and counters only. It holds no health records and no personal data beyond an optional free-text note, so it has zero PHI and zero payment surface.
MySQL or SQLite?
Either — SQLite for a zero-config trial, MySQL/MariaDB for production on ordinary shared hosting.
What if the developer disappears?
You get the full PHP source and your data lives in one database you own — nothing phones home, nothing expires.