Thanks for your feedback Matt. I have optimised and updated the article (it’s been long over due), i hope you find it more useful in 2021. However, up until the time of this reply I still believe based on my research and hands on experience that if your a Tier1 looking for carrier grade full stack (voice, sms, video) CPaaS deployment the Restcomm platform remains to be the best choice. Why? While there are many really nice and promising CPaaS open source projects in 2021 that I like and support, they are still (to this point) missing the maturity and enough history in one or more components e.g API docs, SMS or Video etc.. Until they catch up it’ll be irresponsible for me to encourage a CSP to believe that they can be a reliable alternative to Twilio in all parts of CPaaS.

For the average developer who is building apps with Twilio, they want fast and easy alternatives they cannot use something like Restcomm middleware directly. I have listed some hosted commercial CPaaS alternatives for them like Nexmo, 8x8, Sinch, Unifonic etc..

For the developers who like to have more control over the CPaaS stack (code and routing), I have mentioned Jambonz Open Source Project that can be setup on your own infrastructure, I’m personally a big supporter of this idea (especially after the Facebook crash) as it moves the CPaaS layer to the edge instead of keeping it on hosted CPaaS provider infrastructure like Twilio, RC … but going this route you must have the tolerance and skill set to customise, operate your own CPaaS stack.