Flocci AI Kids: A Crayon Portal Hiding a Serious Machine

A six-year-old asks why the sky is blue, and then asks why the answer is why, and then asks why again — the hundredth “why?” of an ordinary afternoon, the engine of a mind that has not yet learned to stop being curious. And the screens we hand that child to answer it are, almost all of them, built to end the question rather than extend it. Autoplay the next video. Serve the next reward. Keep the eyes still. A generation is being raised on software engineered to answer “why?” as fast and as flatly as possible, so the asking stops. Flocci AI Kids is built on the opposite bet: that the right response to a child’s hundredth “why?” is not a slicker answer but a workbench — a place to build the thing they were wondering about, with their own hands, seat by seat.

The two problems hiding inside “teach kids AI”

There is a fashionable version of children’s AI education, and it is mostly theater: a chatbot with a cartoon mascot, a video course a parent buys and a kid abandons, a “certificate” for watching. It treats AI the way bad edtech treats everything — as content to be consumed. The child watches someone else build, nods, and forgets by Thursday. Passive curricula are the junk food of learning: engineered for the sale, not the outcome.

But there’s a second, quieter problem sitting underneath the pedagogical one, and it’s the one most edtech gets catastrophically wrong. To sell a workshop seat you need commerce — payments, seat limits, receipts, follow-up — and to run that commerce you need to touch a family’s data. When the learner is a child, that data is not a growth-hacking asset. It is a legal and ethical live wire. Most platforms treat every user as fuel: profile them, retarget them, feed their behavior back into the model. Do that with a nine-year-old and you have not built edtech. You have built surveillance with a mascot.

Flocci AI Kids answers both problems at once, and the answer to the second is the more radical of the two.

The insight: the AI-teaching product that refuses to run AI

Here is the thesis that makes AI Kids more than another workshop-booking site. It is the one Flocci product whose entire pitch is build with AI — and it is the one Flocci product deliberately forbidden from using AI on its own users. It carries no runtime LLM integration at all. Unlike nearly every other app in the estate, there is no model in the request path, nothing summarizing a parent, nothing scoring a child.

That is not an oversight or a feature not yet shipped. It is a wall, and the wall has a name: it is the platform’s only child-data-bearing product, so under India’s DPDP Act 2023 its data is walled off — never benchmark-eligible, never behaviorally profiled. Even the shared platform’s event graph, where other Flocci apps freely emit and mine signals, must treat any AI Kids event as untouchable: no benchmarking, no profiling, full stop.

Sit with how unusual that is. The industry default is to instrument the child. AI Kids inverts it: the children learn to command the model; the model is never allowed to command them back.

The delightful contradiction on the surface

If the ethical inversion is the serious half, the aesthetic is the delightful half — and it is a deliberate contradiction. The portal is sketchy on purpose: hand-drawn crayon lines, the Patrick Hand and Caveat and Indie Flower typefaces, the visual language of a kid’s notebook. It looks like something doodled in the margins of a maths book.

Behind that doodle runs a genuinely serious production engine. Atomic seat allocation. GST math. A dual-path PayU checkout. Passwordless OTP auth. Failed-payment recovery. Affiliate commissions. The crayon is the costume; underneath it is commerce infrastructure that would not embarrass a fintech. That gap — childlike front, industrial back — is the whole personality of the product.

How a booking actually moves

Strip away the crayon and watch a parent move through the system. This is the loop, and every step is built to remove friction a family would otherwise pay in patience.

1. Book a seat without ever making an account

   There are no parent or student accounts to create, no password to invent and forget. A parent picks a workshop and checks out — that’s the entire identity story. The friction most sites add at exactly the wrong moment simply isn’t there.

2. A seat is claimed atomically, or you're waitlisted honestly

   On a successful checkout, seats_left is decremented inside a database transaction. If the workshop is full, the system returns a 409 SEATS_FULL waitlist response rather than quietly overselling. Two parents checking out for the last seat at the same instant cannot both win — the database refuses to let them.

3. Pay through PayU, with a fallback that keeps the checkout alive

   Checkout computes 18% GST, generates PayU tokens with a redirectToken and successToken per payment intent, and supports both the broker-routed flow and a direct SHA-512 form-generation path as a fallback. The success callback atomically verifies the payment, marks the transaction booked, creates a booking lead, decrements the seat, and emails both parent and admin.

4. Look up your order later with a 6-digit code

   Weeks on, a parent who wants their booking details doesn’t log in — they request an OTP. A 6-digit code is emailed, its hash stored in email_otps with a 10-minute validity, and verifying it returns their successful bookings. The password they never created is a password they can never lose.

5. Rate the workshop, once the filter clears it

   Both signed-in and anonymous users can leave star ratings and comments. Each one passes through a profanity filter and lands in a moderation queue for admin approval before it’s ever shown — with bulk approve and reject in the cockpit — so the public wall stays clean.

The engine parents never see

The parent-facing portal is half the product. The other half is the ops cockpit, and it’s where the commerce discipline shows.

That offline-first stance is a small philosophy in itself. Most sites treat a backend hiccup as the user’s problem — a spinner, a stack trace, a shrug. AI Kids treats it as its own problem to hide: the crayon portal would rather show slightly stale mock data than confront a parent with failure. And to be found in the first place, custom pre-build scripts emit sitemaps, an events RSS feed, and AI-crawler discovery assets — ai.txt and llms.txt — aimed squarely at ChatGPT Search, Claude, and Perplexity. A product walled off from using AI still wants AI engines to know it exists.

Where it sits in the platform, and where it’s going

AI Kids is Flocci’s K-12 and student-outreach touchpoint — the doorway through which the youngest users meet the platform. Its stack is unfussy and deliberate: a React 18, Vite, TypeScript and Tailwind front end with Zustand and TanStack Query; an Express 5, Prisma, JWT-and-bcrypt backend on Node 20 with node-cron, Helmet, Pino, and its own Nodemailer path; PostgreSQL underneath, now dual-target so a DATABASE_URL flip moves it between the local flocci_app_aikids database and the Neon instance that keeps its live Vercel deployment fed.

Its relationship to the shared platform is the interesting part: partial, and honestly so. Because AI Kids lives on Vercel and cannot reach the VPS-local providers directly, its shared-service adoption is by design incomplete. Notification runs flag-plus-fallback, its own email path authoritative. Identity and payment cutovers are deferred. Intelligence is not applicable — the wall again. It is, in fact, the sole exception to the platform’s clean-replacement service-cutover strategy, the one app that keeps a flag-and-fallback shape precisely because its live home can’t yet see the shared services. The database dual-target work is done; the rest waits on VPS convergence.

The forward story is not a bigger feature list — it’s a deepening of the same principle. The commerce engine already handles the hard parts: atomic seats, dual-path payments, affiliate commissions, lead recovery. What grows on top of that is curriculum and reach — more bootcamps, more camps, more hackathons for six-to-fourteen-year-olds — carried by an engine that stays boringly reliable so the teaching can be the interesting thing. And the wall stays up. As other Flocci products lean harder into the model layer, AI Kids will keep being the one that doesn’t, the one where a child’s data is a responsibility rather than a resource. That child asking “why?” for the hundredth time deserves a place that hands them a workbench and then, pointedly, refuses to study them while they use it.