EXP—01
in production
Tulips.edu
Founder · Jun '26 — now · Ranchi · school ERP, live in 3 schools and used daily
Founded and built it alone, and I own the whole stack: architecture, deployment, operations, plus client onboarding, pricing, support and incident response. Multi-tenant school ERP: student records, fees (UPI deep links + QR), academics and parent communication across three surfaces — public site, staff ERP, parent portal — on one SPA. Tenant isolation is enforced in middleware with tenant_id on every table; every API route is role-checked across five roles; every state change emits an immutable audit event.
failure-mode thinking
The most frequent failure in an Indian school isn't the server — it's the teacher's connectivity. Attendance is offline-first: writes queue in IndexedDB and background-sync on recovery. Uploads go direct to R2 via presigned URLs, so storage failures never touch the app server. Migrations are raw versioned SQL, because schemas holding fee records don't get ORM surprises.