Unofficial Voxeo Product Architecture


I just finished attending the Voxeo Summit 2010 and I came out completely blown away by the sheer amount of innovation going on with this company. Doing telephony is generally hard and most products out there make it boring but Voxeo —wow— they just bring it on every 6 months!

So for the uninitiated Voxeo prospect, here’s a diagram that I hope helps you figure out their how their products fit together.

Unofficial Voxeo Product Architecture

It’s all mostly about finding out what kind of development style do you want to follow. Here’s a decision tree:

  • I don’t want to program and my application is simple: Voxeo Designer and Evolution
  • I don’t want to program and my application is sophisticated: Voxeo VoiceObjects
  • I want to program:
  • ….. in XML: Prophecy and Evolution
  • ….. in a functional language such as Ruby or Python: Tropo
  • ….. a high concurrency full-fledged telephony service in Java: Moho
  • I just need a bunch of SIP or XMPP type-components: try PRISM
  • I want to build a web-based application with Ribbit-style telephony in Flash or Javascript: Phono
Tags:

Leave A Comment...