School communication platform comparison: twelve vendors, one matrix
Every vendor in this category publishes a comparison page in which it wins every row. This one is written by a vendor too, so apply the appropriate discount — but the discount you should apply is smaller if the matrix contains our own failures, and it does. Kastr loses eight rows below, four of them to every other vendor on the page.
| Vendor | Category | Owner | Publishes a price | Voice calls | Translation | District-governed account | Public REST API | SSO / MFA | Attachments & push | Sells to your families |
|---|---|---|---|---|---|---|---|---|---|---|
| ParentSquare | District suite | Independent | No | Yes | Yes | Yes | Partner programme | Yes | Yes | No |
| ClassDojo | Classroom-first | Independent (Tencent-led round) | Free to districts; add-ons unpriced | Announced | Yes | District console over classroom accounts | No | Yes | Yes | Yes — consumer subscription |
| Bloomz | Classroom + district | Independent | Yes — four tiers | From a paid tier | Yes | Yes | No | Unverified | Yes | No |
| SchoolMessenger | Mass notification | PowerSchool | No | Yes — the original strength | Yes | Yes | Within PowerSchool programme | Yes | Yes | No |
| Remind | Teacher messaging | ParentSquare | Free tier published; Hub quoted | Limited | Yes | Hub only | No | Hub only | Yes | No |
| Apptegy | Website + app + comms | Independent | No | Yes | Yes | Yes | Not published | Yes | Yes | No |
| Finalsite | Website-first | Independent | No | Yes (Messages) | Yes | Yes | Documented for CMS | Yes | Yes | No |
| Seesaw | Student portfolio | Independent | Plan structure published, figures quoted | No | Yes | District plan | No | Yes | Yes — core to it | Family plan exists |
| TalkingPoints | Translation-first messaging | Non-profit | Free to teachers; district quoted | No | Yes — the whole product | Narrower admin surface | No | Unverified | Limited | No |
| SchoolStatus | Comms + attendance analytics | SchoolStatus | No | Yes | Yes | Yes | Not published | Yes | Yes | No |
| Smore | Newsletters | Independent | Yes — per-user plans | No | Limited | School or district plan | No | Higher plans | Yes | No |
| Kastr | Comms only | Independent, pre-launch | Yes — $3.50 / $3.25 / $3.00 | Yes, with SMS→voice failover | DeepL-powered, previewable | Yes | 28 endpoints, MIT CLI and MCP | No — magic link only | No — neither is built | Never — prohibited at §9.4 |
Competitor rows are from each vendor's own public pages and from our internal competitor research, both read in August 2026. Where a column could not be verified from a public source it says so rather than guessing. Kastr's two red cells are not softened anywhere on this site: there is no SSO, SAML, OIDC or MFA of any kind, and no attachment, photo, video or push-notification capability. Add to those, off the table: no SOC 2 audit, no native SIS connectors, no auto-notice engine, no grade, school or route audience targeting, and no district references, because nobody is live yet.
How to read a matrix like this without being misled
Three habits, learned from watching districts get this wrong.
- A yes is not a capability, it is a checkbox. Every vendor above will answer yes to "translation". They mean materially different things by it: machine translation applied at send, translation with a human review path, a translation that the sender can read before a family does, or a link that opens a browser translate widget. Ask which, then ask to see it on a real message with a real name in it.
- Columns are not equally weighted, and the weights are yours. A district with a federated identity mandate should stop reading the SSO column and stop reading this page; it eliminates us outright. A district whose superintendent has been burned by a renewal cares about the pricing column more than about eight capability columns combined.
- The absence of a column is the tell. This matrix has no uptime column and no "families reached" column because neither can be verified from outside. Any comparison that carries those columns is reprinting vendor marketing, including when the number favours the vendor publishing the table.
Pricing transparency, scored
The single most predictive column above is whether a vendor publishes a number, because it determines how much of your evaluation budget goes on discovery rather than on evaluation.
| Vendor | Transparency | What is actually public |
|---|---|---|
| Kastr | Full | Per-student rate by enrolment band, the 36-month lock and the year-four cap, all on the pricing page |
| Bloomz | Full structure | Four per-student tiers with the capability boundary between them |
| Smore | Full for small buyers | Per-user plan pricing; school and district agreements quoted |
| ClassDojo | Partial | Free to the district is published. What families are charged is published. District add-on pricing is not. |
| TalkingPoints | Partial | Free to teachers is published; district agreements are quoted |
| Seesaw | Partial | Plan tiers are described; school and district figures are quoted |
| Remind | Partial | Free tier published; Hub pricing quoted, and the roadmap now runs through its acquirer |
| ParentSquare | None | Three tiers and four add-ons, no dollar amount anywhere, one "Contact sales" button under each |
| SchoolMessenger | None | Quote only, usually inside a wider PowerSchool commercial relationship |
| Apptegy | None | Quote only, bundled across website, app and comms |
| Finalsite | None | Quote only, across CMS, messaging and add-on modules |
| SchoolStatus | None | Quote only, enterprise motion |
Six of twelve publish nothing. That is not an accusation of bad faith — quote-only pricing is normal in public-sector software and there are real reasons for it — but it has a cost you should book: each quote-only vendor on your shortlist adds roughly two to six weeks of sales cycle before you hold a comparable number. Shortlist three of them and discovery alone can consume a term. The cost benchmark page covers how to shortcut that with public documents.
Six buyer archetypes, routed
Kastr is absent from three of these six, which is the honest distribution.
- K–8 district where teachers already live in a classroom app. Look hard at ClassDojo and Bloomz first. Displacing an adopted classroom tool to save money on a district platform usually fails, and it fails loudly. The question to settle before anything else is whether family monetisation is acceptable to your board.
- District replacing website, app and comms in one procurement. Apptegy and Finalsite. We do not build a CMS and are not going to; a comms-only vendor here means running two procurements and two renewals.
- District whose binding requirement is emergency mass notification. SchoolMessenger and the specialist notification vendors. Kastr has no emergency console, no two-person authorisation, and publishes no load-test or delivery-time figures. This one is a straightforward elimination.
- District with a federated identity mandate. Anyone with SAML or OIDC. Magic link is our only authentication method and there is no MFA. A district whose security policy requires federated staff login should not put us on the list.
- Multilingual district with a thin budget and a translation-first requirement. TalkingPoints deserves a serious look, and being a non-profit is not a small consideration for a district that has been surprised by a renewal.
- District that wants comms only, at a published price, with an API and an audit trail. This is the archetype we built for, and the one where we would argue hard. One tier, everything included, a 28-endpoint REST API with an MIT-licensed CLI and MCP server, a SHA-256 hash-chained append-only audit log, and a contract that forbids us ever selling to your families.
How each row was verified, and how to check it
Every capability row was set from one of three sources: the vendor's own public product or pricing pages, our internal competitor research file, or the vendor's public documentation. Rows we could not verify from a public source are marked unverified rather than inferred from a competitor's marketing.
Two consequences worth stating. First, this matrix will drift; vendors ship, and a cell that was accurate in August is not automatically accurate in March. Second, the fastest way to audit any row is the same as the fastest way to audit ours: ask the vendor to demonstrate it on your data in a trial tenant, not on their demo district. A capability that only exists on the seeded demo is a capability you will discover the truth about in October.
What we would put in your evaluation packet, in place of a vendor matrix. A one-page requirement list with weights your cabinet agreed before any demo, and a rule that no row is scored from a slide. Every vendor on this page, including us, is better at presenting than at being audited. The districts that get this procurement right are the ones that score from a trial tenant and a contract, and treat the matrix as a way to build the shortlist rather than to make the decision.
Questions people actually ask
What is the best school communication platform for a district?
There is no single answer, and any vendor giving you one is selling. The decision is usually made by three constraints rather than by a feature count: whether you are also replacing your website, whether emergency notification is in scope, and whether your identity policy requires federated single sign-on. Settle those three and the list of twelve collapses to two or three within an hour.
Which school communication vendors publish their pricing?
As of August 2026, Bloomz publishes four per-student tiers, Smore publishes per-user plans, Kastr publishes a per-student rate by enrolment band, and ClassDojo publishes that it is free to districts while charging families. ParentSquare, SchoolMessenger, Apptegy, Finalsite and SchoolStatus publish no dollar figure at all. TalkingPoints, Seesaw and Remind publish a free or entry tier and quote for district agreements.
What should a district shortlist look like for an RFP?
Three to five vendors, containing at most two that publish no price, and containing at least one that is a genuinely different shape from the others — a non-profit, a comms-only vendor, or an incumbent you would not otherwise consider. A shortlist of five near-identical suites produces five near-identical responses and tells your evaluation committee nothing.
Which platforms support SSO and MFA?
Most of the established district suites do — ParentSquare, SchoolMessenger, Apptegy, Finalsite, SchoolStatus, ClassDojo and Seesaw all support some form of federated or social sign-on. Kastr does not. Magic link is our only authentication method, there is no SAML, OIDC or MFA, and if your policy mandates federated staff identity that eliminates us before any other row matters.
Which platform is best for a district under 3,000 students?
Small districts pay the highest per-student rates in this market and have the least negotiating leverage, so published pricing matters more here than anywhere else. Bloomz's entry tier, TalkingPoints and Kastr are the three worth pricing first, because all three can be evaluated without a discovery call. If your requirement includes a website, that changes the answer entirely.
How often is this comparison updated?
It carries a reviewed date at the top of the page and is re-checked against vendor public pages when we revise the cluster. Treat any cell older than a school year as a prompt to verify rather than as a fact, and tell us if you find a row that has gone stale — corrections improve the page for the next district reading it.
One price. Every feature. Locked for three years.
$3.50 per student per year under 5,000 students. No tiers, no add-on modules, no per-message fees. Published on the site because you should not have to book a call to learn a price.