Shwanix Mailer Laravel Package

Product Decisions This Supports

• Cost Optimization: Replace SMTP-based email services (e.g., AWS SES, SendGrid) with a pay-per-use HTTP API (Shwanix), reducing fixed infrastructure costs for low-volume or sporadic email needs.
• Simplified Email Infrastructure: Eliminate SMTP server management (e.g., no need for dedicated mail servers, TLS certificates, or IP warming) for non-critical or transactional emails (password resets, notifications).
• Roadmap Flexibility: Adopt a vendor-agnostic mail driver for future-proofing if Shwanix’s API aligns with long-term strategy (e.g., migrating from SMTP to HTTP APIs).
• Build vs. Buy: Buy for teams lacking SMTP expertise or needing a lightweight alternative to self-hosted solutions (e.g., Mailgun, Postmark).
• Use Cases:
  • Internal tools with low email volume (e.g., admin dashboards, dev notifications).
  • Non-production environments (staging, local dev) where SMTP is overkill.
  • Legacy Laravel apps (7.30+) where upgrading SMTP dependencies is costly.

When to Consider This Package

• Avoid if:
  • High-volume emails: Shwanix’s API may lack scalability/guarantees for bulk sends (e.g., marketing campaigns).
  • Critical deliverability: No SMTP fallback; API downtime = failed emails. Requires redundant mailers (e.g., hybrid MAIL_MAILER=shwanix,failover=smtp).
  • Advanced features: No support for email templates, attachments, or webhooks (verify Shwanix API limits).
  • Laravel version mismatch: Only supports 7.30+ (PHP 8+) and 11+ (PHP 8.2+). Avoid for older stacks.
  • Compliance needs: No built-in DKIM/SPF management or GDPR-compliant logging.
• Look elsewhere if:
  • You need SMTP reliability (use Laravel’s built-in smtp driver).
  • You require enterprise-grade analytics (e.g., Mailchimp, Postmark).
  • Your team lacks API monitoring (e.g., no retries, dead-letter queues).

How to Pitch It (Stakeholders)

For Executives: "This package replaces SMTP with a serverless HTTP API for Laravel emails, cutting infrastructure costs for low-volume sends. Ideal for internal tools or non-critical notifications—think password resets or dev alerts—where reliability isn’t mission-critical. No SMTP servers to manage, and it integrates seamlessly with Laravel’s existing Mail facades. Risk: Limited to Shwanix’s API uptime; we’d pair it with a fallback mailer for production."

For Engineering: *"A lightweight Laravel mail driver that swaps SMTP for JSON POST requests to Shwanix’s API. Key benefits:

• Zero SMTP setup: No ports, TLS, or IP reputation to manage.
• Laravel-native: Works with Mail::send(), queues, and Mailables out of the box.
• Minimal config: Just set MAIL_MAILER=shwanix and publish the API key. Tradeoffs:
• No SMTP features (e.g., no DKIM, no local testing with log mailer).
• API-dependent: Add a failover mailer in .env for production. Next steps: Test with a staging environment and monitor Shwanix’s API SLAs."*