Homeroom Technology · how the platform is built
The technology behind the platform, explained plainly.
A school’s technology buyer wants to know how a tool actually works before they trust it with a roster. This explains the platform plainly: a single roster, a creation suite that runs in the browser, a money model enforced in code, and a privacy posture built on running in our own systems.
The browser-based creation suite, the in-code money rules, the privacy wall, and single sign-on are live today. A published status page for school technology offices is in early access; this page says plainly which is which.
Nothing to install
A browser-based creation suite -- nothing to install on a cart of laptops, and nothing for an IT office to image or patch by hand.
Rules, not policy
Money rules are enforced in code, not left to a policy a person could forget: a cost floor and a fundraiser-skim guard the platform itself checks, every time.
Our own systems
Privacy is built on running in our own systems, with a shared roster underneath the whole platform.
Runs in the browser
The full editor -- layers, version history, fonts, and a print check -- runs in the browser. A school deploys it by sharing a link, not by installing an application on every machine in a computer lab or a cart of laptops. There is nothing to license per seat and nothing for a technology office to keep patched on each device; the browser is the whole footprint.
Because the editor lives in the browser, a student or a staff member picks up where they left off on a different machine without carrying a file around on a drive, and an IT office does not inherit a rollout project every time a lab gets refreshed.
Rules enforced in code, not by policy
A cost floor that nothing sells below, and a fundraiser the platform cannot skim, are enforced in the software itself -- not left to a policy a person could forget or a spreadsheet a new hire might miss. A technology buyer does not have to take a sales conversation on faith; the guarantee is a rule the checkout path itself runs.
The same discipline applies to who can see what: a privacy wall in the software keeps a sales representative from seeing a student row. It is a control built into the platform, not a promise resting on a person remembering to look away -- and it is a scoped guarantee about that access path, not a claim that no system anywhere is ever imperfect.
One roster underneath
A teacher, an adviser, or the school’s own technology staff signs in with the standard ways a school already logs in, or the school imports once from its student roster system -- and the whole platform shares that one list. The directory, the publications, and picture day all read from the same roster, so a technology office is not asked to keep three separate rosters in sync by hand.
When a student enrolls, transfers a building, or graduates, updating the one shared roster is what keeps every part of the platform current -- not a separate re-entry step per tool.
Privacy, said plainly and scoped -- not an absolute
Platform data is kept in our own systems. It is never sold, and it is never handed to an outside company. That is a promise about where the data lives and who it is shared with, not a claim of total immunity from every possible attack or incident -- no software vendor can honestly promise that, and this page does not.
A student’s photo is matched to their record through a roster lookup, not an always-on face scan. Facial recognition is off by default -- a conditional control a family and a school decide on together, not a blanket claim that the platform never touches the capability at all.
What is live, and what is early access
The creation suite, the in-code money rules, the privacy wall, and single sign-on are running today. A published status page for technology offices is still on its way, and this page keeps the line between them honest.
Live today
The browser-based creation suite, the in-code money rules (the cost floor and the fundraiser-skim guard), the privacy wall, and single sign-on all run on the platform right now.
Early access: a status page for technology offices
A published status page built for a school’s own technology office. Not live yet; described here as the product it will be.
How we label it
If a capability is early access, this page says early access — not “coming soon” theater. A technology buyer should never be sold a feature that has not actually shipped.
Common questions
Do we need to install anything?
No. The full creation suite runs in the browser, so a school deploys it by sharing a link, with nothing to install on a cart of laptops or a computer lab.
How are the money rules actually enforced?
In the checkout path itself: a cost floor that nothing sells below, and a fundraiser-skim guard the software checks every time, not a policy a person has to remember to apply.
Can a sales representative see a student’s row?
No -- a privacy wall in the software keeps that access path closed. It is a built-in control, not a promise resting on someone choosing to look away.
Is facial recognition used to find a student’s photo?
By default, no -- a student’s photo is matched through a roster lookup. Facial recognition is off by default.
Is the platform unhackable?
No software vendor can honestly claim that, and this page does not. The specific, named controls above -- the cost floor, the privacy wall, roster-based sign-in -- are the actual guarantees; there is no blanket security promise beyond them.
Is the published status page for our technology office live yet?
Not yet. It is in early access. Until it ships, the honest way to reach us about an issue is the contact page.
Is it free, and is there a checkout on this page?
The core is free to start. There is no checkout and no live charge anywhere on this page.
What this page is and is not claiming
Homeroom Technology is the how-it-is-built facet of the platform: a browser-based creation suite, money rules enforced in code, one shared roster, and a privacy posture built on running in our own systems. The creation suite, the in-code money rules, the privacy wall, and single sign-on are all live today. A published status page for school technology offices is in early access — not live, and this page never implies otherwise. Platform data is kept in our own systems and is never sold or handed to an outside company; a student’s photo is matched through a roster lookup, and facial recognition is off by default. This page makes no absolute security claim -- no software vendor can honestly promise immunity from every attack, and this one does not pretend otherwise. This is a for-profit vendor, not a charity, and nothing here is dressed up as a charitable gift. There are no invented uptime numbers, benchmarks, or testimonials here, and no competitor is named. The core is free to start, and this page runs no checkout.