Feature Flags Laravel Package

Product Decisions This Supports

• Feature Rollouts & A/B Testing: Enables gradual feature releases, targeted user segments, and experimentation without code changes.
• CI/CD & Deployment Safety: Safeguards new functionality behind flags during staging/production deployments, reducing risk of breaking changes.
• Maintenance Mode: Supports feature-specific maintenance toggles (e.g., disabling a broken module without downtime).
• Build vs. Buy: Avoids reinventing feature flag infrastructure; leverages a battle-tested, Laravel-native solution.
• Multi-Environment Control: Centralizes flag management across dev/staging/prod with configurable drivers (e.g., database, cache, or in-memory).
• Compliance & Auditing: Tracks feature access via debug logs and expiration handlers for regulatory needs.
• Query-Level Granularity: Extends Eloquent queries with whenFeatureIsAccessible() for database-level feature gating.

When to Consider This Package

Adopt if:

• Your Laravel app requires dynamic feature toggles (e.g., SaaS, platforms with user-tiered access).
• You need low-risk deployments (e.g., canary releases, dark launches).
• Your team lacks time/resources to build a custom flag system.
• You use Laravel 10+ and want seamless integration with routes, middleware, and queries.
• You require auditability (e.g., tracking which users accessed a flagged feature).

Look elsewhere if:

• You’re using non-Laravel stacks (e.g., Node.js, Django).
• You need enterprise-grade analytics (e.g., LaunchDarkly, Flagsmith) with advanced segmentation.
• Your flags require real-time sync across global regions (consider a dedicated service).
• You’re on Laravel <10 (use v1.x or migrate).
• You need a dashboard (this package lacks one; Flagfox is in beta).

How to Pitch It (Stakeholders)

For Executives: "This package lets us ship features safely—turning them on/off instantly without redeploying. For example, we can test a new checkout flow with 10% of users before rolling it out globally. It also reduces risk during deployments by hiding unfinished features behind flags. The cost? Zero—it’s open-source and integrates natively with Laravel. We’ll save dev time and avoid downtime from misfires."

For Engineers: *"ylsideas/feature-flags gives us a Laravel-native way to gate features at the code, route, query, and validation levels. Key perks:

• Zero reinvention: Handles caching, drivers (DB/cache/in-memory), and middleware.
• Dev-friendly: Fake flags in tests, debug access logs, and Eloquent query mixins.
• Future-proof: Supports Laravel 10–13 and has a roadmap for a dashboard (Flagfox).
• Lightweight: MIT-licensed, 600+ stars, and actively maintained.

Example use case: Disable a buggy API endpoint for specific users via Features::accessible('buggy-endpoint') in middleware. Or roll out a new UI to admins only with whenFeatureIsAccessible('admin-ui') in queries."*

For PMs: *"This aligns with our agile roadmap by enabling:

• Phased releases (e.g., roll out a subscription feature to early adopters first).
• Kill switches for critical bugs (e.g., disable a payment processor if it fails).
• Data-driven decisions (e.g., A/B test a new onboarding flow). No vendor lock-in—we own the flags in our codebase. The dashboard (Flagfox) is coming soon, but we can start today."*