PublicSchool.email · an address, honestly named
A public-school building’s own address — not a personal inbox, and not a working one today
This page names what a traditional public school BUILDING’s front office, attendance desk, records custodian, family-engagement lead, and PTA treasurer could each carry as their own address on this domain. It is a naming page, not a running mailbox: nothing below sends or receives mail today.
Example address shape: [email protected]. No MTA is provisioned for this domain; no mail is created, delivered, or billed anywhere on this page.
What this address is
Named for the desk, not the person who happens to staff it
A public school building runs on a handful of real, recurring correspondence roles: someone answers the front office phone and its mail, someone tracks daily attendance, someone is the building’s designated records custodian under state open-records law, someone coordinates with families whose first language is not the building’s primary instructional language, someone manages IEP and 504 case correspondence, and a parent-run PTA or booster club keeps its own treasurer’s inbox. Every one of those roles today usually rides inside a single shared front-office account, or inside whichever staff member’s personal district account happens to be doing the job this year. When that person changes roles or leaves, the thread of who was writing to the attendance desk about a specific family often walks out with them.
The idea this domain names is narrow and specific: an address belongs to the DESK, not to whoever is currently staffing it. [email protected] would stay the attendance desk’s address across a staffing change; a reply would still read as coming from the desk. That is the entire idea. It is not a claim that the building needs a second email system, and the honest reckoning further down this page says so directly rather than only in a footnote.
It is also deliberately scoped to a single BUILDING rather than a whole district, which is the reason this host sits apart from its own sibling, publicschool.network. A district-wide governance front door makes sense at the district: one elected board, one policy manual, one sunshine-law portal for the whole system. A front-office desk, an attendance clerk, and a PTA treasurer are not district-wide roles — they belong to one building, and a district with a dozen elementary schools has a dozen attendance desks, not one. Naming the address at the building level (yourbuilding.publicschool.email, not yourdistrict.publicschool.email) matches where these roles actually live, even though nothing about that naming choice creates the second email system this page's own reckoning questions the need for.
The problem in one real shape
What actually happens when the person answering attendance@ changes
Most buildings do not run into this problem on a quiet Tuesday. They run into it in late August, when the attendance clerk who has run that desk for six years retires, or in March, when the front-office secretary takes unexpected leave and three different staff members cover the role in a single semester. Whoever is filling in inherits whatever inbox the prior person used — often their own personal district account, sometimes a shared account with a password that has been handed down informally for years, occasionally a brand-new account that starts from zero with no history of the parent who called in February about a chronic absence.
A parent who wrote to that address in the fall does not know any of that happened. They reply to the same thread in the spring and it either bounces, lands with someone who has never seen the earlier message, or sits unread in an account nobody is actively checking during the transition. None of this is a hypothetical edge case invented for this page — it is the ordinary, unremarkable way small-office staffing turnover actually works in a public school building, and it is the specific, narrow problem an address held by the DESK rather than the PERSON would solve, if one existed. It does not solve the underlying staffing churn, and it does not create institutional memory by itself — a new attendance clerk still has to be told what the ongoing threads are. It only keeps the address itself stable across the handoff, so a parent's reply lands somewhere rather than nowhere.
This is also exactly the shape of problem this page's own honest reckoning says a $0 district-issued account can already solve, if the district is willing to set up a role-based alias inside its own existing Google Workspace or Microsoft 365 tenant rather than a personal one. A building considering this domain should ask its own IT department that question first, because the answer is very often yes, at no cost, before ever looking at a third-party domain.
How this differs from the estate’s other .email brands
Not the same shape as preschool.email, privateschool.email, or charterschool.email
The estate already sells a catalog-priced, honest-off branded mailbox on several sibling .email hosts — preschool.email, privateschool.email, charterschool.email, educator.email, and others — each resolved to a shared brand configuration and rendered by one common product page. Those pages show a real catalog price per plan tier (a DISPLAY figure, never a live charge), a persona-specific plan card set, and a “book a demo” lead form, and every one of them carries the same honest transport disclosure this page carries: live MX lookups on those served hosts return no mail-exchange record, so none of them can send or receive mail today either.
publicschool.email is deliberately NOT wired into that shared brand configuration, and this page does not borrow its plan-card layout. Two reasons: first, the KIMI/GROK coordination ruling on this domain (2026-09-04) held it out of the state-school-email family specifically so it would not be folded into a resolver it does not fit, and the same reasoning applies to the mailbox-brand catalog — this domain describes BUILDING DESKS (front office, attendance, records, PTA) rather than a single persona's plan tier, which the shared card layout was not built to show. Second, and more plainly: this page's own honest reckoning found the paid case unproven, so showing a catalog price here — even a display-only one — would imply a decision that has not been made. The sibling .email brands earned their catalog pricing through a real pricebook; this domain has not, and does not borrow one to look more finished.
The desk directory
Eight desks a real building runs, named honestly
Each row is a real, distinct correspondence shape a public-school building office runs today -- not a generic "info@" and "contact@" pair. None of these is a live mailbox; every row is what an address would be for if a building ever claimed one.
| Desk | Address shape | Who would hold it | What it would carry |
|---|---|---|---|
| Front office | [email protected] | The building secretary or office manager, not any one person by name. | The building's general correspondence: a parent asking about early pickup, a substitute confirming a shift, a vendor confirming a delivery window, a visitor asking for the sign-in procedure. The address a family looks for first on the building's own site. |
| Attendance desk | [email protected] | Whoever staffs daily attendance for the building -- a clerk, an assistant principal, or a rotating duty. | A parent's note explaining an absence, a doctor's excuse scan, a truancy-officer inquiry, a coach confirming an athletic-event excusal. Nothing here reads or writes the building's real attendance/ADA math -- that engine, where it exists, lives on the sibling district platform, not on a message sent to this address. |
| Public records / sunshine-law requests | [email protected] | The building's designated records custodian, per whatever state open-records statute applies. | A resident's public-records request for a board packet, a reporter asking for an agenda, a parent requesting their own child's education record under FERPA. A real records desk in a public building genuinely gets this mail; naming the address does not create, route, or fulfill a records request by itself. |
| Family engagement / multilingual liaison | [email protected] | A family-engagement coordinator, ESL/multilingual liaison, or the front office covering the role. | A newsletter reply, a translated-notice request, a question from a family whose first language is not the building's primary instructional language, a volunteer sign-up. The kind of thread that gets lost inside a single shared front-office inbox on a busy Monday. |
| Special education / 504 case coordination | [email protected] | The building's special-education case manager or 504 coordinator. | An IEP-meeting scheduling thread, a related-service provider's note, a parent's question about a service-minute log or an evaluation timeline. This is the single most sensitive desk on this list precisely because IDEA deadline tracking and service-minute logging are real, built engines on the sibling district platform (packages/shared/src/spr-special-ed-compliance.ts) -- and precisely why this page says, without softening it, that this address does not touch that engine and stores nothing today. |
| PTA / booster treasurer | [email protected] | The parent-run PTA or booster club officer for the building, not a district employee. | Fundraiser sign-ups, a sponsor's ad-space inquiry, a volunteer schedule, a treasurer's note about a deposit. Money that moves through a PTA or booster account is the PTA's or booster club's own money and its own tax determination -- nothing on this page is legal, tax, or financial advice, and nothing here processes or holds a cent. |
| Safety & emergency notices | [email protected] | The building administrator responsible for emergency communication, or a district-designated safety lead. | A weather-closure confirmation, a lockdown-drill after-action note to families, a facilities issue report. A safety desk's actual delivery channel in most buildings today is a mass-notification system, not email -- naming this address does not claim to replace or interoperate with one, and this page makes no emergency-notification guarantee of any kind. |
| Substitute / staffing desk | [email protected] | Whoever coordinates day-to-day substitute coverage for the building. | A substitute confirming or declining a placement, a staffing agency's note, a coverage swap between two staff members. A narrow, high-frequency thread that a shared front-office inbox usually absorbs today without a name of its own. |
Every address above reaches nobody today. There is no mail server, no forwarding rule, and no inbox behind any of these -- see “what actually happens today” below for the unconditional version of that sentence.
Deep dive: safety & emergency notices
Named on the directory, and deliberately not sold as an emergency channel
Safety and emergency notices are on the eight-desk directory above because a real building administrator genuinely sends and receives mail about weather closures, lockdown-drill after-action notes, and facilities issues, and that correspondence needs a stable, building-branded address for the same reason every other desk on this list does. What this page will not do is call an address on this domain a channel for actual emergency communication. Most buildings today rely on a dedicated mass-notification system (a phone-tree, text, and voice-call platform built specifically for time-critical alerts) precisely because email is slow, easily missed, and has no delivery guarantee — the wrong tool for a lockdown alert regardless of whose name is on the address. Naming [email protected] here is honest about what that address would be for — routine safety correspondence — and equally honest about what it is not: a replacement for, or an integration with, any emergency notification system a building already runs. No such integration exists, and none is implied.
Deep dive: the records custodian
The one desk on this list whose mail genuinely comes from outside the district
Every state has some form of open-records or sunshine law, and nearly every one of them designates a records custodian at the level of the government body holding the record — for a public school, that is very often the building or the district, not a single named employee. That custodian's mail comes from residents, journalists, advocacy groups, and parents exercising a FERPA right to their own child's education record, none of whom are inside the district's own email directory and most of whom have no way to know which staff member currently holds the custodian role. A request sent to a departed employee's old personal-style district account can sit unanswered past a statutory response deadline simply because nobody is watching that inbox anymore — a real compliance risk that is specific to this one desk in a way none of the other seven quite are.
This is also the desk where a role-based address earns the clearest, most literal reading of its own name: [email protected] is legible on a public-facing records-request form or a district website in a way a personal-sounding account is not, and it survives every staffing change the role goes through. None of that changes who the LEGAL custodian is, what must be retained, what exemptions apply, or how a request gets fulfilled — this domain is not a records-management product, and provisioning an address here would not create or replace the actual records system a building or district already runs. It would only give the desk a name that outlives whoever is answering it this year.
Deep dive: the PTA / booster treasurer
The one desk on this list that is not district correspondence at all
A Parent Teacher Association or a booster club is, in almost every state, a legally separate nonprofit or unincorporated association from the school district it supports — it has its own bank account, often its own EIN, and its own officers who are volunteer parents, not district employees. That structural separation is exactly why a PTA treasurer's correspondence sits awkwardly inside a district-issued email system: the district's IT department has no obligation to provision an account for someone who does not work for the district, and a treasurer who uses a personal Gmail account for fundraiser sign-ups and sponsor invoices creates the same walked-out-the-door risk this page names everywhere else, except here there is often no district account to fall back on at all.
Nothing on this page changes the PTA's or booster club's own legal or tax status, and nothing here is legal, tax, or financial advice — whether a gift to a PTA is deductible to the giver is the PTA's own determination under its own nonprofit status, not something this platform decides or represents. What a named address would offer this desk specifically is the same thing it offers records@: a name that belongs to the treasurer ROLE across the volunteer turnover a parent-run organization goes through every year or two, rather than to whichever parent's personal inbox happens to be doing the job this season.
The family this domain sits inside
Real, built capability exists in this family — on two OTHER hosts, not this one
PublicSchool.email is one of three sibling hosts in the same product family, and the other two are not naming pages -- they carry real, committed, wired capability. publicschool.network runs an elected board’s policy manual and meeting minutes through a closed, fail-closed lifecycle (draft → adopted → superseded → archived), records named, on-the-record roll-call votes into the minutes, and serves an unauthenticated, adopted-only public sunshine-law portal so a resident can read a public board’s record with no login. It also runs the real attendance and average-daily-attendance arithmetic a public school’s accountability depends on (present/absent counts, a ratio that is NULL rather than a fabricated zero on a zero denominator, and a distinct-student membership headcount) -- with the state-submission channel itself held honest-off pending a per-state map. Special-education IDEA deadline tracking and service-minute logging are a real, built engine underneath that platform too.
publicschool.software runs a genuinely free publications editor (yearbook, newspaper, online edition) at no license cost to the building, a one-time roster import that feeds the family directory and ID cards without re-keying a name twice, and an honest money model where the platform’s guards -- a code-enforced cost floor on a parent-store item, a fundraiser ledger that holds the platform’s own cut at zero -- are real and built even though live card payment on that host is itself held honest-off.
None of that reaches a message addressed to anything on THIS domain. An email to [email protected] does not read or write the IDEA service-minute log on publicschool.network; a message to [email protected] does not surface a board’s adopted minutes through the sunshine-law portal. The three hosts are siblings under one family, cross-linked at the bottom of this page; they are not one integrated inbox today, and this page does not imply that they are.
The citations above are precise on purpose: the governance and roll-call engine, the attendance/ADA math, and the IDEA compliance tracker are real, committed, registered application routes on the district platform (packages/shared/src/sch-board-governance.ts and sch-board-rollcall.ts; apps/api/src/domain/attendance-engine.ts; packages/shared/src/spr-special-ed-compliance.ts), not marketing language describing an idea. This domain has no equivalent citation to offer for anything beyond naming an address, and the honest version of this page says that plainly rather than borrowing the sibling's citations to look more built than it is.
What actually happens today
No mail server exists for this domain
This is the plain, unconditional version, not a caveat at the bottom of a feature list: publicschool.email has no mail transfer agent, no MX record, no DKIM record, no DMARC policy, and zero lines of application code anywhere in the platform that route a message to or from this domain. A message sent to any address named on this page — frontoffice@, attendance@, records@, every one of the eight — is not received, stored, forwarded, or read by anyone. It reaches nobody, today, unconditionally.
That is a description of the current state of a real, owned domain, not a promise about a future one. Nothing on this page says an inbox is coming, and nothing says when. If a building address is ever actually provisioned, that would be a separate, later, founder-confirmed decision with its own real infrastructure -- an MTA, a spam and abuse posture, a retention and consent policy for the minors’-data correspondence several of the eight desks above would genuinely carry. None of that exists yet, and this page does not claim otherwise in order to look more finished than it is.
What this would cost
No price is shown, because none has been set
There is no catalog figure on this page. Not a hidden one, not one waiting behind a signup form: no price for a claimed publicschool.email building address has been decided, so none is shown. There is no checkout, no card field, and no plan comparison anywhere on this page, and nothing here bills anyone a cent.
That absence is deliberate rather than an oversight. A live competitor (see the honest reckoning below) already sells a version of this at $0 for forwarding-only and $3-9 per month hosted, and two free incumbents already cover most of the underlying need for most buildings. Any price this domain might eventually carry has to be set against that reality, by Chris, once a real wedge exists -- not invented here to make the page look more like a finished product than it is.
Minors’ data
What would happen to a message about a specific student
Several of the eight desks above -- attendance, special services, family engagement, safety -- exist specifically to carry correspondence that names or concerns a specific minor. Because no mailbox is provisioned for this domain, no such message is received, stored, retained, or processed by us today, for any desk, on any address. That is the honest floor: no student’s data reaches us through this surface at all right now, because the surface does not receive anything.
If a building address on this domain is ever actually provisioned, correspondence naming a specific student would be handled under the same standing rule that governs every other part of this estate: minors’ data is consent-gated, school-owned, never sold, never shared with an outside marketing company, and never made public. That standing rule is not something this page activates early or claims is already running here -- it is the floor a future provisioning step would have to meet, stated now so it is not invented later under pressure to ship.
Should your building actually claim one
An honest reckoning, not a sales pitch
An earlier planning pass looked at whether a paid, branded publicschool.email address is a product worth building, and reached a plain NO. The reasoning is carried forward here rather than buried, because a page that only shows its best case is not the honest page the rest of this estate is held to.
For nearly every US public school building, the underlying need is already met at $0. Google Workspace for Education Fundamentals and Microsoft 365 A1 are the dominant free defaults for K-12 email, and a district running either one has almost certainly already given the building’s front office and every named staff member a working address at no marginal cost. Layering a second, paid, third-party domain on top of an address a building already has for free is not a sale against a gap -- it is a sale against a $0 incumbent, which is one of the hardest sales to make, because it asks a district to add a new vendor and a new student-data agreement for something it is not short of today.
Where a real gap might exist -- a records custodian’s public-facing address, or a PTA treasurer’s address that is legitimately not district correspondence at all -- a live, cheaper competitor already occupies exactly that niche: Forward Email sells branded-domain forwarding to schools and charter schools specifically, at $0 for forwarding-only and roughly $3-9 per month for a hosted tier with unlimited aliases and domains. Nothing on this page claims to already beat that offer on price or features, because it does not, today.
There is also a procurement cost this page will not paper over: adding ANY new paid vendor to a public school building, even one costing a few dollars a month, is rarely a one-click decision. It is a new-vendor procurement, and because student or family correspondence could pass through a claimed address, it would very likely also trigger a student-data-privacy agreement review by the district's own counsel or business office, under whatever state student-data-privacy law applies. That review has a real cost in staff time regardless of the sticker price of the product being reviewed, and it is a cost the $0 incumbents already inside the district's existing agreements do not carry. A wedge strong enough to be worth that review has not been shown to exist for this domain, and this page does not pretend that friction away.
What that leaves is narrow: this domain is a real, owned piece of the estate’s {charter, private, pre, public}school.email set, worth naming honestly rather than leaving dark or overselling. If a genuine wedge ever surfaces -- something a $0 incumbent and a $3/mo forwarding service structurally cannot match, backed by actual demand from building offices rather than an assumption of it -- that would be the trigger to revisit pricing and provisioning. Nothing on this page pretends that trigger has already happened.
If a building address were ever provisioned
What that step would actually require — named, not promised
This section describes what provisioning a real address on this domain would take if that decision were ever made. It is written to be precise about the work, not to imply the work is underway or scheduled, because it is not: nothing below is in progress today.
An MTA would need to be stood up or a hosted-mail provider bound to this domain, with a real MX record, SPF, DKIM, and DMARC configured so mail sent from a claimed address is not silently dropped or flagged as spam by the receiving side — the same infrastructure the estate's paid mailbox-brand family already runs for its six live .email hosts, extended to a seventh. A retention and abuse posture would need to be decided (how long a message is kept, who can read a desk's mail besides the person currently staffing it, what happens to that mail when a staffing change happens — the exact problem this domain exists to name). A consent and minors’-data policy specific to correspondence naming a student would need to be written down and enforced, not assumed. And a price would need to be set, weighed honestly against the $0 incumbents and the $3-9/mo competitor named above, because a price set without weighing those is not a real price, it is a number.
None of that is a promise that this will happen on any timeline. It is the honest list of what “provisioned” would mean if the founder-level decision to build it were ever made, so that decision is not made by accident through marketing copy that quietly implies the work is already done.
Questions people actually ask about this page
Doesn't our district already give the building a free email account?
For most public school buildings in the United States, yes. Google Workspace for Education Fundamentals and Microsoft 365 A1 are free, dominant defaults for K-12, and a district that already runs one of them has almost certainly already given the building's front office, attendance desk, and every named staff member a working address at no marginal cost. This page does not pretend otherwise. If the building's existing district-issued address already covers a desk on the list above, that desk does not need a second address -- the honest answer to whether your building needs this is, for most buildings, probably not solved by scarcity.
Then what would this actually be for?
A distinct, building-branded address for correspondence a district's internal system was not built to be the public face of -- most concretely, the public-records / sunshine-law desk, whose mail comes from residents and reporters who are not part of the district's directory at all, and the PTA/booster treasurer's mail, which is legitimately not district correspondence in the first place because a PTA is not a district employee. Those two desks are the strongest case on this list; the others (front office, attendance, family engagement, special services, safety, staffing) are largely already served by a district's existing system for most buildings, and this page says so rather than inflating the case.
Isn't there already a company selling exactly this?
Yes, one is named honestly here because leaving it out would make this section dishonest by omission: Forward Email already sells branded-domain email forwarding, including to schools and charter schools specifically, at $0 for forwarding-only and $3-9 per month for a hosted tier with unlimited aliases. That is a real, live, cheaper incumbent in the exact niche a shared publicschool.email subdomain would compete in. Nothing on this page claims to already beat that price or that feature set -- it does not, today.
So does the estate think this is a real product?
An earlier planning pass (HOME0A-fabASIC, 2026-08-30) reached a plain NO on funding this as a standalone paid product, for the reasons above: two $0 incumbents cover the default case, a live competitor already sells the narrow niche cheaper, and no measured demand for a third-party branded school-building address surfaced in that pass's search scope. This page carries that finding forward rather than hiding it. What survives is narrower: the domain is a real, owned piece of the estate's {charter, private, pre, public}school.email set, and this page states what it would be, honestly, without claiming a market that has not been shown to exist.
If I email one of the addresses on this page right now, what happens?
Nothing reaches anyone. This domain has no mail server, no inbox, no forwarding rule, and no DKIM or DMARC record provisioned. Every address above is a naming example of what a building's desk would be called, not a working mailbox. That is true today, unconditionally, for every address on this page -- not a caveat at the bottom, the actual current state.
Does this tie into publicschool.network's board governance or publicschool.software's records tools?
No, and this page is explicit about that rather than letting the family relationship blur into an implied integration. publicschool.network's elected-board governance, sunshine-law public portal, and attendance/ADA math are real, built, wired capabilities -- on that host, for a district that adopts that platform. publicschool.software's free publications editor and records back office are real and free -- on that host. A message addressed to [email protected] does not read, write, or touch either engine. The three hosts are siblings in the same family, cross-linked below; they are not one integrated product today.
What about student data in a message to specialservices@ or attendance@?
Because no mailbox is provisioned, no message sent to any address on this domain is received, stored, retained, or processed by us today -- which means no student's data reaches us through this surface at all. If a claimed address is ever provisioned in the future, any correspondence touching a specific minor would be handled under the same consent-gated, never-public, school-owned posture that governs every other part of this estate; nothing here changes that standing rule, and nothing here activates it early.
Could our building just ask its own district IT department for a role-based alias instead?
For most buildings, yes, and this page recommends asking that question first. Both dominant free incumbents (Google Workspace for Education and Microsoft 365 for Education) support role-based or shared mailboxes inside a district's own existing tenant at no additional cost. If a district's IT department is willing to set one up, it solves the staffing-turnover problem named above without adding a vendor, a student-data agreement, or a second domain to manage. This page exists for the case where that has not happened or is not going to -- not to talk a building out of the free option that already exists inside its own system.
Does claiming a publicschool.email address change anything about who owns the building's records?
No, and it would not even if a mailbox were provisioned. A building's public records stay the building's and the district's, governed by whatever state open-records statute applies, regardless of what address a records custodian's correspondence arrives at. Nothing on this page is a records-custody product, and nothing here would change who is legally the records custodian, what must be retained, or how a records request is fulfilled.
Is this page trying to talk me out of the idea?
It is trying to give an accurate account, which is not the same thing. The honest reckoning section states a real finding against funding this as a paid product today, and the FAQ names two free incumbents and one cheaper live competitor rather than pretending they do not exist. That is not the same as concluding no building anywhere would ever want this -- it is a refusal to claim a market that has not been shown to exist, on a page that is otherwise plain about what the idea is and what it would take to build it for real.
Why publish a page for something that is honestly not provisioned and honestly might not be worth building?
Because a domain the estate already owns should say plainly what it is, rather than sit dark or oversell a product that has not been shown to have a buyer. A resident who lands here after a records request, or a building office that is curious about the idea, gets an accurate account either way: what the address would name, what it would not do, who already gives most buildings this for free, and the one honest finding against funding it as a paid product. That is the complete, honest page for a domain at this stage -- not a promise, and not silence.
The rest of the family
Two sibling hosts, each with its own real product
publicschool.network — the elected-board governance and sunshine-law transparency front door, built for a public school DISTRICT: a policy manual with named roll-call votes, an unauthenticated adopted-only public records portal, and the real attendance/ADA math underneath it.
publicschool.software — the budget-stretched publications and records back office, built for a BUILDING or district office: a free yearbook/newspaper/online-edition editor, a one-time roster import, and an honest money model with a code-enforced cost floor.
This host, publicschool.email, is the identity layer between them: it names the desks a building runs without re-implementing either sibling’s engine. A building that wants the governance or records capability should look at the two hosts above; a building that is curious about a named address for its own desks is the audience for this page.
The closing ledger
What is true today, in one list
- True todaypublicschool.email is a domain the estate owns.
Confirmed against the owned-domain roster; nothing about ownership is honest-off. - Honest-offEvery address on this page is a working mailbox today.
No MTA, no MX record, no DKIM/DMARC, zero apps/api wiring. A message sent to any address on this page reaches nobody. - Honest-offA price exists for claiming a building address.
No catalog figure is shown because none has been set. No checkout exists on this page. - True of a sibling host, not this oneAn elected board's minutes, votes, and policy manual are real and built.
True of publicschool.network, a different host with its own render module and its own real API routes. Not reachable from an address on this domain. - True of a sibling host, not this oneA free publications editor and a records back office are real and built.
True of publicschool.software, a different host. Not reachable from an address on this domain. - True todayTwo free incumbents and one paid competitor already serve most of this niche.
Google Workspace for Education Fundamentals, Microsoft 365 A1, and Forward Email, named honestly in the FAQ rather than pretended away.
In short
Who this page is actually for
Not every visitor to this page has the same reason for being here. A records custodian or a PTA treasurer evaluating whether a named address would solve a real staffing-turnover problem for their one desk is the audience this page is most honestly useful to, because those are the two desks whose case survives the free-incumbent test above. A district IT director checking whether this domain duplicates something they should build themselves inside Google Workspace or Microsoft 365 is also well served here, because the honest answer for most of the other six desks is that it probably does, at $0, and this page says so rather than selling past it. And a resident or reporter who lands on this page after following a link from a records request is owed the plainest account of all: nothing here is a working address yet, and this page names that without apology.