- What is SubKit and what does it do in Laravel?
- SubKit is a Laravel subscription toolkit that provides package-owned models, migrations, Blade helpers, and a Filament admin UI for managing plans, features, subscribers, and trials. It is designed to accelerate early-stage SaaS billing when you already use Laravel with Stripe through Cashier and Filament for back-office administration. It is an accelerator, not a full billing platform, so complex pricing, tax, invoicing, and enterprise contracts remain outside its scope.
- Which Laravel, Filament, Cashier, and PHP versions does SubKit support?
- The provided materials do not list exact version constraints, so verify Composer requirements for Laravel, Filament, Cashier, PHP, and your database driver before adoption. Pin exact versions and test migrations for table-name collisions. Confirm compatibility in a disposable proof of concept, especially if your app uses an older Laravel or Filament release.
- How do I install SubKit in a Laravel app?
- Install via Composer, publish the package config and migrations, register the Filament plugin, and configure Cashier with your Stripe keys and webhooks. Then map Stripe products and prices to SubKit plans and pilot with Stripe test-mode subscriptions. For brownfield apps, reconcile existing subscriptions and schema before rolling out.
- Does SubKit wrap Laravel Cashier or replace its models?
- SubKit is described as using Stripe via Cashier, but the overview does not confirm whether it wraps Cashier or introduces its own subscription models alongside Cashier's tables. Treat this as a key integration question and inspect the package source and migrations before adopting it. Running it beside Cashier-native billing without a clear model ownership plan increases duplication and reconciliation risk.
- Can SubKit handle trials, coupons, proration, seats, usage billing, tax, and invoices?
- The package is positioned for simple plans, features, trials, and middleware access gating, not complex billing. The technical assessment flags coupons, proration, seats, usage billing, tax, invoices, refunds, and payment failures as areas to verify or handle with Cashier or another billing platform. Do not assume SubKit covers regulated or enterprise billing requirements without source-level validation.
- Does SubKit support multi-tenancy and custom billable models?
- Multi-tenancy and custom billable models are open questions in the technical assessment, not confirmed features. Verify whether SubKit supports tenant scoping, custom billable entities, and policy integration before using it in a multi-tenant SaaS. If not, you may need to fork or extend the package.
- How are Stripe webhooks verified and made idempotent in SubKit?
- The materials do not document SubKit's webhook verification or idempotency implementation. Because Stripe webhooks are critical, confirm how signatures are verified, how events are queued and retried, and whether duplicate events are handled safely. Test webhook behavior in Stripe test mode and with your queue configuration before production.
- How do I migrate existing subscriptions or entitlement mappings to SubKit?
- For existing billing, run a disposable proof of concept and then dual-run SubKit alongside your current entitlement logic, comparing access decisions before cutover. Map users or tenants to billable entities, seed plans and prices, and document a rollback to Cashier-native or manual billing. Brownfield adoption is harder due to schema collisions, tenant scoping, and existing subscription reconciliation.
- Are SubKit's Filament resources authorized by role or tenant?
- The technical assessment lists Filament resource authorization by role and tenant as an open risk, so do not assume built-in policy enforcement. Verify how SubKit's Filament resources integrate with Laravel policies, panel tenancy, and admin permissions. Add role-based access and audit logging before exposing the UI to internal staff.
- What are the maintenance, testing, and fork risks of using SubKit in production?
- SubKit has low adoption signals, likely single-maintainer risk, and open questions around test coverage, release cadence, and upgrade policy. Treat it as an accelerator rather than a billing platform, and be prepared to read source, patch issues, or fork under MIT if it becomes operationally critical. Assign a named owner, pin versions, and track Laravel, Filament, Cashier, and Stripe API upgrades.