Communications
Email and in-app notes to families and staff, off the same roster as everything else. Texted family alerts and voicemail are in early access.
Email live · texting early access
Homeroom · one platform for the whole school
Most schools run twenty tools that do not talk to each other — a student system here, a yearbook editor there, a photo vendor, a directory, a health-office spreadsheet, a fundraiser page. Homeroom is the one platform underneath all of it. One roster feeds every part, so a student’s name is right on the report card, the ID card, the yearbook page, and the picture-day list, without anyone retyping six hundred names. The core is free to the school.
Core platform free — no per-student license. The engines are built; the picture-day store and texted alerts are early access, and live payment is not turned on yet. We label which is which.
One vendor instead of about twenty
A school district’s software budget is a stack of contracts that do not share a roster: the student information system, the gradebook, the yearbook tool, the school-photography vendor, the directory, scheduling, comms, the fundraiser platform, the health-office log. Homeroom replaces the stack. Enrollment, rosters, standards-based report cards, transcripts, and course-request scheduling live in the same platform as the yearbook editor, picture day, the nurse’s console, and the family store — sharing one source of truth.
And it is modular: a preschool skips the scheduling engine, a district skips the memory book, a studio takes only picture day and commerce. You take what fits and leave the rest.
What it replaces
Homeroom
The walls live below the app
Most platforms put their privacy promises in application code and a policy page. Homeroom puts the load-bearing ones one layer down, in the database itself, where an app bug cannot route around them. A cross-school read returns zero student rows — and that wall is re-checked by CI on every build.
Postgres decides which rows each school can see. A cross-school read returns zero student rows, and CI re-checks that wall on every build.
A single module governs every lane — commerce, publications, face-matching, the directory — with a database trigger that refuses to publish a consent-blocked student even if the app is bypassed.
Money and commissions run on add-only ledgers. A correction is a new entry, never an edit, so who-approved-what outlives the person.
Raw card data is never handled on our own servers — the payment surface is walled off so the sensitive path stays outside the platform.
This is what the platform enforces now, in code we can point a board or an auditor at — not a certificate we bought.
A student system that follows the student
Homeroom is a real school operating system: enrollment and rostering, a staff and family directory, records that follow a student from grade to grade, standards-based report cards, transcripts, and course-request scheduling. It is built to stand in for the incumbent student information systems, not sit beside them — and because it shares the platform’s one roster, the same names and enrollments drive the gradebook, the ID cards, the yearbook, comms, and the library.
Import once, or start clean; nothing gets re-keyed across the platform. The record is the source of truth, and every other part of the platform reads it rather than asking a volunteer to type it again.
The publications suite
The publications suite is the part schools already know us for, and it is the deepest editor in the category: layers, version history, your own self-hosted fonts, a page ladder with deadlines, and a print check that refuses a broken job instead of shipping it. One editor makes the yearbook, the newspaper, the literary magazine, the memory book, and the online editions — plus all your publications in one place, annuals for sports, arts, journalism, and a district edition — with a built-in ad-sales engine and a fundraising lane where the school keeps the proceeds.
It is roster-native, so student names come straight from the platform, not a volunteer’s spreadsheet. All of it is free to the school.
Picture day, run off the roster
Picture day runs off the same roster as everything else, so the adviser cockpit already knows who is enrolled. Every part of the day is a handler you set: capture, proofs, fulfillment, and the ID-card pipeline can run on the platform, be self-run by the school, or route to an outside vendor — mixed and matched, so a school can sell through us while a local studio still shoots the day. Backdrops, and the senior, underclass, sports, and dance verticals are built in.
Finding a student’s photo is a permission-checked roster lookup on name and ID — not a face scan. Facial recognition is off by default, and a minor’s photo is never made public, never indexed, and never sold.
The photo and face posture, stated plainly.A health office no yearbook company has
This is a category the photo and yearbook vendors do not touch. The Five-Rights medication engine is built and tested as a pure rule engine. Recording a dose in-app is not switched on yet: the route returns a plain refusal and tells the nurse to use the paper MAR.
An immunization-compliance dashboard blocks by default: a student who is not cleared does not quietly pass. It is built to be Medicaid-billing-ready. Because it is on the same roster, the nurse is working from the same enrollment as the front office, with no separate list to reconcile.
Everything else a school runs
Beyond records, publications, picture day, and the health office, the platform carries the rest of what a school runs. It is one house of brands on one foundation — 675+ owned sites across the family, each a real product on the same roster, consent, and money model. Take what fits.
Email and in-app notes to families and staff, off the same roster as everything else. Texted family alerts and voicemail are in early access.
Email live · texting early access
A consent-gated family store, fundraisers with no skim, studio and rep commission wallets, payroll, aging, 1099s, bank reconciliation, and tuition collection — on add-only ledgers. Live payment is not turned on yet.
Engines built · live payment not turned on yet
An account base seeded with every US school from public records, a deals-and-forecast pipeline, a competitor-intelligence layer, and an interactive geocoded territory map — each scoped per user by the same database walls.
Built
A native coding sandbox, an assessment engine, study sets and flashcards, per-state standards content, and an office suite — the classroom-facing side of the platform.
Built
A notation engraver, a DAW, and our own trained instrument models. The engraver is ours. Some published scores were produced with a GPL toolchain, and we are cleaning that up rather than claiming otherwise.
Built · early access
A skinnable command center in a real browser desktop — windowing and multitasking — that ties the platform together for advisers, studios, and administrators.
Built
Moving to us is an import, not a leap of faith
Getting started is a roster import, not a rebuild. And leaving is symmetric: your data is exportable in a clean export and deletable on request. Switching to us, or away from us, is an import-and-export, not a vendor hostage fight. A school owns its data on the way in and on the way out.
Step 1
Bring an existing student roster once and it drives the whole platform — records, gradebook, picture day, ID cards, and comms.
Step 2
Check the names and enrollments against your source. The roster is the one source of truth every part of the platform reads.
Step 3
Bring advisers, the front office, and the nurse onto the same enrollment. No six-week re-keying project before anyone sees value.
Built for the questions a board will ask
A school’s data of record lives in our own private cloud — infrastructure we operate end to end, not rented space on a public cloud and not handed to an outside photo or AI service. Rosters, records, and photos are never sold.
On compliance: FERPA and COPPA walls are enforced at the database — a single-school FERPA wall, a rep PII wall that shows studios zero student rows, and an under-13 block in the commerce path. Our data-processing and state student-privacy agreements (DPA, NDPA, SDPC) are build-ready. SOC 2 for us is a readiness posture, not a purchased certificate — and we say that plainly rather than implying an audit we do not have.
If your review needs the paperwork or a security conversation, there is a real path to request it.
Free to the school. We earn when the school sells.
The core platform is free to the school — no per-seat license, no per-student fee. We earn the way the school does: from picture-day sales, ad sales, and fundraisers that run above a code-enforced cost floor, with automatic payouts to each party’s own connected account, and a fundraiser gift is never skimmed.
The picture-day store is in early access — built, opening gradually. When it opens, families buy prints and downloads and the school earns above that floor. We are honest about the state of it: there is no live checkout on this page and no charge is taken here.
Leave your email and we will tell you the day the store opens.
Email only. No account, no charge, nothing bought here — the store is early access and this page takes no payment.
Every student deserves a yearbook
We built one platform for everything a school runs because a school buried in twenty disconnected tools is a school that cannot afford to make sure every kid ends up on a page. The core is free to the school so cost is never the reason a student is left out of the record.
Start with a roster and the part you need most — the editor, the records, picture day, the health office — and add the rest when you are ready. That is it. No per-student license, no lock-in, no leap of faith.