Laravel Frontdoor Laravel Package

Product Decisions This Supports

• Roadmap Alignment: Enables a passwordless authentication feature for projects prioritizing frictionless user onboarding (e.g., SaaS, marketplaces, or apps targeting non-tech-savvy users). Aligns with trends toward zero-trust security and reduced credential fatigue.
• Build vs. Buy: Buy—avoids reinventing OTP/email workflows, caching logic, and session management. Ideal for teams lacking backend auth expertise or constrained by timelines.
• Use Cases:
  • Consumer apps (e.g., e-commerce, food delivery) where password recovery is a pain point.
  • B2B portals with low-frequency logins (e.g., vendor dashboards) to eliminate password resets.
  • MVP acceleration: Launch auth without schema migrations or complex infrastructure.
• Security/Compliance: Supports session-based identity (no persistent storage), reducing attack surfaces. Extensible for custom account providers (e.g., SSO, OAuth hybrids).
• Cost Efficiency: Eliminates need for third-party auth services (e.g., Auth0, Firebase) for simple email-based flows.

When to Consider This Package

• Adopt if:
  • Your primary auth method is email-based (no social logins required).
  • You lack a dedicated auth team or need to ship fast.
  • Database migrations are a bottleneck (cache-backed OTP avoids schema changes).
  • You prioritize simplicity over customization (e.g., no need for MFA, role-based access).
• Look elsewhere if:
  • You need multi-factor authentication (MFA) or phone/SMS support (this is email-only).
  • Your app requires scalable user profiles (no built-in user model; relies on sessions).
  • You’re using non-Laravel stacks (PHP framework lock-in).
  • High-security compliance (e.g., HIPAA) demands audit logs or persistent storage.
  • You need enterprise features (e.g., SSO, federated identities) out of the box.

How to Pitch It (Stakeholders)

For Executives: "Frontdoor lets us launch passwordless email login in days, not months*, cutting support costs from password resets while improving UX. No database changes or third-party fees—just drop-in Laravel integration. Ideal for our [target user segment], where friction kills conversions. Risk-free: MIT-licensed, cache-backed, and extensible for future needs."*

For Engineering: *"This package handles the heavy lifting of OTP generation, email delivery, and session auth—we just configure it. Key benefits:

• Zero migrations: OTPs live in cache, identity in sessions.
• Testable: Built-in testing driver for CI/CD.
• Extensible: Swap email providers or add custom account logic later. Tradeoff: Limited to email-only flows (but we can layer on other auth methods). Recommended for [specific project] where speed > customization."*

For Security/Compliance: "Session-based auth reduces persistent data exposure, and MIT license ensures no vendor lock-in. For [use case], this meets our baseline for passwordless flows. We’ll monitor cache eviction policies and email delivery reliability as part of QA."