Vonage

Vonage — Ericsson-owned CPaaS with clean self-serve access and no Australian entity story. Vonage, formerly Nexmo and now part of Ericsson, offers straightforward self-serve access, published per-country pricing and solid SDK coverage. For Australian traffic it behaves as an international aggregator: rates sit in the same band as Twilio's, there is no Australian data residency position, and billing does not come from an Australian entity. Reasonable as a secondary or failover route rather than a primary Australian sender. Built by Vonage (Ericsson). Founded 2010.

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.

• SDK languages — node, python, php, ruby, java, dotnet, 4th of 12.
• Dedicated number — A$5 /mo, the best figure of the 3 here.

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.

• Carrier route — international-aggregator, 10th of 13. Telstra Messaging API records direct-carrier.
• AU data residency — No. MessageMedia records Yes.
• MMS to AU — No. MessageMedia records Yes.
• Price /SMS @ 10k — A$0.08 /SMS, 7th of 8. SMS Broadcast records A$0.032 /SMS.

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. 23 of 26 tracked fields carry a value for Vonage, 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. Vonage is ahead on Self-serve API key (Yes against Partial) and RCS (Partial against No). AWS End User Messaging takes AU data residency (Yes against No) and Ownership (hyperscaler against global-listed). That pattern repeats across the rest of the roster — see Vonage alternatives for the other rivals, each compared the same way.

Company

Vonage (Ericsson)

Founded

2010

Fields we track

23 of 26

Competent, self-serve and priced in the same band as Twilio without Twilio's documentation or its Australian invoicing entity. Its clearest use in an Australian stack is as a second route behind a local primary, not as the primary itself.

Carrier route

international-aggregator10th of 13

Inferred

AU data residency

○No12th of 13

Inferred

MMS to AU

○No9th of 12

Inferred

Price /SMS @ 10k

A$0.08 /SMS7th of 8

Inferred

Operating since

20108th of 11

Inferred

Price /SMS @ 1k

A$0.08 /SMS8th of 9

Inferred

SDK languages

nodepythonphpruby+24th of 12

Inferred

Self-serve API key

●Yes1st of 13

Inferred

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

• Failover routing behind an Australian primary provider.
• Existing Nexmo integrations with no reason to move.
• Teams that want self-serve access and do not need AU residency.
• SDK languages is your binding constraint. Vonage records node, python, php, ruby, java, dotnet, 4th of 12 in the AU SMS APIs roster. We define that field as first-party, vendor-maintained SDKs.
• Dedicated number is your binding constraint. Vonage records A$5 /mo, the best figure in the AU SMS APIs roster. We define that field as monthly rental in AUD for one dedicated Australian virtual mobile number, which two-way messaging requires.

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

• Carrier route. Vonage records international-aggregator, 10th of 13 in the AU SMS APIs roster. Telstra Messaging API records direct-carrier on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• AU data residency. Vonage records No on the AU SMS APIs table. MessageMedia records Yes on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• MMS to AU. Vonage records No on the AU SMS APIs table. MessageMedia records Yes on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• Price /SMS @ 10k. Vonage records A$0.08 /SMS, 7th of 8 in the AU SMS APIs roster. SMS Broadcast records A$0.032 /SMS on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• Operating since. Vonage records 2010, 8th 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. 3 of the 26 fields we track for Vonage are still blank: Min top-up, ACMA Sender ID and MCP server. 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.