Ben Curtis - Honeybadger, Breakwater
Quick Overview
Ben Curtis, co-founder of Honeybadger, explains that the company's origin was driven by a desire to build better developer tools and services than what was available, specifically citing the complexity of error reporting in the early web (pre-2005) and the need for a product that developers would pay for and that offered superior customer service compared to existing options like Airbrake.
Key Points: Ben Curtis co-founded Honeybadger, initially starting the project because he felt existing developer tools, like error monitoring, were inadequate compared to what was needed. The early development was heavily influenced by pre-web technologies like TRS-80 and BBS scenes, leading to a desire to build something new rather than relying on existing frameworks like Ruby on Rails or Node.js for error handling. A key motivator for Honeybadger was the realization that developers needed better visibility into application health, which led to creating an observability tool with its own query language (like BadgerQL) instead of relying on existing solutions. The founders decided against taking venture capital early on, preferring to bootstrap so they could maintain control over the product development and customer support experience, which they viewed as superior to competitors. Curtis notes that the initial development was challenging due to the lack of mature tooling, requiring them to build much of the infrastructure themselves, including Docker container support for self-hosting options. The product philosophy centers on being highly reliable and offering excellent customer service, which they see as a differentiator in a market where many tools are complex or difficult to self-host. Curtis advises fellow indie hackers to focus on building things they genuinely enjoy, even if they don't immediately see a clear path to massive revenue, as enjoyment sustains long-term effort.
Context: This is an interview segment from the DevTools.FM podcast, featuring Ben Curtis, co-founder of Honeybadger, an application performance monitoring service. The discussion centers around the origin story of Honeybadger, the technical and business decisions made by the founders, and their philosophy on building developer tools, contrasting their approach with the broader industry trends of the time, such as the rise of Ruby on Rails and early error monitoring tools.