elementaryschool.technology · For elementary schools · Technology that gets out of the way
The technology under an elementary school should disappear. A K–5 building has no bell-schedule solver, no course requests to arbitrate, and no production yearbook editor to run — it has a small office and the youngest children. So this is quiet plumbing: a roster that syncs once from your student system, ID cards for the youngest students off that same roster, a simple branded school page, and a picture day matched by name rather than by a face scan. Built for a small staff and careful with young children by default.
Roster sync, ID cards, and the school page are live today. The picture-day store and text-message alerts to families are in early access, and money is honest-off — the platform does not process payments yet.
What fits
A high-school platform is built around a bell-schedule solver, course requests, transcripts, and an athletics-eligibility office — none of which a K–5 building runs. Trim that tool down and a small staff ends up fighting software built for a problem they do not have. These four quiet pieces are shaped like the elementary problem from the start, and they all read from one roster.
Piece 1
A school signs in the standard ways it already logs in, or imports the roster a single time, and that one list becomes the spine the rest of the technology reads from. Nobody enters the same young students into a directory tool, an ID printer, and a picture-day form as three separate lists that drift apart the first time a name is corrected in one and not the others. The roster is owned by the school, not by us.
Piece 2
Cards for the building come off the same roster, not a second spreadsheet. A card design, the roster photo, and a student number print as a batch, and when a child’s record changes in one place the card pipeline reads the change. There is no parallel badge database to keep in sync by hand, and no re-keying a class of six-year-olds twice.
Piece 3
Stand up a clean, branded page with your colors, your contact details, and the handful of things families actually look for. It is enough to look established without hiring anyone, and it is a page — not a storefront you have to staff, price, and reconcile. A small office should not be handed a shopping cart it did not ask for.
Piece 4
Picture day runs off the same roster, so a photo is matched to a child by the roster name a person with permission applied, the way you would look up a name in a directory. A parent finds only their own child by a permission-checked roster lookup, not a face scan. It is careful with the youngest children by default, because a five-year-old’s photo deserves the careful default.
The most expensive thing a small office does with its data is enter it more than once. A child typed into a directory tool, again into the ID printer, and again into a picture-day form is three copies that drift apart the first time a name is corrected in one and not the others — and in an elementary building that is a lot of hand-keying of the same young students.
Here the roster is entered once. A school signs in the standard ways it already logs in — the same single sign-on the staff use elsewhere — or imports the list a single time, and that roster becomes the shared spine: the directory, the ID batch, the school page, and picture day all read from it. Correct a name in one place and it is correct everywhere, because there is only one place. The roster is owned by the school, not by us, and it is never sold or handed to an outside company.
This directory and roster are a daily-driver that complements the district’s student information system. It is not a certified state system of record, and it does not pretend to be one or to replace the SIS — it reads from the roster and holds what the school’s own office owns.
ID cards for an elementary building are usually a second spreadsheet somebody maintains by hand, a stack of photos that has to be matched to names, and a print run that goes wrong the first time a child’s name was fixed on the roster but not on the badge list. Here the cards come off the same roster the directory and picture day use.
A card design, the roster photo, and a student number print as a batch. When a child’s record changes in one place, the card pipeline reads the change — there is no parallel badge database to keep in sync. For the youngest students, that means the card carries what the school chooses to put on it and nothing it does not, and a card is regenerated from the roster rather than re-typed. It is plumbing that gets out of the way, which is the whole point.
An elementary school does not need a web shop bolted onto its front page. It needs a clean, branded page: the school’s colors, a contact, the office hours, and the handful of things a family actually looks for. This stands one up without hiring anyone and without a designer — enough to look established, and no more than that.
It is deliberately a page, not a store. A small office should not be handed a shopping cart, a price list, and a reconciliation report it never asked to run. When the picture-day store opens later, it opens as its own thing in early access — the school page itself stays a page. That restraint is the feature: the technology should fit the size of the staff, not the size of the vendor’s ambition.
Everything here runs on our own private systems. A young child’s records and photos are owned by the school and are never sold to or shared with advertisers, data brokers, or any outside company. A minor’s photos are never made public, never handed to an outside search engine to index, and never sold.
Find-my-child is a permission-checked roster lookup, not a face scan. A parent finds only their own child by the roster tag a person with permission applied, the same way you would look up a name in a directory — it does not scan a crowd of children for a face by default. Face matching is not available in the shipping product: it holds no face-recognition model weights and computes no face template. Photo finding uses a permission-checked roster lookup instead. Withdrawing the opt-in stops the matching, on the spot. It is consent-gated and owned by the school.
One thing we will not overstate. The step that actually destroys a stored template is not finished, and we are not going to tell a parent it runs on a schedule when it does not. The cleanup job is built to refuse rather than pretend: when it cannot truly destroy a template, it stops and raises an alert instead of marking the job done. We would rather leave that alert standing than write down a deletion we cannot show you, and when it can be demonstrated end to end this page will say so plainly. What does already work, end to end, is the part most families are really asking about: mark a child do-not-publish and their pictures and their name drop out of the digital edition, the online reader, and the print run.
This page is deliberately careful about two things it does not claim. It does not promise that a picture can never leave the building — a picture-day order routed to an outside print lab does leave it, and we say so. Face matching is not available in the shipping product: it holds no face-recognition model weights and computes no face template. Photo finding uses a permission-checked roster lookup instead. The claims we make are the narrower, keepable ones: private systems, never sold, face-matching off by default, templates walled and never handed back, a withdrawal that stops the matching, and a minor’s photos never made public, indexed, or sold. An adviser or office manager can read that posture in plain words and hold us to it.
Live today: roster sync and standard sign-in; ID cards printed off the same roster; and the simple branded school page. These are built and run today.
Early access: the picture-day store and text-message alerts to families. These are named early access on purpose, and nothing else on this page is dressed up as more finished than it is.
Money is honest-off. elementaryschool.technology does not process payments yet. When the picture-day store opens, it is the surface where a school earns and a parent buys their own child’s portraits — that is a description of a future product, not a live charge. The store settles no money on this site today; no card is charged here.
What this is: elementaryschool.technology is a for-profit software platform for elementary schools. It is not a school, not a district, and not a nonprofit. Elementary schools are (mostly) public; the platform that serves them is a for-profit vendor. There is no charity or donation framing here, and none would be honest. There are no invented adoption numbers, testimonials, or named schools on this page; the anchors are what the technology actually does. A demo shows the current state honestly — what is built, what is early access, and what is honest-off.
FAQ
They are two views of the same platform. elementaryschool.software is the whole-school family front door — the family directory, the keepsake memory book, gentle picture day, and the family newsletter you run. elementaryschool.technology is the technology that fits underneath — the roster sync and sign-in, the ID cards, the simple school page, and where the data lives. If you are choosing what your office will run, start with the software page; if you are the person asking how it is built and how it fits a small K–5 staff, this is the page for you.
Because a high-school platform is built around a bell-schedule solver, course requests, transcripts, and an athletics office — none of which a K–5 building runs. Trim that down and a small staff is fighting a tool built for a problem they do not have. These four pieces — roster, ID cards, a school page, and a name-matched picture day — are shaped like the elementary problem from the start, and they get out of the way instead of demanding attention.
No — that is the whole point. You sign in the standard ways your school already logs in, or import the roster once, and every piece reads from that one list: the directory, ID cards, the school page, and picture day. Correct a name in one place and it is correct everywhere, because there is only one place. The roster is owned by the school and is never sold.
Find-my-child is a permission-checked roster lookup, not a face scan. A parent finds only their own child by the roster tag a person with permission applied — it does not scan a crowd of children for a face by default. Where a parent turns optional face-matching on, the template stays on our own private systems, is never sent to an outside AI service, is never handed back to anyone, and is kept for a limited window of about a school year — the point at which it is marked due for destruction. Withdrawing the opt-in stops the matching. We will not overstate the rest: the step that destroys the stored template is not finished, so we do not claim it happens on a schedule; the cleanup job stops and raises an alert rather than write down a deletion it cannot carry out. It is consent-gated and school-owned.
No. The directory and roster are a records daily-driver that complements your district’s student information system; it is not a certified state system of record, and it does not try to replace your SIS. It holds the directory, the ID cards, and the family-facing record the school’s own office owns, and leaves the certified record to the system certified for it.
Not yet on this site. The picture-day store and text-message alerts to families are in early access, and money is honest-off — elementaryschool.technology does not process payments yet. When the store opens it is where a school earns and a parent buys their own child’s portraits, but today it settles no money; no card is charged here.
Roster sync, ID cards, and the school page are free to start and settle no money. elementaryschool.technology is a for-profit software vendor for elementary schools — not a school, district, or nonprofit — and there are no invented adoption numbers or testimonials on this page. The honest next step is a demo that shows the current state plainly: what is built, what is early access, and what is honest-off.
One roster, four quiet pieces, and technology that gets out of the way. Roster sync, ID cards, and the school page are live and free to start; the picture-day store and text-message alerts to families are in early access; and money is honest-off — the platform does not process payments yet. A demo walks the whole thing honestly.