PHPackages particle-academy/laravel-fms - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Utility & Helpers](/categories/utility) 4. / 5. particle-academy/laravel-fms ActiveLibrary[Utility & Helpers](/categories/utility) particle-academy/laravel-fms ============================ Laravel Feature Management System (FMS) for product feature entitlements and usage tracking v0.2(3mo ago)0711MITPHPPHP ^8.2 Since Jan 4Pushed 3mo agoCompare [ Source](https://github.com/Particle-Academy/laravel-feature-management-system)[ Packagist](https://packagist.org/packages/particle-academy/laravel-fms)[ RSS](/packages/particle-academy-laravel-fms/feed)WikiDiscussions main Synced 1mo ago READMEChangelogDependencies (5)Versions (3)Used By (1) [![Powered by Tynn](https://camo.githubusercontent.com/db5bfff78510a1a7471a9ad18c48da044e62a4bcd1661875963411643b84303e/68747470733a2f2f696d672e736869656c64732e696f2f656e64706f696e743f75726c3d687474707325334125324625324674796e6e2e61692532466f2532467061727469636c652d61636164656d792532466c61726176656c2d636174616c6f6725324662616467652e6a736f6e)](https://tynn.ai/o/particle-academy/laravel-catalog) Laravel Feature Management System (FMS) ======================================= [](#laravel-feature-management-system-fms) A standalone Laravel package for flexible feature access control and management. FMS provides simple, intuitive ways to control feature access using multiple strategies: Gates/Policies, config-based, registry-based, and database lookups. Features -------- [](#features) - **Multiple Access Control Strategies**: Gates/Policies, config files, feature registry, or database - **Boolean & Resource Features**: Support for simple on/off features and metered resource features - **Middleware Protection**: Protect routes based on feature access - **Facade & Helpers**: Clean API via facade and global helper functions - **Standalone Package**: Zero dependencies on other packages - **Laravel 12 Compatible**: Built for Laravel 11+ and 12+ Installation ------------ [](#installation) ``` composer require particle-academy/laravel-fms ``` The package will auto-discover and register its service provider. Configuration ------------- [](#configuration) Publish the configuration file: ``` php artisan vendor:publish --tag=fms-config ``` Define your features in `config/fms.php`: ``` return [ 'features' => [ // Simple boolean feature 'use-mcp' => [ 'name' => 'Use MCP', 'description' => 'Access to MCP-powered assistants and tools.', 'type' => 'boolean', 'enabled' => true, // or callable: fn($user) => $user->isPremium() ], // Resource feature with limit 'ai-tokens' => [ 'name' => 'AI Tokens', 'description' => 'Metered AI token usage per billing period.', 'type' => 'resource', 'limit' => 10000, // or callable 'usage' => fn($user) => $user->getTokenUsage(), // optional ], ], ]; ``` Usage ----- [](#usage) ### Using the Facade [](#using-the-facade) ``` use ParticleAcademy\Fms\Facades\FMS; // Check if feature is accessible if (FMS::canAccess('use-mcp')) { // Feature is enabled } // Check if feature is enabled (alias) if (FMS::isEnabled('use-mcp')) { // Feature is enabled } // Check if user has feature if (FMS::hasFeature('use-mcp', $user)) { // User has access } // Get remaining quantity for resource features $remaining = FMS::remaining('ai-tokens', $user); if ($remaining > 0) { // Allow action } // Get all enabled features $enabled = FMS::enabled($user); ``` ### Using Helper Functions [](#using-helper-functions) ``` // Get feature manager or check feature if (feature('use-mcp')) { // Feature is enabled } // Check feature access if (can_access_feature('use-mcp', $user)) { // User has access } // Check if feature is enabled if (feature_enabled('use-mcp')) { // Feature is enabled } // Get remaining quantity $remaining = feature_remaining('ai-tokens', $user); // Get all enabled features $enabled = enabled_features($user); ``` ### Using Middleware [](#using-middleware) Protect routes with feature requirements: ``` use ParticleAcademy\Fms\Http\Middleware\RequireFeature; Route::middleware(['auth', RequireFeature::class . ':use-mcp'])->group(function () { Route::get('/mcp', [McpController::class, 'index']); }); // Multiple features (OR logic - user needs at least one) Route::middleware(['auth', RequireFeature::class . ':feature1,feature2'])->group(function () { // Route protected by feature1 OR feature2 }); ``` ### Using Gates/Policies [](#using-gatespolicies) FMS automatically checks Laravel Gates if they exist: ``` // In AuthServiceProvider Gate::define('use-mcp', function ($user) { return $user->subscription->plan === 'pro'; }); // FMS will automatically use this gate if (FMS::canAccess('use-mcp')) { // Gate check passed } ``` ### Feature Registry [](#feature-registry) Register features programmatically: ``` use ParticleAcademy\Fms\Services\FmsFeatureRegistry; app(FmsFeatureRegistry::class)->register('custom-feature', [ 'name' => 'Custom Feature', 'type' => 'boolean', 'enabled' => fn($user) => $user->hasPermission('custom'), ]); ``` Access Control Strategies ------------------------- [](#access-control-strategies) FMS checks features in this order: 1. **Gates/Policies** - If a Gate exists with the feature name, it's checked first 2. **Feature Registry** - Checks registered features via `FmsFeatureRegistry` 3. **Config File** - Checks `config/fms.features.{feature}` 4. **Database** - If `FeatureUsage` model exists, checks database (extensible) Resource Features ----------------- [](#resource-features) Resource features support metered usage: ``` 'api-calls' => [ 'type' => 'resource', 'limit' => 1000, 'usage' => fn($user) => $user->apiCalls()->thisMonth()->count(), 'remaining' => fn($user) => 1000 - $user->apiCalls()->thisMonth()->count(), // optional ], ``` Requirements ------------ [](#requirements) - PHP 8.2+ - Laravel 11+ or 12+ Testing ------- [](#testing) Run tests using Pest: ``` pkg laravel-fms php vendor/bin/pest ``` Integration with Laravel Catalog -------------------------------- [](#integration-with-laravel-catalog) FMS integrates seamlessly with [Laravel Catalog](https://github.com/particle-academy/laravel-catalog) for feature-based product management. When both packages are installed, Catalog automatically configures FMS to use Catalog's `ProductFeature` model. ### Quick Integration Setup [](#quick-integration-setup) 1. **Install both packages**: ``` composer require particle-academy/laravel-fms composer require particle-academy/laravel-catalog ``` 2. **Configure FMS features** in `config/fms.php`: ``` return [ 'features' => [ 'manage-products' => [ 'name' => 'Manage Products', 'type' => 'boolean', 'enabled' => fn($user) => $user->hasRole('admin'), ], ], ]; ``` 3. **Use FMS in your Catalog controllers**: ``` use ParticleAcademy\Fms\Facades\FMS; use LaravelCatalog\Models\Product; class ProductController extends Controller { public function store(Request $request) { if (!FMS::canAccess('manage-products')) { abort(403); } $product = Product::create($request->validated()); // ... } } ``` ### Product Features Integration [](#product-features-integration) Catalog's `ProductFeature` model works with FMS to provide feature-based access control: ``` use LaravelCatalog\Models\Product; use LaravelCatalog\Models\ProductFeature; // Attach features to products $product = Product::find($productId); $feature = ProductFeature::where('key', 'advanced-editing')->first(); $product->productFeatures()->attach($feature->id, [ 'enabled' => true, 'included_quantity' => 100, ]); // Check feature access for user's subscription if (FMS::canAccess('advanced-editing', $user)) { // User has access via their subscription } ``` ### Subscription-Based Feature Access [](#subscription-based-feature-access) When integrated with Catalog, you can check feature access based on user subscriptions: ``` use ParticleAcademy\Fms\Facades\FMS; // Check if user's subscription includes a feature $user = auth()->user(); $subscription = $user->subscriptions()->active()->first(); if ($subscription) { $product = $subscription->product(); // Check if product has feature and user has access foreach ($product->productFeatures as $feature) { if (FMS::canAccess($feature->key, $user)) { // Feature is available } } } ``` ### Example: Feature-Gated Product Actions [](#example-feature-gated-product-actions) ``` use ParticleAcademy\Fms\Facades\FMS; use LaravelCatalog\Facades\Catalog; class ProductController extends Controller { public function sync(Product $product) { // Check if user can sync products if (!FMS::canAccess('sync-products', auth()->user())) { abort(403, 'You do not have permission to sync products.'); } Catalog::syncProductAndPrices($product); return redirect()->back()->with('success', 'Product synced.'); } public function create() { // Check remaining product creations $remaining = FMS::remaining('product-creations', auth()->user()); if ($remaining back() ->with('error', 'Product creation limit reached.'); } return view('admin.products.create'); } } ``` ### Protecting Catalog Routes [](#protecting-catalog-routes) Use FMS middleware to protect catalog admin routes: ``` use ParticleAcademy\Fms\Http\Middleware\RequireFeature; Route::prefix('admin')->middleware([ 'auth', RequireFeature::class . ':manage-products' ])->group(function () { Route::resource('products', ProductController::class); }); ``` For more detailed integration examples and patterns, see [INTEGRATION.md](INTEGRATION.md). License ------- [](#license) MIT ### Health Score 34 — LowBetter than 77% of packages Maintenance79 Regular maintenance activity Popularity5 Limited adoption so far Community9 Small or concentrated contributor base Maturity38 Early-stage or recently created project Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~16 days Total 2 Last Release 112d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/3af1e64dc359664cd7a3cc9f6f4030ec8bce17d587eff9f41a7ca84cfda2285a?d=identicon)[wishborn](/maintainers/wishborn) --- Top Contributors [![wishborn](https://avatars.githubusercontent.com/u/461446?v=4)](https://github.com/wishborn "wishborn (4 commits)") --- Tags laravelfeature-flagsfeature managemententitlements ### Code Quality TestsPest ### Embed Badge ![Health badge](/badges/particle-academy-laravel-fms/health.svg) ``` [![Health](https://phpackages.com/badges/particle-academy-laravel-fms/health.svg)](https://phpackages.com/packages/particle-academy-laravel-fms) ``` ### Alternatives [livewire/volt An elegantly crafted functional API for Laravel Livewire. 4195.3M84](/packages/livewire-volt)[whitecube/laravel-timezones Store UTC dates in the database and work with custom timezones in the application. 106106.2k](/packages/whitecube-laravel-timezones)[forxer/laravel-gravatar A library providing easy gravatar integration in a Laravel project. 4235.6k](/packages/forxer-laravel-gravatar)[iteks/laravel-enum A comprehensive Laravel package providing enhanced enum functionalities, including attribute handling, select array conversions, and fluent facade interactions for robust enum management in Laravel applications. 2516.7k](/packages/iteks-laravel-enum)[tomshaw/electricgrid A feature-rich Livewire package designed for projects that require dynamic, interactive data tables. 116.6k](/packages/tomshaw-electricgrid) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)