Laravel Jetstream and the official starter kits
Where it wins: it is free, it is first-party, and it will be maintained by the Laravel team for as long as Laravel exists. Jetstream already gives you authentication, two-factor, browser sessions, API tokens and teams with roles and invitations. If what you are building is not a subscription business, or you are happy writing billing and an admin panel yourself, a paid kit is money you do not need to spend. Start there.
Where Laraspring differs: billing, an admin panel with audited impersonation, presigned uploads, a translated product and a tenant boundary that is re-checked on every request rather than set at login. And the scaffolding difference is the one that shows up in year two: Jetstream publishes code into your application and it becomes yours to maintain, while Laraspring’s domains stay Composer dependencies that an upgrade replaces.
Larafast
Where it wins: breadth and time on the market. It is a mature commercial Laravel boilerplate with several payment providers, a long list of integrations and more than one frontend flavour, and it has been sold and supported for years. If you want the widest pile of pre-built marketing, blog and integration features, look there first.
Where Laraspring differs: it is narrower on purpose. Eight domains, each an installable package with its own isolated suite, instead of a large repository you copy and then diverge from. If your judgement is that a boilerplate’s real cost is the upgrade you can never take, that is the trade Laraspring is making.
SaaSykit
Where it wins: Filament. If you and your team already work in Filament, you get an admin experience out of the box that no hand-rolled panel matches, plus a plan and subscription setup you configure through a UI rather than in code. That is a genuinely faster path to an internal tool.
Where Laraspring differs: no Filament dependency, for better and for worse. The admin panel is ordinary Inertia pages in your own layout, behind one ability, which means less power and one fewer large framework to track. And the customer-facing product is a React application rather than Blade and Livewire.
supastarter
Where it wins: it is the polished reference for this category, and if your team writes TypeScript end to end, a Next.js or Nuxt monorepo is the coherent choice. Its organizations, billing and i18n are the shape Laraspring is aiming at, and its documentation is excellent.
Where Laraspring differs: it is not a competitor so much as the other side of a language decision. If you want Laravel, Eloquent, queues, Cashier and PHP hosting, supastarter is not for you no matter how good it is. If you want the whole product in TypeScript, Laraspring is not.