Moonguard Laravel Package

Product Decisions This Supports

• Build vs. buy for uptime/SSL monitoring: MoonGuard provides in-app Laravel-native uptime, SSL certificate, and (Pro) performance monitoring, letting us avoid standing up a third-party SaaS (Pingdom, UptimeRobot, Better Stack) for basic availability checks on client-facing sites we own and operate.
• Platform upgrade planning (Laravel 11): v1.2.3 updates the package's dependency constraints for Laravel 11, which directly informs whether MoonGuard can stay in the stack when we move the platform to Laravel 11. This is a green light for the roadmap; it does not, by itself, commit us to the upgrade path.
• Infrastructure/observability roadmap slot: decides whether monitoring lives as a first-party capability inside the admin panel (MoonGuard's model) or as an integration to an external incident-management vendor.
• Use cases: internal uptime dashboards for our own customer-facing apps; SSL expiry alerting to prevent certificate lapses; lightweight status pages; per-site performance trends where the Pro tier is licensed.
• Risk posture: the release is dependency-only (no API or schema changes), so it does not create migration, backward-compatibility, or data-shape workstreams for existing adopters.

When to Consider This Package

Adopt when:

• Our monitoring targets are URL endpoints we control, and we want alerts surfaced inside Laravel (notifications, admin UI) rather than in a separate ops tool.
• The team is Laravel-centric and values keeping dependencies and credentials in one application boundary rather than adding another vendor, SSO surface, and data-processing agreement.
• Requirements are availability plus certificate/expiry checks — the core value MoonGuard is built around — rather than deep APM (distributed tracing, log correlation, SLO error-budgeting).
• We're on, or migrating to, Laravel 11; v1.2.3 removes the dependency constraint as a blocker.

Look elsewhere when:

• We need synthetic transaction monitoring, multi-region probing, on-call rotation/escalation, or status-page SLA reporting — that's a dedicated incident vendor's territory, and MoonGuard would become a partial substitute.
• The monitoring domain is production-critical with strict uptime guarantees; a self-hosted in-app monitor shares failure domain with the app it watches.
• We need vendor support contracts or compliance attestations (SOC 2 reports from the tool vendor itself) — assess the Pro support terms explicitly.

How to Pitch It (Stakeholders)

For executives: MoonGuard is an open-source Laravel package that gives us built-in uptime and SSL-certificate monitoring inside our own applications. The v1.2.3 release is a maintenance update — it refreshes dependencies for Laravel 11 compatibility and patches a transitive dependency flagged by Dependabot. There are no breaking changes, no new features, and no migration effort. The practical value is that it keeps the Laravel 11 upgrade path unblocked and keeps our dependency scanning clean. Decision framing: this is a low-risk, low-cost option for basic availability monitoring, best used alongside — not instead of — a dedicated incident-management vendor if we need escalation, multi-region checks, or contractual SLAs.

For engineering: the release is dependency-only. [FEAT-132] updates Laravel 11 dependency constraints (PR #133); the follow-redirects 1.15.5 → 1.15.6 bump (PR #131) is a transitive/frontend-tooling patch. No public API, config, or database changes are indicated by the changelog. Verification work is limited to running the existing test suite on Laravel 11 in CI and smoke-testing the monitor scheduling and notification paths. Recommend pinning to ^1.2.3 and treating future releases as routine unless the changelog flags a breaking change or schema migration.