Their launch tagline was "Open source alternative to Twilio".
I just took a look at their repository(https://github.com/plivo/plivoframework) and it looks like it hasn't been updated since 2015 and the documentation has been down for long time(https://groups.google.com/g/plivo-users/c/ZuImvGKhnno/m/Uj-109PQCQAJ). I couldn't find any announcement that they have become closed source. I think I might have missed a conversation/announcement regarding this.
Some clarification on what you mean would be great.<p>When I look at their <i>organization</i> on Github I see quite a few active projects e.g. "Sharq" - SHARQ Server is an flexible, rate limited queuing system based on the SHARQ Core library and Redis. (<a href="https://github.com/plivo/sharq-server" rel="nofollow">https://github.com/plivo/sharq-server</a>) as well as client packages in quite a few languages.<p>Beyond that the documentation you referenced clearly points out that FreeSwitch (<a href="https://github.com/signalwire/freeswitch" rel="nofollow">https://github.com/signalwire/freeswitch</a>) is the telephony engine (<a href="https://web.archive.org/web/20130314113846/http://docs.plivo.org/get-started/" rel="nofollow">https://web.archive.org/web/20130314113846/http://docs.plivo...</a>) and the install script from the docs shows that their roots are in Pilvo being a Python web app (<a href="https://github.com/plivo/plivoframework/blob/master/scripts/plivo_install.sh" rel="nofollow">https://github.com/plivo/plivoframework/blob/master/scripts/...</a>). I also see a few Django applications in their repositories as well.<p>Thus, they open sourced their software. Are they open sourcing <i>all</i> of their software? Likely not. It could be that they open sourced much of their code and then got no contributions.<p>If they weren't receiving any contributions in alignment with their development, there would be no value for them to continue to have that distraction from running their business. It could also be that they didn't have the resources to _maintain_ external facing repositories, issues, and the communities around them.<p>Providing a more clear explanation of your expectations would help get you the best answer.