Weave Code
Spark Laravel Package
laravel/spark
Laravel Spark is a commercial SaaS scaffolding package for Laravel that provides subscription billing via Stripe or Paddle, team management, invoices, authentication, and admin tooling to help you launch recurring-revenue apps faster.
Laravel Spark is a commercial scaffolding package for building subscription-based SaaS applications on Laravel. It provides ready-made authentication, billing, and team management so developers can focus on product features instead of recurring billing infrastructure.
- Stripe and Paddle billing with subscriptions, coupons, and invoices
- Team management with invitations, roles, and member billing
- Authentication and profile management out of the box
- API token management and admin dashboard
- Customizable Vue-powered UI
Frequently asked questions about Spark
- What is Laravel Spark used for?
- Laravel Spark is a commercial Laravel package that scaffolds SaaS subscription billing, including plans, coupons, trials, invoices, team and seat management, and Stripe, Braintree, or Paddle payments. It is an opinionated application scaffold rather than a composable library: spark:install injects routes, controllers, Blade and Vue views, migrations, and config into your app and then expects to own authentication, billing, and the user dashboard. It fits greenfield Laravel 5.x monoliths selling seat-based subscriptions, not API-first products or existing domain-heavy applications.
- How do I install Laravel Spark with Composer?
- Spark ships through a private Composer repository, so installation requires valid license credentials in your auth.json or composer.json before Composer can resolve the package. The public laravel/spark repository is a thin installer stub; the substantive code is only available through the licensed channel. Running spark:install then publishes routes, controllers, views, migrations, and configuration into the host application.
- Does Laravel Spark support Laravel 11 or PHP 8?
- No. Spark's last release was in January 2018, targeting the Laravel 5.x line and PHP 7.1 through 7.3, with no PHP 8.x support. Upstream Laravel 5.x itself no longer receives security fixes, which is a compliance problem for SOC 2 or PCI DSS workloads. Running Spark on a modern Laravel 11 or 12 baseline is not supported and would require an extensive self-maintained fork.
- Can I still buy a Laravel Spark license?
- Spark has been retired as a commercial product, so acquiring a new license for a new project is effectively impossible. Even existing licensees depend on a private Composer channel that is no longer maintained. Before planning any work, confirm whether your team already holds a valid license and whether that private repository is still reachable today; if not, the evaluation ends.
- Is Laravel Spark still maintained?
- No. The last release was 2018-01-01 and the package targets Laravel 5.x on PHP 7.1 through 7.3. The bundled Cashier predates Stripe Payment Intents and SCA/3DS2, and the front end still uses Vue 2, which reached end of life in December 2023, plus Bootstrap 4 and Laravel Mix with webpack 3/4 and node-sass. Modern Node and OpenSSL builds typically fail before you touch any PHP.
- What payment providers does Laravel Spark support?
- Spark integrates subscription billing through Stripe, Braintree, or Paddle, built on the Cashier version of its era. That integration predates Payment Intents, SCA/3DS2 enforcement, and modern webhook semantics, so running it against today's Stripe API ranges from fragile to non-functional. Pinning an old API version buys time but does not make it safe.
- Does Laravel Spark handle SCA and 3D Secure 2?
- No. Spark's bundled Cashier predates Payment Intents and SCA/3DS2, which have been mandatory in the EU since 2019. Running it against current Stripe APIs is fragile at best, and API version pinning only delays the problem. If you need strong customer authentication, local payment methods, or tax handling, you will need a modern Cashier-based implementation.
- What are good alternatives to Laravel Spark?
- The recommended path is to treat Spark as a specification rather than a dependency: re-implement its billing state machine, including plans, coupons, trials, proration, seat quantity changes, invoice history, and team roles, on Jetstream or Breeze plus Cashier, Fortify, and a small entitlement service. That removes the license gate, the EOL runtime, and the front-end rot in one move. If you only need single-user subscription billing, Cashier alone covers it.
- Can I use Laravel Spark for an API-first or headless SaaS?
- No. Spark is an opinionated monolith scaffold that expects to own authentication, subscription billing, team and seat management, invoices, and the user dashboard, including Blade and Vue views. It does not fit API-first or headless products, existing domain-heavy applications, custom multi-tenancy, or usage-based and metered billing. It fits exactly one shape: a greenfield Laravel 5.x monolith selling seat-based subscriptions.
- How should I test or run Laravel Spark in CI today?
- Pin the entire stack into a container: PHP 7.3, Node 14, and Composer with the licensed repository baked into a private artifact registry so builds do not depend on a live credential. Rotating license credentials in CI/CD is an audit and secret-management burden most teams will not want. Testing is limited to that frozen environment, and you should verify whether your license even permits forking and patching before assuming you can self-maintain.
Weaver
How can I help you explore Laravel packages today?