Kevin Hamilton was on a long flight, thinking about the damage that was caused when a third party API stopped sending a field of data that our platform relied on for social logins. Facebook had changed the way they returned names. The code failed, and our users couldn’t sign up. As he thought about how many other sites would be affected by this change, it became clear that there was a need in the market for a solution that could alert you of these issues when they happen.
He went about building the solution immediately. Plans were made and development began as soon as the plane landed. Once the system was ready for a private beta, it was introduced into his companies services. Revenue soared the following days as small nuances were discovered throughout the system. Once the dust had settled, there was a clear indication that the new website had delivered more than we had ever hoped for, and continues to do so to this day.
We believe there is nothing more valuable than data. The ability to interpret that data and extract meaning is not only incredibly powerful- it's the future. Our goal is to enable developers and companies an easy way to access that data in a way that allows them to make impactful decisions about their business.
We don't think it should be the end users who have to tell developers about bugs, errors messages or exception notices. We don't think users should have to find out how to contact developers. Developers don't want to take customer service calls, and management doesn't want them spending any more time doing customer support than they have to. With ErrorStream.com all of this simply goes away. Developers see errors as they happen, and can resolve the issue in minutes, not days, weeks or months. They can make educated decisions on when to rollback a release or they can decide what bugs should be prioritized. The roadmap for development becomes a lot more clear when you understand how your users interact with your code and the data that flows through it.