Arrival and pickup
Check a child in, and check them out against the adult who collected them. At most one open session per child per day, and a retry never opens a second one.
CubbyLoop is the calm daily record for one center: who is in the building, what happened in each child's day, and which family can see it. It is built for a director who is still on the floor and a teacher who is holding a phone in one hand.
Honest status: the daily loop below is built and tested, the server behind it is deployed, and the app has been driven through a whole fictional day against it. No screen has been run against that server yet and sign-up is not open — here is exactly where the product is.
Centers do not need another system. They need these four answers to be right at four o'clock on a Tuesday, when the phone is ringing and someone is at the door.
The composer asks only for what that kind of update needs: how much they ate, what was served, a short note the family reads as written. The teacher never has to leave the room, and never loses track of which child is selected.
A parent opens their feed and sees their own linked children, grouped by day: when each arrived, what they ate, when they slept, what they joined in. A guardian linked to a different family sees none of it — and that boundary is covered by its own tests, not by a hidden button.
In the building, open sessions, updates still sitting on a staff device, and the handful of things that need a person — each counted from what was actually recorded, with the time of the count printed next to it. A stale board says it is stale instead of calling itself live.
The strongest privacy protection is not a policy page — it is the absence of a place to put something. These are not switches a center can turn on. There is nowhere in CubbyLoop to record any of them.
Everything on this list runs in the app right now and is covered by its tests. Nothing else is advertised on this site.
Check a child in, and check them out against the adult who collected them. At most one open session per child per day, and a retry never opens a second one.
An arrival recorded against the wrong twin is corrected with a reason. The correction references the original rather than overwriting it, so the day still reads honestly a month later.
Meals, bottles, naps, diapers, toileting, activities and a short note. Each type has its own closed set of fields, so a meal cannot be saved as a shapeless blob of text.
A parent sees their own linked children and that day's updates. They cannot reach a classmate, another family, a roster or a staff directory — and that is proven by tests, not by hiding a button.
A teacher sees the rooms they are assigned to and nothing else. Remove the assignment and the access goes with it. A suspended membership authorizes nothing at all.
A family link is created only by accepting a one-time invitation, never by editing a field. Invitations expire, can be revoked, and a replayed acceptance is safe.
The demo is the product with an invented center inside it: Willow & Pine Early Learning, three rooms, twelve children, none of them real. It runs offline, it resets, and it is seeded with the awkward situations — an open session, a corrected checkout, a suspended teacher, an update still waiting to send.
There is no clickable demo on this website yet, and we are not going to put a button here that pretends otherwise. The whole script is published instead, with a real screen for each step.
CubbyLoop follows the device's light or dark setting throughout, at every text size people actually use. The app is rendered and checked at phone, tablet and desktop widths, in both brightnesses, at text scales up to double size.
CubbyLoop today is a complete, tested daily loop running on a device with fictional data. The server functions and the access rules behind it are deployed, and the app's data layer has been driven through the whole day against them. What has not happened is a screen rendered against that server, and there is no way for a center to get an account at all. Nothing can be delivered to a parent, and messaging, photos, notifications and tuition are not features a center could rely on.
The price is decided and published — $89 a month for one center — but there is no sign-up button here, because we do not want a center paying for a promise. It opens when the product is ready for one.
CubbyLoop is being built for independent centers of roughly 20 to 100 children at one location. If that is you, we would rather hear what your day actually looks like than guess at it.
Writing to us starts an email to hello@cubbyloop.com. There is no form on this site and nothing is collected by this page.