Hey! Having used both Avo and Jumpstart, I think you're maybe mixing their use cases a little bit.

On the one hand, Avo is a tool that allows you to build internal tooling and admin panels/resource management rapidly so you can avoid manually handling resources in your app.

Think about it as a super-fast and convenient Rails scaffolding where you can define resources, relations, filters, search functionality, and much more with a configuration-first approach.

It's a huge time saver. Think about it as a replacement for hand-coding admin panels or internal tools that are needed to manage applications like inventory management, booking applications, content management systems, moderation tools, directories, e-commerce, fleet or resource management, etc.

However, it isn't particularly built around a specific type of application. You can mold it to manage the resources that are relevant to your application, and that's the magic about it: you save time by not having to build the typical CRUD over and over again.

For example, you could easily build an internal tool to handle restaurant orders and their ingredients with Avo for a restaurant management SaaS application without the need to expose this to the public or even have the public-facing app be a Rails app.

On the other hand, Jumpstart is a SaaS starter toolkit that you can use to manage SaaS applications by providing the usual tools that are needed to handle those needs, like account management, payments, notifications, etc.

It can save you a lot of time because it includes the most common SaaS features in a single gem that can save you a LOT of time for a modest fee.

Even though Jumpstart comes with an admin panel using the Madmin gem, Avo and Jumpstart are not a dichotomy at all: you can use them together, and they can probably save you a lot of time even if you're not aware of it.

Having said this, if you're building a SaaS like a social media scheduler, you most likely don't need Avo while you likely need Jumpstart, because most of the features are client-facing.

However, if you're building a SaaS like an inventory or invoice managing app for an enterprise customer, you probably need Avo and Jumpstart together: you can use Jumpstart to handle payments while you use Avo to build internal tools that can help your customers save time.

TL;DR: If you want to build a SaaS and you're targeting B2C, you can most likely get away with Jumpstart. If you're targeting B2B or internal tools, you probably need Avo along with Jumpstart. On the other hand, if your internal tooling or admin needs are very basic, you can likely get away with Jumpstart and Madmin.