AWS End User Messagingbaseline
SMS as an AWS primitive: no vendor relationship, but registration is a support ticket.Cellcast
Cellcast is australian-owned SMS provider competing mainly on published per-message price. We compare it in AU SMS APIs. It is 2nd of 8 on Price /SMS @ 100k (A$0.03 /SMS). The trade-off is being 13th of 13 on Agent-ready docs (2).
What is Cellcast?
Cellcast — Australian-owned SMS provider competing mainly on published per-message price. Cellcast is a smaller Australian-owned provider positioned on price and local support. Signup is self-serve with a published rate card, and the API is a straightforward REST endpoint with minimal ceremony. There is little SDK tooling and the documentation is thinner than the larger vendors', but for high-volume one-way notification traffic from an Australian entity the economics are among the best available without negotiation. Built by Cellcast Pty Ltd.
We track it in 1 comparison — AU SMS APIs — so every claim below is a cell in a table you can open and check rather than an impression. Across those rosters it sits against 12 other tools, and what follows is where it visibly separates from them.
Where it wins.
- Price /SMS @ 100k — A$0.03 /SMS, 2nd of 8.
Each of those is ranked against the whole roster on its category page, not against a hand-picked subset, so a first place here means first of everything we list.
Where it gives ground.
- Agent-ready docs — 2, the weakest of the 13 here. Twilio records 5.
- SDK languages — curl-only, 11th of 12. Twilio records node, python, php, ruby, java, dotnet, go.
None of these disqualify it on their own. They are the fields to check against your own requirements before you commit, because they are the ones where a competitor genuinely does better.
Provenance. 21 of 26 tracked fields carry a value for Cellcast, and 0 of those cite a document you can open. Nothing here carries a verification date yet, which is itself a reason to check before committing. Every figure keeps its own provenance — measured by us, claimed by the vendor, inferred, or community-reported — and we would rather print a dash than a guess.
Its nearest neighbour in our data is AWS End User Messaging. Cellcast is ahead on MMS to AU (Yes against No) and Carrier route (hybrid-direct against international-aggregator). AWS End User Messaging takes SDK languages (node, python, php, ruby, java, dotnet, go against curl-only) and Agent-ready docs (4 against 2). That pattern repeats across the rest of the roster — see Cellcast alternatives for the other rivals, each compared the same way.
At a glance
- Company
- Cellcast Pty Ltd
- Fields we track
- 21 of 26
Cellcast in AU SMS APIs
Ranked against 13 tools across 26 sourced fields. Open the full AU SMS APIs table.Among the cheapest published Australian rates from a locally-owned provider with self-serve access, which is a rare combination. Documentation and tooling are noticeably behind the larger vendors, so budget an afternoon rather than an hour for the first integration.
Where it lands in this roster
- Agent-ready docs
- 213th of 13 Inferred
- Price /SMS @ 100k
- A$0.03 /SMS2nd of 8 Inferred
- SDK languages
- curl-only11th of 12 Inferred
- Self-serve API key
- Yes1st of 13 Inferred
- Price /SMS @ 10k
- A$0.042 /SMS2nd of 8 Inferred
- Carrier route
- hybrid-direct2nd of 13 Inferred
- Alphanumeric sender
- Yes1st of 13 Inferred
- Delivery receipts
- Yes1st of 13 Inferred
When to use Cellcast
Cellcast is the right call in these situations, each one drawn from a field we actually record:
- Cost-sensitive one-way notification traffic at moderate volume.
- Buyers who want an Australian-owned supplier without a procurement process.
- Teams comfortable writing the HTTP call themselves.
- Price /SMS @ 100k is your binding constraint. Cellcast records A$0.03 /SMS, 2nd of 8 in the AU SMS APIs roster. We define that field as list price in AUD per outbound SMS segment at roughly 100,000 messages/month.
When not to use Cellcast
Reach for something else when any of the following is a requirement rather than a nice-to-have:
- Agent-ready docs. Cellcast records 2, the weakest of the 13 tools in the AU SMS APIs roster. Twilio records 5 on the same field. If that is a hard requirement rather than a preference, start elsewhere.
- SDK languages. Cellcast records curl-only, 11th of 12 in the AU SMS APIs roster. Twilio records node, python, php, ruby, java, dotnet, go on the same field. If that is a hard requirement rather than a preference, start elsewhere.
We publish this block because a comparison that only lists what a tool is good at is marketing. Every figure above sits on the same page as its source, and the field definitions are on the category tables if you want to check how we measured them.
Tools compared alongside Cellcast
Everything below shares at least one comparison category with Cellcast, ordered by how much overlap there is. For the reasoning on each — which fields it wins, which it loses — see Cellcast alternatives.Recent Cellcast changes
We have not logged a dated change for Cellcast yet. The timeline fills in as pricing moves, features ship and things get deprecated.Sources and gaps
What we don't know. 5 of the 26 fields we track for Cellcast are still blank: Dedicated number, Min top-up, Public status page, ACMA Sender ID and Operating since. Those render as dashes rather than as zeroes or assumptions, because an empty cell and a bad cell are not the same thing and only one of them is honest. If you know any of these figures and can point at a document, tell us.