Toggle Laravel Package

Product Decisions This Supports

• Decouple deploy from release: ship code dark and enable features by audience, reducing release risk and rollback time.
• Progressive delivery: support canary/beta cohorts, internal dogfooding, and percentage-based rollout for PHP/Laravel services.
• Kill switches: disable problematic features without redeploying, provided operational safeguards and ownership are defined.
• Plan/entitlement gating: use simple toggles for feature access by user, date, or condition — though not a replacement for billing or entitlement systems.
• Build-vs-buy for feature management: helps decide whether feature flags are strategic enough to buy a platform or tactical enough to self-host.
• Roadmap sequencing: enables smaller, safer releases and migration work without long-lived branches.
• Not a substitute for: experimentation analytics, remote config at scale, audit/compliance workflows, or customer-facing experimentation platforms.

When to Consider This Package

• You need lightweight, self-hosted PHP feature toggles with simple conditions and can manage configuration in code or app-owned storage.
• You are in a non-Laravel or legacy PHP service where a first-party Laravel option like Pennant is unavailable.
• You want MIT-licensed, no-SaaS procurement, and can wrap the library behind an internal FeatureFlags interface.
• You can accept tactical use cases: dark launches, beta access, internal cohorts, simple percentage/date/user rules.
• You can own testing, version pinning, and upstream monitoring — especially given the repository signals: 379 stars, 0 dependents, and a release date that should be validated.
• Look elsewhere if you need an admin UI, RBAC, audit logs, approval workflows, experimentation statistics, guaranteed support, or high-scale consistent bucketing.
• Prefer Laravel Pennant for Laravel-first teams wanting first-party integration; prefer Unleash, Flagsmith, LaunchDarkly, or ConfigCat for managed/enterprise feature management.
• Avoid as a critical kill-switch dependency unless you have strong operational safeguards and a migration path.

How to Pitch It (Stakeholders)

Executive summary: This is a low-cost, MIT-licensed feature-toggling library that can reduce release risk and enable progressive rollout without buying a feature-management platform. It is best treated as a tactical capability, not a strategic differentiator.

Recommendation: Run a time-boxed spike on one low-risk internal feature. Wrap the library behind an internal interface, document ownership, and define an exit plan. The main concerns are ecosystem maturity and integration risk — low dependents, no first-party Laravel integration, and release metadata that should be verified before adoption.

Engineering message: Evaluate against Laravel Pennant first. If qandidate/toggle is selected, isolate it, pin the version, add tests around toggle evaluation, and avoid deep coupling so migration remains cheap.