Kudosity

Kudosity — Burst SMS rebuilt as a customer-engagement platform, with the original API still underneath. Kudosity is the rebrand of Burst SMS, one of the longer-running Australian self-serve SMS APIs. The platform has moved upmarket into campaign management and customer engagement, but the underlying transactional API remains available with self-serve credentials and published pricing. Worth a look where a marketing UI for non-engineers and a programmatic path for the application both need to come from a single Australian account. Built by Kudosity (formerly Burst SMS). Founded 2009.

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 gives ground.

• Operating since — 2009, 7th of 11. SMSGlobal records 1999.

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. 22 of 26 tracked fields carry a value for Kudosity, 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. Kudosity 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 node, php, python) and MCP server (Partial against No). That pattern repeats across the rest of the roster — see Kudosity alternatives for the other rivals, each compared the same way.

Company

Kudosity (formerly Burst SMS)

Founded

2009

Fields we track

22 of 26

The rebrand pushed the product toward marketing teams, but the original transactional API is intact and self-serve. Pick it when the same account has to serve both the application and a non-technical campaign owner, which is a real requirement more often than engineers expect.

Operating since

20097th of 11

Inferred

Price /SMS @ 100k

A$0.032 /SMS4th of 8

Inferred

Self-serve API key

●Yes1st of 13

Inferred

Price /SMS @ 10k

A$0.045 /SMS4th of 8

Inferred

Carrier route

hybrid-direct2nd of 13

Inferred

Alphanumeric sender

●Yes1st of 13

Inferred

Delivery receipts

●Yes1st of 13

Inferred

AU legal entity

●Yes1st of 13

Inferred

Kudosity is the right call in these situations, each one drawn from a field we actually record:

• Products where marketing and engineering share a sending account.
• Teams wanting opt-out and list management handled by the platform.
• Long-running Burst SMS integrations that do not need to move.

Reach for something else when any of the following is a requirement rather than a nice-to-have:

• Operating since. Kudosity records 2009, 7th of 11 in the AU SMS APIs roster. SMSGlobal records 1999 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.

What we don't know. 4 of the 26 fields we track for Kudosity are still blank: Dedicated number, Min top-up, RCS and ACMA Sender ID. 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.