Weave Code
Code base for Filament SaaS Template
Frequently asked questions about Filament Saas
- Does this package support multi-tenancy with separate databases per tenant?
- Yes, the package integrates with Spatie/Tenant, which supports both shared and separate database strategies. You can configure tenant isolation in the published config file. However, ensure your Laravel app’s environment is set up to handle database connections dynamically.
- Can I use this with Laravel 9.x or do I need to upgrade to Laravel 10.x?
- This package requires Laravel 10.x due to its dependency on Filament 4.x. If you’re on Laravel 9.x, you’ll need to upgrade first, which may introduce breaking changes. Test thoroughly after upgrading to avoid compatibility issues.
- How do I customize tenant onboarding flows (e.g., trial periods, welcome emails)?
- The package provides a modular structure for tenant management, but customization hooks aren’t fully documented. You’ll likely need to extend the published views or create custom Filament resources. Check the GitHub issues for community contributions or open a feature request for clearer guidance.
- What billing providers are supported (Stripe, Paddle, etc.), and can I switch them?
- The package doesn’t explicitly list billing providers in the README, but it’s designed to integrate with common SaaS billing systems. You may need to configure Stripe or Paddle manually or extend the package. Check the published config for provider-related settings or review the source code for hooks.
- Will this work if my Laravel app uses Livewire or Inertia.js instead of Filament?
- No, this package is tightly coupled with Filament 4.x for the admin panel. If you’re using Livewire or Inertia.js, you’ll need to rebuild the SaaS-specific UI/UX features manually or find an alternative package that supports your frontend stack.
- Are there performance concerns with tenant switching or Filament plugin overhead?
- Tenant switching performance depends on your database strategy (shared vs. separate). Filament plugins may add slight overhead, but the package is optimized for SaaS workflows. Monitor query logs and consider caching tenant-specific data to mitigate bottlenecks.
- Does the package include feature flags for tenant-specific access control?
- The package doesn’t explicitly mention feature flags in the README, but you can integrate it with Laravel Nova Features or Spatie Feature Flags by extending the published config or creating custom middleware. Review the source code for event hooks to customize logic.
- How do I handle audit logging for tenant actions like subscription changes?
- The package doesn’t include built-in audit logging, but you can implement it using Laravel’s built-in logging or packages like Spatie Laravel Activitylog. Listen for relevant events (e.g., tenant creation, subscription updates) and log them to a dedicated table.
- What’s the upgrade path if Filament 5.x is released, and will this package support it?
- The package is currently in beta and may not support Filament 5.x immediately. Monitor the GitHub repository for updates or check the changelog for compatibility announcements. Plan for potential breaking changes and test thoroughly before upgrading.
- Are there alternatives if I need a more flexible or documented SaaS solution?
- If documentation or flexibility is a concern, consider alternatives like **Spatie SaaS Starter Kit** (for multi-tenancy) or **Filament’s official SaaS plugins** (e.g., filament-shield for auth). Evaluate whether your team prefers a pre-built template or a more modular approach.
Weaver
How can I help you explore Laravel packages today?