- How do I install nafiswatsiq/subbase in a Laravel application?
- Run composer require nafiswatsiq/subbase, then php artisan subbase:install to publish the config and migrations, and php artisan migrate. Add the subscription trait to your User model and register SubbasePlugin::make() in your Filament panel provider. A pricing page is available out of the box via the x-subbase::plan-list Blade component. For updates use the subbase:upgrade command instead of subbase:install so existing migrations are not overwritten.
- Does Subbase work with Filament v3 or v4?
- No. Subbase requires Filament 5.0 or higher and is built as a Filament panel plugin. Teams on Filament v3 or v4, or on Nova, Livewire-only, or custom admin panels, get much less value because the admin UI is the main deliverable. In that case evaluate laravelcm/laravel-subscriptions directly and budget two to three weeks for custom UI.
- Which Laravel, PHP, and Filament versions does Subbase require?
- The stated floors are PHP 8.2+, Laravel 13.7+, Filament 5.0+, and laravelcm/laravel-subscriptions 1.8+. Those Laravel and Filament floors sit beyond the current stable release line, so verify installability on your stack before anything else. A short 30-minute install spike should be a blocking gate before you commit to the package.
- Does Subbase handle payments, invoicing, and recurring billing?
- No. Subbase is not a billing system: there is no payment provider integration, invoicing, proration, dunning, tax handling, or webhook reconciliation. It manages the plan catalog, entitlements, and subscription state, so actually moving money remains your responsibility. If your requirement is charging customers recurringly, treat Subbase as at most a third of the build, not the whole solution.
- How does multi-currency pricing work in Subbase?
- A plan can hold prices in multiple currencies, with currency and locale mapping configured in config/subbase.php. This is catalog pricing and display, not foreign-exchange conversion, settlement currency logic, or tax-per-region handling. If you need FX rates or audit-grade currency rounding, confirm those requirements before adopting.
- Can I use my own models with Subbase instead of the default ones?
- Yes. Model bindings, table names, and permission strings are externalized in config/subbase.php rather than hardcoded, so you can point the package at your own models that extend the base subscription models. This keeps the package adaptable if you already have subscription or plan tables in your schema. It also makes forking or patching behavior more straightforward.
- Does Subbase support promo codes and discounts?
- Yes. It supports percentage and fixed-amount discounts with validation, usage limits, and targeting to specific plans. The discount engine is homegrown by the same single maintainer, which makes it the most money-adjacent surface in the package. There are no documented guarantees around rounding rules, idempotency, or concurrency on max_uses, so review it carefully if financial audit requirements apply.
- Do I need spatie/laravel-permission to use Subbase?
- No, it is optional. Subbase works with spatie/laravel-permission when that package is installed and works without it otherwise, with permission strings configurable in the config file. That makes it usable in apps that manage roles and access differently.
- Is Subbase production ready, and does it have tests?
- Treat it as early-adopter territory. The package has a single maintainer, low download numbers, and no visible test suite, CI, or static analysis in the published materials, and you also inherit the maintenance posture of laravelcm/laravel-subscriptions. Be prepared to fork and maintain it under MIT if the maintainer goes quiet within twelve months.
- What are the alternatives to Subbase for Laravel subscription management?
- You can use laravelcm/laravel-subscriptions directly with your own Filament UI if you want fewer opinions and more control. If the real requirement is recurring revenue collection rather than entitlement gating, Laravel Cashier with Stripe or a dedicated billing platform is a better fit. Subbase makes the most sense when you already run Filament 5 and need plan catalogs, feature gating, and an admin panel quickly.