
Vue or React? What about both!
Choosing a frontend framework used to mean committing to a stack for the life of your project. Saucebase 2.0 changes that β ship with Vue 3 or React 19, and every module works either way.

Most software starter kits give you a locked box. You get the features, but you also get the constraints. Want to change how authentication works? Fork the package and maintain the fork yourself. Want to add a field to the billing model? Hope the package has an extension hook for that. Want to understand why something works the way it does? Read documentation, not source code.
Saucebase takes the opposite approach: copy-and-own.
When you install a Saucebase module, the source code lands in your repository under modules/. It's tracked in version control. It's yours to read, edit, extend, and break. There's no vendor lock-in, no abstraction layer between you and the code that runs your business logic.
This isn't a new idea β it's how Laravel itself recommends building things. Publish vendor files, customise them, own them. Saucebase applies that philosophy at the module level.
When a bug appears in your authentication flow, you look at modules/auth/app/Http/Controllers/. When you want to add a field to the billing portal, you edit modules/billing/resources/js/pages/. There's no mental overhead of figuring out which hook to use or which config key controls the behaviour you need. You find the code and change it.
When Saucebase ships improvements to a module, you don't get them automatically. But this is the right tradeoff. A module that runs your business should be something you understand and control β not something you blindly upgrade and hope nothing breaks.
The recipe system makes it trivial to scaffold new modules that follow the same conventions:
php artisan saucebase:recipe ModuleName
Your custom features get the same structure, the same patterns, the same copy-and-own philosophy. They feel like first-class citizens because they are.
This is the sauce. These are your recipes. Build on them.

Choosing a frontend framework used to mean committing to a stack for the life of your project. Saucebase 2.0 changes that β ship with Vue 3 or React 19, and every module works either way.

Every SaaS starts the same way: weeks of setup before you write a single line of real product code. Saucebase is the modular Laravel starter kit that skips that part.

One Artisan command scaffolds a fully structured module β service provider, controller, routes, Vue pages, migrations, factory, tests, and Vite config. Here's how it works.