Bloomz alternatives for schools and districts
Most people arrive here for one of two reasons: the tier that contains the feature they need costs three times the tier they are on, or the product has stopped fitting a district that got bigger. Those are different problems with different answers, so this page sorts the field by pricing structure first and features second.
| Option | Pricing structure | What pushes the price up | Published? | Best fit |
|---|---|---|---|---|
| Kastr | Flat per student, one tier | Enrolment only — the rate falls as you grow | Yes | Districts wanting comms only at a readable, capped price |
| ClassDojo | Free to district; families monetised | Nothing for you; conversion pressure on families | Free is published; district add-ons are not | K–8 sites where teachers already use it and the board accepts the model |
| TalkingPoints | Free to teachers; district agreement quoted | District scope | Partial | Multilingual districts with thin budgets |
| ParentSquare | Tiered, plus four add-ons | Tier placement and add-on selection | No figure published | Districts wanting a suite with a website and payments included |
| Apptegy | Bundled contract | Bundle scope, rebrand and implementation work | No | Districts replacing website, app and comms together |
| Smore | Per user, plan-based | Number of staff creating newsletters | Yes | Single schools whose real requirement is a good newsletter |
| Bloomz (staying) | Four per-student tiers | Which tier holds the capability you need next | Yes | Districts using behaviour and PBIS features alongside comms |
Two of these are per-student flat, two are quote-only, one is per-user, one is free-to-district, and the incumbent is tiered. That distribution matters more to a small district's three-year budget than any feature column, because it determines whether a new requirement in year two produces a conversation or an invoice.
Six signals you have outgrown Bloomz
None of these is a criticism of the product. They are the points at which a classroom-first tool starts being asked to do a district-office job.
- A person needs two roles at once. A teacher at one school who is a parent at another, or an aide who is also a coach. When staff start keeping two accounts, the identity model has stopped fitting and every downstream record — audit, consent, opt-out — is now split across two people who are one person.
- Somebody asked for an audit trail and you produced a screenshot. The first records request or attendance appeal that needs "who was told what, when, on which number, in which language" is the moment a communications tool becomes a system of record.
- You want to drive sends from another system. Once the SIS, the transport system or a homegrown script should be triggering messages, you need a documented API with rate limits and signed webhooks, and a partner programme is not that.
- Consent state is being scrutinised. When counsel starts asking whether a number is validated, whether the household consented, and where the number came from, you need those as three separate recorded facts rather than one column called "phone".
- Tier drift. You are on the tier below the one you need for the third year running, and the annual upgrade conversation is now a budget line.
- Procurement wants transparency you cannot get. A board that has asked for a defensible market comparison needs vendors that publish, or comparables you can source. This is the one signal that argues for staying, since Bloomz does publish.
Where we are the wrong answer, named
Two profiles where a reader should close this tab and go elsewhere.
- A single elementary school, not a district. Our commercial model, our administrative surface and our pricing bands are all built for a district. More importantly, a K–5 school's real requirement is usually classroom texture — photos of the day, portfolios, behaviour recognition — and Kastr has no attachments, no photo or video sharing and no behaviour features. Stay with Bloomz, or look at ClassDojo. If your actual need is a good weekly newsletter with a bit of design, Smore is a better answer than either.
- A district whose primary requirement is a bundled website and mobile app. Apptegy and Finalsite compete on that ground and we do not build a CMS. Buying comms separately means two procurements, two renewals and two vendor relationships, and unless you have a specific reason to unbundle, the bundle is a legitimate choice.
Where we would argue: a district that wants messaging only, at a published rate with a contractual cap, with a real API, and with a tamper-evident audit trail. One tier at $3.50, $3.25 or $3.00 per student per year by enrolment band, everything included, no per-message fee, fixed 36 months with year four capped at the lesser of CPI-U or 5 per cent. And the honest counterweight: we are pre-launch with no single sign-on of any kind, no attachments, no push notifications, no native SIS connectors, no SOC 2 and no district references.
What actually has to move when you leave
Whichever alternative you pick, the migration work is dominated by four record classes, and only one of them is easy.
- People and relationships. Students, guardians and the link between them. Usually exportable, usually messy: duplicate guardians, junk names entered at enrolment, and phone numbers in six formats.
- Contact points with their state. The number is the easy part. Whether it is validated, whether the household consented, where it came from and which is preferred are the parts that carry the compliance weight, and they are the parts most likely to arrive as a blank column.
- Message history. Frequently the hardest, sometimes only available on request. Decide early whether you need it live in the new system or archived for records purposes; the second is much cheaper and is usually what the requirement really is.
- Groups and audiences. Almost always rebuilt by hand. Budget for it rather than being surprised by it in week three.
What our importer does and does not do. Kastr publishes an MIT-licensed importer that runs independently of us and, today, targets the ParentSquare export bundle rather than a Bloomz one. It parses the archive, normalises phone numbers to E.164, validates emails, maps languages, deduplicates contacts, drops guardian records named "mom", "dad" or "unknown", and emits a signed PDF receipt with a per-file SHA-256 manifest and a full ledger of what was dropped and why. It is a validator and a procurement artefact: it does not write a row into the database. For a Bloomz export the sensible route today is CSV into our roster API, with the same withdraw guardrail that aborts an import which would withdraw more than half your active records.
Questions people actually ask
What is the best alternative to Bloomz for a whole district?
It depends on what pushed you off. If the trigger was tier pricing, look at flat per-student vendors that publish a rate. If it was district-scale governance — multi-role staff, audit trails, consent records — look at district-grade platforms rather than classroom-first ones. If it was a website requirement arriving alongside comms, the answer is a bundle vendor and the comms decision should be made inside it.
Are there alternatives to Bloomz that publish their pricing?
Yes, though fewer than you would hope. Kastr publishes a per-student rate by enrolment band, Smore publishes per-user plans, ClassDojo publishes that its district product is free, and TalkingPoints publishes that it is free to teachers. ParentSquare, SchoolMessenger, Apptegy, Finalsite and SchoolStatus publish no dollar figure at all.
Which Bloomz alternative works best for a single elementary school?
Probably not a district platform, including ours. A single K–5 school usually needs classroom texture — photos, portfolios, behaviour recognition — which is exactly what ClassDojo does well and what a comms-only district tool does not do at all. If the real requirement is a well-designed weekly newsletter rather than messaging, Smore is a cheaper and better fit than either.
Do any alternatives avoid tiered pricing entirely?
A few. Kastr runs one tier at a published per-student rate with everything included, with the rate falling by enrolment band rather than by feature set. TalkingPoints is free to teachers as a non-profit. ClassDojo charges the district nothing at all but funds itself by selling a subscription to families, which is a different structure rather than an absent one.
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.