Hey HN,<p>We’re Everest, Andrei and Sabera, the founders behind Fuzzbuzz (<a href="https://fuzzbuzz.io" rel="nofollow">https://fuzzbuzz.io</a>) - a fuzzing as a service platform that makes fuzzing your code as easy as writing a unit test, and pushing to GitHub.<p>Fuzzing is a type of software testing that generates & runs millions of tests per day on your code, and is great at finding edge cases & vulnerabilities that developers miss. It’s been used to find tens of thousands of critical bugs in open-source software (<a href="https://bugs.chromium.org/p/oss-fuzz/issues/list" rel="nofollow">https://bugs.chromium.org/p/oss-fuzz/issues/list</a>), and is a great way to generate tests that cover a lot of code, without requiring your developers to think of every possibility. It achieves such great results by applying genetic algorithms to generate new tests from some initial examples, and using code coverage to track and report interesting test cases. Combining these two techniques with a bit of randomness, and running tests thousands of times every second has proven to be an incredibly effective automated bug finding technique.<p>I was first introduced to fuzzing a couple years ago while working on the Clusterfuzz team at Google, where I built Clusterfuzz Tools v1 (<a href="https://github.com/google/clusterfuzz-tools" rel="nofollow">https://github.com/google/clusterfuzz-tools</a>). I later built Maxfuzz (<a href="https://github.com/coinbase/maxfuzz" rel="nofollow">https://github.com/coinbase/maxfuzz</a>), a set of tools that makes it easier to fuzz code in Docker containers, while on the Coinbase security team.<p>As we learned more about fuzzing, we found ourselves wondering why very few teams outside of massive companies like Microsoft and Google were actively fuzzing their code - especially given the results (teams at Google that use fuzzing report that it finds 80% of their bugs, with the other 20% uncovered by normal tests, or in production).<p>It turns out that many teams don’t want to invest the time and money needed to set up automated fuzzing infrastructure, and using fuzzing tools in an ad-hoc way on your own computer isn’t nearly as effective as continuously fuzzing your code on multiple dedicated CPUs.<p>That’s where Fuzzbuzz comes in! We’ve built a platform that integrates with your existing GitHub workflow, and provide an open API for integrations with CI tools like Jenkins and TravisCI, so the latest version of your code is always being fuzzed. We manage the infrastructure, so you can fuzz your code on any number of CPUs with a single click. When bugs are found, we’ll notify you through Slack and create Jira tickets or GitHub Issues for you. We also solve many of the issues that crop up when fuzzing, such as bug deduplication, and elimination of false positives.<p>Fuzzbuzz currently supports C, C++, Go and Python, with more languages like Java and Javascript on the way. Anyone can sign up for Fuzzbuzz and fuzz their code on 1 dedicated CPU, for free.<p>We’ve noticed that the HN community has been increasingly interested in fuzzing, and we’re really looking forward to hearing your feedback! The entire purpose of Fuzzbuzz is to make fuzzing as easy as possible, so all criticism is welcome.