Weave Code
Filament Saas Laravel Package
a2insights/filament-saas
Filament SaaS provides scaffolding for building SaaS admin panels with Filament, including publishable migrations, config, and views to get subscription and team management wired into your app quickly. Install via Composer, publish assets, migrate, and extend from there.
Filament Saas for A2Insights
Frequently asked questions about Filament Saas
- How do I install a2insights/filament-saas in a Laravel app?
- Install it with Composer using composer require a2insights/filament-saas, then publish and run the migrations with php artisan vendor:publish --tag=filament-saas-migrations and php artisan migrate. You can also publish the config and views using the filament-saas-config and filament-saas-views tags. Because the package is a Filament SaaS template, confirm your app meets the Filament 4.x and Laravel requirements before installing.
- Does filament-saas support multi-tenancy with shared or separate databases?
- The package is designed as a Filament SaaS template, and the evaluation points to Laravel multi-tenancy approaches such as Stancl or Spatie Tenant. That suggests it can fit shared-database or separate-database tenant strategies, but the README does not document the exact tenancy model. Audit the published migrations and tenant middleware in the source before assuming a specific strategy.
- Which Laravel and Filament versions does a2insights/filament-saas require?
- The technical evaluation places the package on Filament 4.x with Laravel 10.x inferred from that Filament support. The README itself does not publish a detailed compatibility matrix, so check the composer.json constraints and Packagist metadata before installing. Apps on older Laravel versions should expect a major upgrade path.
- What migrations, config, and views does filament-saas publish?
- The documented publish tags are filament-saas-migrations, filament-saas-config, and filament-saas-views. Publishing migrations creates the SaaS-related tables, while the config file is currently shown as an empty array in the README. Views are optional and can be published when you need to override the Filament UI.
- Is a2insights/filament-saas production ready or still beta?
- Treat it as beta-stage: the evaluation notes that most releases are beta and that documentation is incomplete. Pin the package and its Filament dependencies to tested versions, review GitHub issues, and plan a rollback path before using it in production. A staging rollout with migration backups is prudent.
- How customizable are tenant onboarding and subscription flows in filament-saas?
- The package modularizes core SaaS concerns such as tenants and subscriptions, but the evaluation says customization hooks and extension points are not explicitly documented. Start by reading the service provider, published config, and migrations to identify events, middleware, and overridable classes. Expect to extend or override flows in application code rather than relying on documented hooks.
- Does filament-saas include Stripe or Paddle billing integration?
- The README does not document Stripe, Paddle, or any other billing integration, and the evaluation only raises them as possibilities to verify. Do not assume a billing provider is included; inspect the source and published config for payment or subscription provider code. If billing is present, confirm whether the provider can be swapped without forking the package.
- Can I use filament-saas with an existing Spatie Tenant or Stancl Tenancy setup?
- It may be possible, but migration and model conflicts are the main risk because this package publishes its own SaaS tables. Audit your existing tenants, subscriptions, and billing schema, then disable or adapt duplicate migrations before running the package migrations. Pin versions and test tenant resolution carefully in a staging environment.
- Where can I find usage documentation and examples for filament-saas?
- Usage documentation is a work in progress; the README includes installation and publishing commands but the Usage section is still marked TODO. For now, rely on the source code, tests, changelog, and GitHub issues for examples. Check the repository regularly because docs may improve as the package matures.
- How do I test and maintain a Laravel app using this Filament SaaS template?
- Run the package test suite with composer test and add your own feature tests around tenant provisioning, subscription changes, and admin panel access. Because the package is beta, pin Composer versions, monitor releases, and keep migrations reversible. Plan an upgrade review when Filament releases a new major version.
Weaver
How can I help you explore Laravel packages today?