For nurseries & kindergartens
Teachers log a nap, a meal or a nappy change in two taps. Parents see it - with the photos - before pick-up. The office gets attendance, invoices and staff hours in the same system.
No setup fee · No contract · Your data stays yours
TUESDAY 14 MAY
SOFIA
Arrived 07:52TODAY
Breakfast
09:15Ate well
Water play in the garden
10:40Nap
12:30 - 14:051h 35m
Nappy change
14:20Dry
Parent app in English, Greek, Russian & French
Works on any phone - nothing to install
Every school's data fully isolated
Built for the floor, not the desk
The problem
A teacher writes the day on a sheet. It gets lost in a bag, or it arrives at 6pm with three words on it. Meanwhile the office is chasing the same information twice - once for the parents, once for the invoice.
KidsKlab collapses that into one flow. Log it once on the floor and it's already where the parent, the register and the invoice need it.
Three people, one system
The day as a timeline - naps, meals, nappies, photos and notes, as they happen. Message the teacher, update allergies or pickup contacts, and pay what's due by card without leaving the app.
Made for a phone held in one hand. Tap the child, tap the type, done - times are editable because logging happens after the moment, not during it.
One console for the whole school: who's in today, who owes what, which room is over ratio, and who worked which hours.
The parent app
Every moment becomes an icon on a strip that stays pinned to the top while the day scrolls underneath it.
The lit icon is always whichever record is at the top of the list, so the rail tells a parent where they are in the day. Tap a moment and that record comes straight up. Someone opening the app after work can go to the 10:40 photo without scrolling past everything that happened before it.
Nap
12:30Went down easily
Water play in the garden
10:40Breakfast
09:15Ate well
A child's day in the parent app. Names and entries are invented.
What's inside
Not a to-do list app with children's names in it. Each piece below is built around how a nursery day really works.
Naps, meals, nappies and any type you define yourself - with options, notes and editable times. Open-ended naps stay open until someone ends them.
Recorded per child, separately for sharing with other families and for use in marketing, with 'never asked' kept distinct from 'refused'. Filing a photo against a child who has no consent is refused by the database, not by a checkbox someone can skip. Parents withdraw consent themselves, with no request to approve.
Real-time threads between a family and their child's teachers. Parents can't message each other - the channel stays professional by design.
Staff-to-child ratios per room, live, with an alert the moment a room goes over - before it becomes an inspection finding. Record each room's floor area in square metres and it is checked the same way: where the rules for your jurisdiction set a space requirement per child, the room is measured against the children actually in it. A room can be correctly staffed and still be too small, so the two verdicts are shown separately rather than as one green tick.
Trust
This is the part we'd want to ask about if we were choosing software for our own child's nursery.
SecuritySeparation is enforced in the database itself, on every table, not by application code that could forget. One school can never read another's records - we test this as a matter of routine.
A parent sees their own children. A teacher sees the classes they're assigned to. Admin screens are closed to everyone else. Same rules for the app and the office console.
Images live in private storage and are served through short-lived signed links, so a URL that leaks doesn't become a permanent window into your nursery.
Less time writing the day down. More time with the children - and parents who actually see it.