Thanks for the clarification Anthony

My point was to thank you for mentioning us, and to agree with you as I feel I have a lot of experience on this topic.

To answer your new questions:

You mentioned in your earlier comment you were looking at how open source meets business. Being in a position to comment on this subject, I was pointing out that one of the places where it becomes necessary is the professional simplification and mainstreaming of complex technology.

Communications has been in the cloud since SIP and H323 made it possible on a grand scale at the turn of the century. No matter where you deploy it, it has to be reachable over the Internet to be of any use especially commercially.

The current notion of “Cloud Communications” is more about simplification and ease of access than anything else. Current solutions offer a gateway to send communications but not a true infrastructure to develop more meaningful products and services. You still have to do a lot of hard work yourself, not everyone wants that.

As for differences with SignalWire, that’s subjective but since you asked.

One of your opening points was said that some vendors offer open source clients and that’s not really a big deal in terms of open source. That’s a fact. Since we provide an open source core communications technology stack I think that’s a significant difference right away.

I would agree that yes, we expose Communications APIs and that’s a commonality in all SaaS models but if the features and functionality differ I think that’s actually a more significant factor.

API companies are supposed to be about developers and enabling them to be successful. I feel our history gives us an edge in this category when it comes to providing developers with not only communications APIs but infrastructure and solutions to problems.

Also as you well know being deep into WebRTC there is a whole new wave of ways to communicate and it will go well beyond making phone calls over PSTN.

Anthony,

I don’t really understand your point here. The end result is similar – isn’t it? To a large extent, SignalWire is CPaaS(T) 🙂

It might be different in the features and functionality it offers. It might be more complex or simpler. But at the end of the day, it exposes communication APIs in a hosted/managed/aaS manner.

Am I missing anything?

I am not sure either. I admit the punchline or takeaware here is somewhat hard to find 🙂

This one is more what my thoughts are around open source these days, and where open source meets businesses and marketers.