This is incredible. I wish we developed mobile apps, because I'd jump right on this. I'm working on something similar for our web apps, but using the application logs (Rails) to develop "click paths" for a logged in user. We use Airbrake for error notification, and it collects a lot of useful data, but it doesn't tell us how the user managed to get to the point of failure.
Just a little piece of advice, I found really confusing that the different plans in Pricing section are ordered from the most expensive to the cheaper.
The video is nice. You do that in-house?<p>I'd be nice if there was a short description / value prop. statement above the fold. While your name implies what you provide, it's not 100% apparent what you are going to help me with and why it's better.