oss-fuzz VS awesome-saas-boilerplates

> because the ifunc code was breaking with all sorts of build options and obviously caused many problems with various sanitizers

for example, https://github.com/google/oss-fuzz/pull/10667

Have you tried Googles grpc fuzzer?

https://github.com/google/oss-fuzz/blob/master/projects/grpc...

https://www.fda.gov/medical-devices/digital-health-center-ex...

oss-fuzz: https://github.com/google/oss-fuzz :

> We support the libFuzzer, AFL++, and Honggfuzz fuzzing engines in combination with Sanitizers, as well as ClusterFuzz, a distributed fuzzer execution environment and reporting tool.

> Currently, OSS-Fuzz supports C/C++, Rust, Go, Python, Java/JVM, and JavaScript code. Other languages supported by LLVM may work too. OSS-Fuzz supports fuzzing x86_64 and i386 builds.

I love fuzzing as a technique and use it quite regularly, but running AFL++ on even a single program occupies all threads of a high end AMD server for weeks. I'm running it locally so only paying for the electricity. If it was a cloud instance it would cost a small fortune. I think this is a reason it is not used more widely.

I will note that Google have a programme for doing fuzz testing on open source projects using computer from their cloud: https://google.github.io/oss-fuzz/

Yes, mosh has fuzz tests in oss-fuzz [1].

[1] https://github.com/google/oss-fuzz/tree/master/projects/mosh

We will explore how Jazzer is used to automatically generate malicious inputs for Java programs, and how it compares to Symflower, which can automatically generate unit tests to uncover bugs and errors in your code. With the help of Jazzer, many bugs - some of them even in the OpenJDK - were found already. Also, as of March 2021, Jazzer is officially part of OSS-Fuzz, Google's cloud fuzzing engine. It should be noted that Jazzer is a pure "bug detection" utility that finds reproducers for errors in user code. Symflower can do the same, but provides additional functionalities to boost developer productivity, like generating high coverage unit tests and providing test templates for the software developer or tester.

Amazing to see more options in the market! Consider adding your solution to: https://github.com/smirnov-am/awesome-saas-boilerplates .

I'm obviously biased, so take what I say with a grain of salt, but I also probably know more about this space than ~anyone else. I'd say that your characterization is pretty accurate. There are many similar products to Pegasus (you can find a pretty comprehensive list here: https://github.com/smirnov-am/awesome-saas-boilerplates) but most of them are either more focused on infrastructure/setup (e.g. cookiecutter-django or - as you noted - far less mature/maintained (most of the others on that list).

Don’t worry about technology too much. Google for “SaaS boilerplate” and use one that suits your existing skills. Example: https://github.com/smirnov-am/awesome-saas-boilerplates

https://github.com/smirnov-am/awesome-saas-boilerplates collects such frameworks, it lists 4 for Rails.

If you end up building one, please add it to https://github.com/smirnov-am/awesome-saas-boilerplates

I think what you're describing is an entire product category, often referred to as a "SaaS boilerplate" or a "SaaS Starter". There are a huge number of them, and you can find lists of them on github as well as places like starter.place.

https://github.com/smirnov-am/awesome-saas-boilerplates There are also some golang based

Skip team features until a customer (or somebody ready to pay) is asking for it. In our B2B SaaS we have Fortune 100 companies as customers and even they are so far fine with individual accounts. We implemented two-factor-auth after customer requests but it's shocking how few of our users actually switch it on, definitely not relevant to grow or get more sales.

Start with a framework that includes authentication. It will save weeks of work. https://github.com/smirnov-am/awesome-saas-boilerplates

Good luck for your MVP/launch.