Kastr vs SchoolStatus: two different products with overlapping marketing
Both companies use the phrase "family engagement" and mean substantially different things by it. SchoolStatus starts from student data and works outward to intervention; we start from the message and work backward to whether it arrived. Knowing which problem you have prevents an expensive category error.
| Job | SchoolStatus | Kastr |
|---|---|---|
| Attendance analytics and intervention workflow | Core | Not built |
| Student data aggregation across systems | Core | Not built |
| Automated detection of at-risk students | Core | Not built — nothing raises an issue |
| Teacher call and contact logging | Yes | Message history only |
| Mass district notification | Yes | Yes |
| Two-way messaging with translation | Yes | Yes, previewable |
| Delivery queue guarantees | Not published in detail | Claim TTL, idempotency, SMS to voice failover |
| Tamper-evident audit chain | Not published | SHA-256 chained, append-only twice over |
| Public REST API and signed webhooks | Not published | 28 endpoints, HMAC webhooks |
| Published price | Quote only | $3.50 / $3.25 / $3.00 |
| Customers and references | Yes | None — pre-launch |
The first four rows are theirs outright and we are not building any of them. Row three deserves emphasis: Kastr has no automated data-health or at-risk detection at all — nothing in the product raises an issue on its own.
The genuine overlap is smaller than it looks
Two rows in that table are true duplication: mass notification and two-way messaging with translation. Everything else only appears to overlap because both companies describe their work as family engagement.
The distinction that matters in a procurement: SchoolStatus's value proposition is that it tells you who to contact and why, by pulling attendance, assessment and behaviour data together and surfacing patterns. Ours is that once you have decided to contact someone, the message reliably arrives, in a language they read, and you can prove afterwards exactly what was sent, by whom, to whom.
Those are complementary rather than competing, which is why the double-buy risk is real and specific. If you hold both, decide which one owns outbound messaging and turn the other's off. Two systems sending to the same families is how a district ends up unable to answer a simple question about what a parent was told.
What we do not do, stated flatly
Because our category names blur, it is worth listing our absences explicitly rather than leaving them to inference:
- No attendance analytics. We do not calculate chronic absenteeism, we do not tier interventions, and we do not produce an attendance dashboard.
- No automated data-health detection. Nothing in Kastr raises a data-quality issue on its own. Issues can be recorded and cleared, but they are not generated by the system, and we will not imply otherwise.
- No automated notice engine. Rules for attendance or lunch-balance notices can be configured; no engine currently fires them. It is on the roadmap and it is not in the product, and we will say that in a demo before you ask.
- No grade, school or route audience targeting. Audience resolution today handles specific people and everyone. The presets a district would expect are not shipped, and our API rejects them rather than silently sending to everybody.
- No native SIS connectors. No PowerSchool, Infinite Campus, Skyward, Aeries or Synergy integration. Roster data is POSTed to our API.
That is a substantial list and any of it may disqualify us. The reason we publish it is that the alternative is a district discovering it in week six of an implementation, which costs both of us more than a lost deal.
What we can substantiate instead
Our claim is narrow: the delivery and evidence layer, described precisely enough to be verified.
The queue claims work with SELECT … FOR UPDATE SKIP LOCKED under a five-minute claim TTL, performs network I/O outside the transaction, and enforces row-level idempotency keyed on broadcast, person and channel so a retry cannot double-send. Terminal SMS failures fail over to voice with the relationship recorded. Quiet hours default to 21:00–07:00 and only an emergency-flagged send, gated behind its own capability, bypasses them.
Underneath, per-organisation isolation runs on Postgres row-level security under a non-owner database role, failing closed when no organisation context is set, with cross-tenant leakage tested in CI against real Postgres. Every state-changing action lands in a hash-chained audit log that is append-only at both the role and policy layers.
On top, a 28-endpoint REST API, signed webhooks with an SSRF guard and automatic disable, and an MIT-licensed CLI and MCP server. If your reason for looking at a data platform is that you cannot currently evidence outbound communication, that is the part of the problem we solve, and it is genuinely a different part from the one SchoolStatus solves.
One observation, offered without malice. SchoolStatus ranks first for "school crisis communication plan" with a post from November 2023 that contains no actual templates. That is an accurate description of where the category invests: top-of-funnel content, and nothing that helps a buyer compare. We would rather compete on the comparison.
Questions people actually ask
Does Kastr do attendance analytics?
No. We do not calculate chronic absenteeism, tier interventions or produce attendance dashboards. We send and evidence messages. If attendance intervention is the problem you are solving, buy a product built for it.
Is SchoolStatus a communications platform or a data platform?
Primarily a data platform with communications attached. Its distinctive capability is aggregating student data to identify who needs contact and why. The messaging exists to act on that analysis rather than as the product's centre of gravity.
Can a district use SchoolStatus and Kastr together?
Yes, with one rule: decide which system owns outbound messaging and disable the other's. Our REST API and signed webhooks are built for that kind of coexistence. Two systems messaging the same families independently is how a district loses track of what a parent was told.
What does SchoolStatus cost?
They do not publish pricing; it is quoted, typically per student with modules. Public records requests to peer districts are the reliable route to a real figure. Our rate is published: $3.50 per student per year under 5,000 students, $3.25 to 14,999, $3.00 above that, everything included.
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.