highschool.technology · For high schools · The stack, not the sales pitch
A single high school can publish more pages in a year than a small college: a yearbook, a newspaper, a literary magazine, online editions, a directory, and a wall of ID cards. The stack here is what carries that load — a roster synced once from your student system, a real production editor with version history, ID cards printed from the same roster, and publications and records that read from one source of truth instead of four copies that drift apart. This page is about the engineering and where the data lives, not a feature wall.
The editor, roster sync, ID cards, and records are live today. The picture-day store and outside-lab order routing are in early access, and money is honest-off — the platform does not process payments yet.
The stack
A high school program is not one app; it is a stack. Read from the bottom up, each layer stands on the one below it — and the whole thing stands on a single roster and our own private systems.
Layer 1
One roster is what every layer above reads from. A school signs in the standard ways it already logs in, or imports the list once, and that single roster becomes the source of truth for the whole stack. Nobody re-enters the same students into the yearbook tool, the newspaper tool, the records office, and the ID printer as four separate lists that drift apart the first time a name is corrected in one and not the others.
Layer 2
A browser page-layout editor with the depth a well-funded school pays a design vendor for: layers you can reorder and lock, masking for a real cut-out, your own licensed fonts, and version history on every spread. It is a canvas a design student — or an adviser new to layout — can actually work in, not a template filler with a logo dropped in. The last layer of the editor is a print preflight that refuses a job it can see is broken.
Layer 3
ID cards for the building come off the same roster, not a second spreadsheet. A card design, the roster photo, and a barcode or student number print as a batch, and when a student’s record changes in one place the card pipeline reads the change. There is no parallel badge database to keep in sync by hand.
Layer 4
Enrollment, the staff-and-family directory, and the student record sit on the same source of truth as the publications. It is a records daily-driver that complements the district’s student information system; it does not claim to be a certified state system of record, and it does not try to replace the SIS. It reads from the roster and holds what the school’s own office owns.
Layer 5
Every layer above runs on our own private systems. Student work, rosters, and photos are school-owned and never sold, and find-my-photo is a permission-checked roster lookup rather than a face scan. The matching capability behind that consent is not wired and is not turned on today — we are building it, designed to be studio-enablable with a parent's consent. Where the optional lane is exercised at all, the template is held only inside our own private system — never handed to an outside recognition service, and never returned to anyone. Withdrawing consent stops the matching, refused at the gate rather than honoured on a delay.
Most tools sold to a school as an “editor” are a template filler with a school logo dropped in. This one is built for staff who actually design: layers you can reorder and lock, masking for a real cut-out, your school’s own licensed fonts instead of a fixed menu, and a canvas that behaves the way a design student expects from a desktop tool.
Version history is not a nice-to-have on a yearbook — it is the difference between a recoverable mistake and a lost spread. Every page keeps a history, so an accidental delete at eleven at night in deadline week is an undo, not a phone call to support. Two editors on the staff do not silently overwrite each other; the history shows what changed and when.
The layer the category usually skips is print. A book that looks right on a laptop can still print wrong: an image dropped in at screen resolution, art that runs off the trim with no bleed, color that will not separate. The editor’s print preflight reads a job before it goes out — resolution, bleed, and color — and refuses a job it can see is broken rather than letting a school discover the problem in a box of misprinted books. Refusing a bad job is the honest behaviour; passing it through and hoping is not.
The most expensive thing a school does with its data is enter it more than once. A student typed into the yearbook tool, again into the newspaper roster, again into the records office, and again into the ID printer is four copies that drift apart the first time a name is corrected in one and not the others.
Here the roster is entered once. A school signs in the standard ways it already logs in, or imports the list a single time, and that roster becomes the shared spine: the yearbook ladder, the newspaper staff list, the directory, the ID batch, 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.
The records office and the design studio usually live in different software that never speak. On this stack they share the roster, so the directory, the student record, and the ID-card pipeline are the same list the publications use. An ID card prints from the roster photo and the student number already on file; nobody maintains a parallel badge spreadsheet.
Be plain about scope: this is a records 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 — the directory, ID cards, and the publication-facing record — and leaves the certified transcript-of-record to the system certified for it.
Everything on this stack runs on our own private systems. Student work, rosters, 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-photo is a permission-checked roster lookup, not a face match. It finds a student’s pictures 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 for a face by default. Face matching is a capability we are building and is not turned on today — the recognizer is not yet wired: it holds no face-recognition model weights, and no face template is computed from a photo. Photo finding uses a permission-checked roster lookup instead. Withdrawing the opt-in stops the matching, on the spot.
What does already work, end to end, is the part a family usually means: mark a student 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 a capability we are building and is not turned on today — the recognizer is not yet wired: it holds no face-recognition model weights, and no face template is computed from a photo. Photo finding uses a permission-checked roster lookup instead. The claims we make are the narrower, keepable ones: private systems, never sold, face-matching not turned on in the software we run, templates walled and never handed back, a withdrawal that stops the matching, and a minor’s photos never made public, indexed, or sold.
Live today: the production editor with layers, masking, version history, your own fonts, and the print preflight; roster sync and standard sign-in; the ID-card pipeline; and the records and directory. These are built and run today.
Early access: the picture-day store and outside-lab order routing. 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. highschool.technology does not process payments yet. When the picture-day store opens, it is the surface where a school earns and a family buys prints — that is a description of a future product, not a live charge. The store assembles an order and settles no money on this site today; no card is charged here.
What this is: highschool.technology is a for-profit software platform for high schools. It is not a school, not a district, and not a nonprofit. High 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 stack 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. highschool.software is the program front door — the newsroom, design studio, records office, and fundraising shop you run. highschool.technology is the stack underneath — the roster sync, the production editor, the ID pipeline, and the records that share one source of truth. If you are choosing what your school will operate, start with the program page; if you are the person asking how it is built and where the data lives, this is the page for you.
Layers you can reorder and lock, masking for a real cut-out, your own licensed fonts, and version history on every spread — plus a print preflight that reads resolution, bleed, and color and refuses a job it can see is broken. A template filler drops your logo into a fixed layout; this is a canvas a design student or an adviser can actually work in, with a print check that will not let a broken book ship.
No — that is the point of the stack. You sign in the standard ways your school already logs in, or import the roster once, and every layer reads from that one list: publications, the directory, ID cards, 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.
No. It is 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 publication-facing record the school’s own office owns, and leaves the certified transcript-of-record to the system certified for it.
Find-my-photo is a permission-checked roster lookup, not a face match. It finds a student’s pictures by the roster tag a person with permission applied — it does not scan a crowd for a face by default. The matching capability behind that consent is not wired and is not turned on today — we are building it, designed to be studio-enablable with a parent's consent. Where the optional lane is exercised at all, the template is held only inside our own private system — never sent to an outside recognition service, and never returned to anyone. Withdrawing consent stops the matching, refused at the gate rather than honoured on a delay. It is consent-gated and school-owned.
Not yet on this site. The picture-day store and outside-lab order routing are in early access, and money is honest-off — highschool.technology does not process payments yet. When the store opens it is where a school earns and a family buys prints, but today it assembles an order and settles no money; no card is charged here.
The editor, roster sync, ID cards, and records are free to start and settle no money. highschool.technology is a for-profit software vendor for high 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, one editor, one source of truth for every publication, the records office, and ID cards. The editor, roster sync, ID cards, and records are live and free to start; the picture-day store and outside-lab routing are in early access; and money is honest-off — the platform does not process payments yet. A demo walks the whole stack honestly.