Sorry for the delay.
Americas: Chile, Brazil, Argentina, Mexico, Panama, Dominican Republic, Peru, Puerto Rico
Europe & Middle East: UK, Germany, Greece, Ireland, Poland, Portugal, Netherlands, Spain, Sweden, Finland, France, Austria, Bahrain, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Georgia, Hungary, Israel, Italy, Latvia, Lithuania, Luxembourg, Malta, Norway, Slovakia, Slovenia, Switzerland
Asia & Africa: Singapore, Vietnam, Hong Kong, Australia, New Zealand, Japan, South Africa
We are working on a blog post to do that as we speak you should have something within next 10 mins. Thanks for the patience.
With Plivo, it seems that I can get all the benefits of Twilio, at a better price, and it seems to be more open. Moreover, I can connect to it via SIP. And there are OSS libraries available to help me with that part.
Can you elaborate on that?
Then it's a question of volume to reach higher tiers / lower costs, and/or getting enough funding to sustain low margins at launch.
Twilio has both the volume and the funding. Hopefully Plivo can differentiate through innovation.
Plivo supporting SIP out of the box means I'm a lot more interested, independent of price. Supporting wideband (G.722) would be my other requirement.
welcome to the party
Think Cloud hosting for telephony :)
Noticed an interesting price thing with Twilio while comparing, which seems misleading to me... The big numbers on https://www.twilio.com/voice/pricing for the UK state 10c/min for mobiles, but lower down the smaller print shows that this price is only for a few prefixes (44751, 44754, 44759, 447500), and that most mobile numbers (all other 447) are 32c/min.
Also, I'm sure you've already considered it so probably no point me mentioning it, but would be interested if you could share your reasoning for not offering the free credit like Twilio do. As a single point of data, I signed up for Twilio and started playing around because of that offer (even though it meant putting a little in myself), despite having no use for it at the time. Without it I probably wouldn't have bothered, whereas now I'm someone who, while never had the need to spend more than a few dollars here and there with them, am happy using their service as my go-to whenever I need any voip/sms stuff.
"Plivo makes it to 50 countries in 30 days". and "In many countries, setting up a phone solution is challenging and involves negotiations with carriers, hardware, and network configuration." Wouldn't that mean the startup has been working for some time to reach that scale? no offense for the startup, but the article sounds biased. I do not trust an article overly emphatic with few details.
Because it'll be a lightly-edited version of a press release that was sent to VentureBeat by Plivo.
Honestly, we are just trying to make telephony easier across the globe. Its not a YC ad :)
Can you guys work on the documentation? It's unclear after a few minutes how the SMS API works other than sending a text.
And we can still scale as its needed.
I love that Plivo is concentrating on features and functionality that make building a scalable product easy. It's one thing dealing with the pain of scaling telephone infrastructure, but Plivo is allowing us to more easily scale our backend control infrastructure too (primarily though callbacks).
Not to mention that we are based in Australia, a country that is generally ignored by this type of service.
http://itre.cis.upenn.edu/~myl/languagelog/archives/004835.h...
