Class, student and parent
A student belongs to a class, a class has teachers, and a student has one or more parents or guardians. That link is what decides who sees what.
What gets built
Four things you could have working this week
Not a feature list. These are the apps people actually describe, and what the platform hands back when they do.
Daily log and announcements
The teacher records the student's day, with meals, naps and a note, and the school publishes announcements by push to everyone or just one class, with read receipts.
Attendance and report cards
A register per lesson, grades per subject and term, and the report card open on the parent's phone as soon as the teacher closes the grades.
Tuition by subscription
Recurring card billing, with a history per student and the list of overdue accounts on the office dashboard.
Included
The parts nobody wants to build twice
Database, login, payments and publishing are part of the platform, not a list of services you go and wire up afterwards.
A real database, not a form dump
Every screen reads and writes models you can open, query and export. The data is a database of yours from the first minute, not a spreadsheet the app pretends to read.
Login for your own users
Email, magic link and Google sign-in, with roles and per-record ownership enforced by Postgres itself. A badly written screen cannot become a leak, because the database answers empty.
Payments that land in your account
Stripe, Pagar.me and Mercado Pago connect once. Card, Pix, boleto and subscriptions, with the card fields rendered by a hosted vault your app never touches.
Web, installable, and in the stores
One project published three ways: your own domain, an icon on the phone straight from the browser, and a signed binary submitted under your own store account.
Found in search, and by the models
Titles, metadata, sitemap, structured data and social images are generated with the app. Pages get found instead of only being linked.
React code you can take with you
Real React, edited line by line or by clicking the element on screen, exported as a ZIP or pushed to your GitHub. No lock-in you have to negotiate your way out of.
How it works
From a paragraph to a published app
Three steps, and the second one is the one people do not believe until they watch it.
Start here
A prompt you can paste right now
This is a complete first message, not a slogan. Paste it, change the nouns to yours, and you have an app to react to instead of a blank page.
Build an app for a school with a nursery and a primary section. Classes with year, shift and teachers; students with a photo, date of birth, class, allergies and dietary restrictions, linked to one or more parents or guardians; a teacher sees only their own classes, takes the day's register and logs each student's day with meals, naps, activities and a note; the school publishes announcements with attachments to the whole school, a year group or a class, with push and read receipts from parents; grades per subject and term, with the report card released to parents when the teacher closes the term; a school calendar with holidays, meetings and events; the week's menu; tuition billed as a card subscription with a payment history per student; a parent signs in and sees only their own children; and an office dashboard with students per class, average attendance, unread announcements and arrears.
Ready to start from
Templates in this category
A template is a working app with data already in it. Open one, make it yours, publish it under your own account.
Questions
Frequently asked questions
Describe it. See it running. Publish it to the store.
Free to start, no credit card. You subscribe when you want your own domain without the badge or your app in the stores, and on the Builder plan you take the code with you if you ever want to.