For independent child-care centers and preschools

Run the day calmly. Keep every family in the loop.

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.

The CubbyLoop director dashboard: nine of twelve children in the building, nine open sessions, one update waiting to sync and four follow-ups, above a follow-up list and three classroom cards.
The director's Today board. A real screen from the app, running the fictional Willow & Pine Early Learning demo. No part of it is a real child or a real center.
What it is for

Four questions, answered quickly and accurately

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.

  1. Who is in the building right now?
  2. Which adults are responsible for each classroom and child?
  3. What happened during each child's day?
  4. Has the correct family received the correct information?
For the teacher

A meal, a nap, a diaper change — in a few taps, on a phone

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.

  • Meals, bottles, naps, diapers, toileting, activities and notes
  • Each type has its own fields, validated — not a free-text blob
  • The room's board shows who is in, who is not, and when it was counted
The CubbyLoop update composer on a phone: Ellie O. is selected, the Meal type is chosen, "Most" is selected for how much she ate, and a note field is ready for the family.
Recording a meal for one child in the Fireflies room. Real screen from the app, running the fictional Willow & Pine Early Learning demo. No part of it is a real child or a real center.
For the family

The right family sees it. Nobody else does.

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.

  • Only the children a guardian is actually linked to
  • No classmate list, no other guardians, no staff directory
  • A link is created by accepting an invitation, never by editing a field
The CubbyLoop parent feed on a phone: the Okafor family, two linked children, with Amos's arrival at 8:10am, story circle and lunch, and Ellie's arrival, meal, diaper change and water-table activity.
One family's feed. Two linked children, one day. Real screen from the app, running the fictional Willow & Pine Early Learning demo. No part of it is a real child or a real center.
For the director

The day, counted from the records

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.

  • Follow-ups are operational prompts, not determinations
  • Room staffing shows the center's own target, never a legal threshold
  • Corrections and checkouts land in an audit trail with their reasons
The CubbyLoop director dashboard: 9 children in the building of 12 enrolled, 9 open sessions, 1 update waiting to sync, 4 follow-ups, and three rooms each showing checked-in counts against the center's own staffing target.
The Today board for a 12-child demo center. Real screen from the app, running the fictional Willow & Pine Early Learning demo. No part of it is a real child or a real center.
The boundary

What CubbyLoop has no field for

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.

Read the privacy boundaries

  • Health history, diagnoses, medication or immunization documents
  • Government identifiers, custody documents or court orders
  • Child accounts, child-facing chat or public child profiles
  • Cameras, video streaming, facial recognition or biometric check-in
  • Precise location tracking of children, staff or guardians
  • Advertising identifiers, behavioural profiling or data sold to anyone
Built today

The daily loop, end to end

Everything on this list runs in the app right now and is covered by its tests. Nothing else is advertised on this site.

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.

Corrections that keep the original

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.

The day, in a few taps

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 feed scoped to one family

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.

Classrooms and staff scope

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.

Protected guardian links

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 guided demo

One fictional day, in nine steps

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.

The CubbyLoop audit trail: a checkout with the collecting adult, an attendance correction reading “Arrival recorded against the wrong twin at 8:40”, a staff assignment, a suspension, two guardian links and a revoked invitation — each with an actor, a role and a timestamp.
Step eight: the day, read back a week later. Real screen from the app, running the fictional Willow & Pine Early Learning demo. No part of it is a real child or a real center.
Built for a long day

The same screens at 6am and at 7pm

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.

  • Light and dark, on every screen
  • Checked at 375, 768 and 1440 pixels wide
  • Readable at 1x, 1.6x and 2x text size
  • State is never carried by colour alone
The same CubbyLoop director dashboard in dark mode, with the same counts, follow-ups and room cards on a dark navy surface.
The same board, in dark mode. Real screen from the app, running the fictional Willow & Pine Early Learning demo. No part of it is a real child or a real center.
Where the product is

We would rather tell you this up front

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.

Tell us about your center

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.