Weave Code
Saas Laravel Package
savannabits/saas
savannabits/saas is a Laravel package for building SaaS applications, offering scaffolding for plans, subscriptions, teams, and tenant-aware workflows so you can add recurring billing and multi-tenant features to your PHP app faster.
SaaS starter for FilamentPHP projects
Frequently asked questions about Saas
- How do I install savannabits/saas in a Laravel application?
- Install it with Composer using composer require savannabits/saas, then publish the package config and migrations and run php artisan migrate. Because the package builds on top of spatie/laravel-permission, confirm which Permission major version your app runs before you migrate. Do the install in a branch or staging environment first so guard, role-table, or migration conflicts surface before production.
- Does savannabits/saas support spatie/laravel-permission v6?
- Yes. Version 1.2.0 is a compatibility release that adds support for spatie/laravel-permission v6. The release notes only state that support was added, so check the Composer constraint to see whether v5 is still allowed alongside v6 or whether the package has moved exclusively to v6. If your app is still on Permission v5, upgrade Permission first or verify dual support before bumping the package.
- What Laravel and PHP versions does savannabits/saas require?
- The supported Laravel, PHP, and database versions are declared in the package composer.json, so run composer show savannabits/saas or check Packagist for the authoritative constraints. Compare those constraints against your app's Laravel and PHP versions plus your database driver. Because v1.2.0 is a dependency-alignment release, the spatie/laravel-permission constraint matters as much as the Laravel one.
- Can I use savannabits/saas for multi-tenant and team-scoped subscriptions?
- The package provides scaffolding for teams and tenant-aware workflows alongside plans, subscriptions, and feature gates. It fits monolithic Laravel apps using Eloquent, standard guards, and Blade, Inertia, or Livewire front ends. Fit is less clear for database-per-tenant models or custom authorization layers, where you should validate team scoping and guard behavior yourself.
- How do I upgrade savannabits/saas from v1.1.5 to v1.2.0?
- Pin savannabits/saas to v1.2.0 in a branch, update Composer, and compare published config and migrations against what you already have installed. Clear the permission cache, then run your authorization, plan enforcement, and team-scoping test suites. Deploy with a rollback plan and warm the caches again after release.
- Does savannabits/saas handle recurring billing and payment gateways?
- The package scaffolds plans, subscriptions, and feature gating so you can model recurring billing and tenant-aware workflows faster. Check the source and docs for whether a specific payment provider integration is included or whether you are expected to wire in your own gateway and webhooks. Review the plan and subscription models before assuming gateway behavior.
- What should I test after upgrading savannabits/saas to v1.2.0?
- Prioritize regression tests around role and permission checks, guard names, team-scoped permissions, and subscription feature gates. Add coverage for cache invalidation after role or permission changes, since stale permission caches are the most common post-upgrade failure. Run the suite in staging against a copy of production role data before deploying.
- Why are permissions stale or wrong after deploying a savannabits/saas upgrade?
- spatie/laravel-permission caches roles and permissions, so a deploy that changes roles, guards, or cache keys can leave nodes serving outdated authorization decisions. Clear the permission cache as part of your deploy routine and ensure multi-node deployments share a cache store. Re-run authorization tests after clearing the cache to confirm behavior.
- Is savannabits/saas suitable for headless or API-only Laravel apps?
- Fit is less clear for headless or API-only architectures, since the package targets conventional Laravel apps with Eloquent models, standard guards, and Blade, Inertia, or Livewire front ends. You can still reuse the plan and subscription models behind an API, but verify that its authorization and team-scoping assumptions match your token or guard setup.
- What are alternatives to savannabits/saas for Laravel SaaS billing?
- Laravel Cashier and Laravel Spark cover subscription billing, spatie/laravel-permission handles roles and permissions, and dedicated tenancy packages handle multi-tenancy. savannabits/saas combines plans, subscriptions, teams, and tenant-aware workflows with a FilamentPHP-friendly starting point. Evaluate it against your existing authorization stack, because overlapping role and permission layers add maintenance cost.
Weaver
How can I help you explore Laravel packages today?