- How do I install Laravel Subby?
- Install it with Composer by requiring bpuig/laravel-subby in your project. Then publish the package's migrations and configuration with the vendor:publish command and run php artisan migrate. Laravel's package auto-discovery registers the service provider, so you normally do not need to add it to your config manually.
- Does bpuig/laravel-subby support Laravel 10?
- Yes. Version 7.0.4 added Laravel 10 support, so the package constraint will resolve on a Laravel 10 host where earlier 7.x tags would have failed. Before upgrading, confirm that the rest of your dependency graph also supports Laravel 10, since one package resolving does not guarantee the full tree does. Run a regression pass over service provider registration and facade aliases after the framework bump.
- Which Laravel versions does Laravel Subby support?
- The 7.x line targets modern Laravel releases, and 7.0.4 adds Laravel 10 to the supported set. The change is additive, so Laravel 8 and 9 support is not deprecated by it. Always read the composer.json constraint on the exact tag you intend to pin.
- How do I attach a subscription plan to an Eloquent model?
- Add the package's subscription trait to the model that should own subscriptions, then use the provided relationship and helper methods to assign a plan. Because the package is model-agnostic, the same trait works on User, Team, or any other Eloquent model. Plans are defined once and then attached with the dates and status your application needs.
- Can I define features per plan and check them in my app?
- Plans can carry a set of features describing what a subscriber gets. You define those features when creating a plan, then check them against a model's active subscription in your application code, such as policies, middleware, or Blade templates. This keeps entitlement checks out of your billing logic and in a single place.
- How do grace periods work in Laravel Subby?
- A grace period keeps a subscription usable for a configurable window after it lapses, so access is not cut the instant a period ends. The package supports grace periods as part of the subscription lifecycle and the window is configurable. This is useful for dunning flows or renewals where a short delay is acceptable.
- How do I handle plan changes, upgrades, and downgrades?
- Laravel Subby supports changing a subscription's plan without creating a brand-new subscription, so the history stays intact. Depending on your configuration, the change can take effect immediately or at the end of the current period. Test both paths if you prorate charges or gate features by plan.
- How should I test subscription logic built with Laravel Subby?
- Write feature tests against a real database and freeze or travel time with Carbon so period and grace-period logic is deterministic. Assert on subscription state and feature checks rather than on internal package tables, which keeps tests resilient to package updates. Because the package is Eloquent-based, model factories and RefreshDatabase work normally.
- Is Laravel Subby actively maintained?
- The project lives on GitHub as bpuig/laravel-subby and ships versioned releases, with 7.0.4 being a patch that added Laravel 10 support. That release was a single-contributor change, so review the repository's recent activity and open issues before adopting it for a long-lived product. Pin a version and watch for follow-up patches if you depend on Laravel 10.
- What are the alternatives to Laravel Subby for subscriptions?
- It depends on what you need: Laravel Cashier if you want a Stripe or Paddle payment integration out of the box, or a custom implementation if your billing rules are simple. Laravel Subby is a plan and subscription manager rather than a payment gateway SDK, so it pairs well with a billing provider you already use. Compare alternatives on provider lock-in, feature entitlements, and how much of the subscription lifecycle you want a package to own.