Weave Code
Filament Subscriptions Laravel Package
tomatophp/filament-subscriptions
Filament plugin for managing subscription plans and recurring subscriptions in Laravel admin panels. Define plans and features, assign subscribers, and control access from a clean Filament interface that plugs into your existing billing workflow.
Manage subscriptions and feature access with customizable plans in FilamentPHP
Frequently asked questions about Filament Subscriptions
- What is tomatophp/filament-subscriptions and how does it relate to laravel-subscriptions?
- It is a Filament plugin for managing subscription plans, features, subscribers, and recurring access inside Laravel admin panels. It layers Filament resources, pages, billing UI, widgets, and translations over laravelcm/laravel-subscriptions 1.8. The underlying library remains the domain engine for plans, features, subscriptions, and recurring periods, while this package supplies the admin surface.
- What are the requirements for installing filament-subscriptions?
- The documented stack fit is Laravel 12, PHP 8.2 or newer, Filament v5, and laravelcm/laravel-subscriptions 1.8. Filament v5 and laravel-subscriptions 1.8 are both required prerequisites, and there is no supported mixed-version configuration. Install it into an application that already meets those constraints before wiring it into your panel.
- Does filament-subscriptions support Filament v3?
- Version 5.0.0 targets Filament v5, and Filament v3 users are directed to a 1.x or v3 branch rather than a maintained release line. The plugin major version tracks the Filament major version, so your panel upgrade cadence becomes this dependency's cadence. Treat the v3 branch as branch-only support and do not assume backports.
- Does filament-subscriptions process payments or integrate with Stripe or Paddle?
- No, this package is in-panel subscription administration, not a payments platform. It does not provide a headless billing API or a payment-provider abstraction, so Stripe Billing or Paddle-style scope remains outside the package. It plugs into an existing billing workflow rather than replacing it.
- How do I install and set up filament-subscriptions?
- Meet the Laravel, PHP, Filament, and laravel-subscriptions prerequisites first, then require the Composer package and use its install scaffolding to publish and migrate. The install command now migrates before creating the main plan, removing a first-run ordering assumption that affected CI seeds, container init, preview environments, and fresh-tenant bootstrap. After installation, configure the subscription models and panel URLs your application uses.
- Can I customize the billing page URL and subscription models in filament-subscriptions?
- The billing page honors configured subscription models and resolves panel URLs and redirects, so you are not forced onto library defaults. That lets you wire billing behind your actual panel path. Test carefully if you use a non-default panel path, subdomain tenancy, or a reverse proxy with a path prefix, because URL resolution in those setups is an open question.
- What changed with the cancels_at column in filament-subscriptions?
- Renewal no longer writes the cancels_at column. Any report, export, dashboard, or downstream integration that reads it must be found and retired or updated. It is also open whether the migration drops the column or leaves it orphaned, and an orphaned column returning stale data can fail silently, so confirm the migration behavior and plan remediation for existing rows.
- How does translation auto-fill affect plan and feature edits?
- Plan and feature edits now populate every translation, which improves consistency but removes the ability to keep partial translations. Locales deliberately left blank will carry the source-language string, so demo content and content-ops workflows may change. Whether auto-fill overwrites non-empty translations or only fills empties is not confirmed, so verify before relying on manual translations.
- Is filament-subscriptions tested and production ready?
- Positive signals include a stated full test suite, URL and redirect fixes, billing page support for configured models, and an outside contributor. The main risks are major-version lockstep with Filament, branch-only prior-major support, the cancels_at migration question, and whether Laravel 13 is actually tested rather than only permitted by composer.json. Validate the package in your own CI against your exact Filament v5 minor and panel setup before production rollout.
- What alternatives should I consider to filament-subscriptions?
- If you want the same domain engine but your own admin UI, use laravelcm/laravel-subscriptions directly and build the Filament resources yourself. If you need payment-provider integration or headless billing, evaluate Laravel Cashier with Stripe or another billing platform instead. If entitlements also live in a feature-flag service, CRM, or warehouse, decide deliberately how you will reconcile them rather than discovering that work in QA.
Weaver
How can I help you explore Laravel packages today?