What is Nexmo?
Who uses Nexmo?
Here are some stack decisions, common use cases and reviews by companies and developers who chose Nexmo in their tech stack.
Nexmo vs Twilio ?
Back in the early days at SmartZip Analytics, that evaluation had - for whatever reason - been made by Product Management. Some developers might have been consulted, but we hadn't made the final call and some key engineering aspects of it were omitted.
When revamping the platform, I made sure to flip the decision process how it should be. Business provided an input but Engineering lead the way and has the final say on all implementation matters. My engineers and I decided on re-evaluating the criteria and vendor selection. Not only did we need SMS support, but were we not thinking about #VoiceAndSms support as the use cases evolved.
Also, on an engineering standpoint, SDK mattered. Nexmo didn't have any. Twilio did. No-one would ever want to re-build from scratch integration layers vendors should naturally come up with and provide their customers with.
Twilio won on all fronts. Including costs and implementation timelines. No-one even noticed the vendor switch.
Many years later, Twilio demonstrated its position as a leader by holding conferences in the Bay Area, announcing features like Twilio Functions. Even acquired Authy which we also used for 2FA. Twilio's growth has been amazing. Its recent acquisition of SendGrid continues to show it.
We fall back to Nexmo when Chikka (https://api.chikka.com) and Semaphore (http://semaphore.co) have downtime or deliverability problems. Chikka and Semaphore are local (Philippine) SMS APIs handled by SMART and Globe, respectively, and report higher deliverability rates than Nexmo (at lower cost). Nexmo
- Inbound SMS
- Outbound SMS
- Outbound Text-To-Speech Calls
- Outbound VoiceXML Calls
- Inbound VoiceXML Calls
- Outbound SIP
- Inbound SIP
- Number Verification
- Number Insight