why I built it
The problem I'm interested in
Homeschool families end up running their school across a dozen systems — planning in one place, records in another, documents nowhere in particular — and the parent becomes the integration layer.
What I built
A homeschool operating system a family sets up to match how they actually work: modules turn on and off, the navigation rearranges, and the school has its own name, colours and identity.
Records, documents and guidance live in the same product, so a transcript is built from the records the family already kept rather than assembled from scratch in a spreadsheet.
What it does
- Customise My OS: turn tools on and off and rearrange navigation — a module that is off is hidden, and its records are kept
- School identity: name, tagline, colours, and a faith / secular / mixed / unlabelled designation
- Document Studio: progress reports, transcripts, diplomas and portfolios that match one school identity
- Attendance, capture and export, with records marked family-issued unless the family changes that
- A parent learning centre of short guides, recommended from the household's own records
- A shareable school page that is private by default, with grades, diagnoses and private records never publishable
The thinking(3 notes)
Turning a tool off hides it and keeps its records. Deleting somebody's history because they stopped using a feature is not a setting.
The share page defaults to private and refuses to publish the sensitive things at all, rather than trusting a tired parent to get a permissions screen right at 11pm.
Reading a guide never changes a family's records by itself. Guidance and record-keeping stay separate on purpose.
Where it is
Not open to the public yet — this is the build as it stands, not a launch announcement.