Maintenance Switch Laravel Package

Product Decisions This Supports

• Feature Flagging for Maintenance Mode: Enables quick, UI-driven toggling of maintenance mode without manual code changes, reducing deployment friction for scheduled downtime or urgent fixes.
• Developer Experience (DX) Improvements: Accelerates onboarding for new developers by providing a self-service toggle for maintenance mode, eliminating dependency on backend deployments for testing.
• Security & Access Control: Supports custom secret tokens to bypass maintenance mode, useful for admins or support teams during critical incidents (e.g., "We’re live but hiding content for A/B testing").
• Roadmap for Admin Panels: Justifies investment in Filament Admin (if not already adopted) by offering lightweight, high-impact plugins that reduce custom development effort. Aligns with a strategy of modularizing admin tools.
• Build vs. Buy: Buy for teams prioritizing speed over customization. Build only if needing deeply integrated maintenance logic (e.g., per-route rules, dynamic messages).
• Use Cases:
  • Scheduled deployments (e.g., "We’re down for 10 minutes at 3 AM").
  • A/B testing (hide features for specific users without code changes).
  • Emergency fixes (flip a switch to isolate traffic during incidents).
  • Staging environments (toggle visibility of test data).

When to Consider This Package

• Adopt if:

  • Your team uses Filament Admin and needs a no-code toggle for maintenance mode.
  • You frequently perform scheduled downtime or require quick access control for admins.
  • Your maintenance mode is global (not route-specific) and doesn’t need custom branding/messaging.
  • You’re evaluating Filament and want to test its plugin ecosystem before committing.

• Look elsewhere if:

  • You need granular control (e.g., per-route maintenance, IP whitelisting, or dynamic messages).
  • Your stack isn’t Laravel/Filament (e.g., using Django, Rails, or a headless CMS).
  • You require enterprise-grade features (e.g., audit logs, multi-environment secrets, or SSO integration).
  • Your team prefers custom solutions over third-party plugins (e.g., for branding or deep integration).
  • You’re using Laravel Forge/Envoyer or another tool that already handles maintenance mode at the server level.

How to Pitch It (Stakeholders)

For Executives (Business/Operations)

*"This plugin lets us toggle maintenance mode with a single click—no more coordinating with DevOps for deployments or risking downtime during updates. For example, we can:

• Schedule maintenance (e.g., hide the site for 30 minutes during a database migration) without code changes.
• Isolate traffic during incidents (e.g., show a ‘We’re back!’ page while debugging).
• Reduce support overhead by giving admins a secret token to bypass maintenance for critical tasks. Cost: Free (MIT license), 10-minute setup. ROI: Saves 2+ hours/month in deployment coordination and incident response."*

For Engineering (Devs/Architects)

*"This is a Filament plugin that wraps Laravel’s built-in maintenance mode (php artisan down) into a UI toggle. Key benefits:

• Zero backend changes: Toggle maintenance via Filament’s admin panel (no CLI or config edits).
• Secret token support: Securely bypass maintenance for admins/support (configurable in config/maintenance-switch.php).
• Lightweight: ~50 lines of code, MIT licensed, actively maintained (last release: March 2025).
• Extensible: Hook into Filament’s global-search.before or customize the toggle UI (icon, placement, etc.). Tradeoffs:
• Not for per-route maintenance (use Laravel’s middleware instead).
• Limited theming options (but easy to override via Filament’s CSS). Recommendation: Use for global maintenance needs; pair with custom middleware for advanced use cases."*

For Product (PMs/Design)

*"This solves a pain point for reliability and testing:

• Faster iterations: Test features in staging without exposing them to users (toggle maintenance mode to hide/show).
• Controlled rollouts: Simulate downtime for A/B tests or canary releases.
• Incident response: Quickly isolate traffic during outages while debugging. Example pitch to stakeholders:

‘Imagine we’re testing a new checkout flow. With this, we can hide the old flow for 10% of users—no code deployments, just a toggle. For $0 cost and 15 minutes of setup.’"