Laravel Health Check Laravel Package

Product Decisions This Supports

• Serverless migration go/no-go. If Bref/Lambda is on the roadmap for the Laravel app, this package supplies a Lambda-native health signal — the missing input for deciding whether the migration is production-safe or needs another quarter of hardening.
• Build vs. buy on observability glue. The alternative is hand-rolling health-check Lambdas, CloudWatch alarms, and SNS/Slack routing. A thin MIT package from the Bref maintainer is a cheap bet against weeks of undifferentiated plumbing work.
• Turning "healthy" into a product spec. Adopting a health-check surface forces the team to name the critical path — database, cache, queue, object storage, secrets, outbound APIs — and to decide which failures page someone versus which degrade silently. That artifact outlives the package.
• Release gating and rollback policy. A synthetic invocation after deploy gives you a concrete gate for canary or blue-green cutover, and a defensible trigger for automatic rollback.
• SLO and on-call investment. Health-check output feeds error budgets, paging thresholds, and the decision to publish a customer-facing status page.
• Vendor coupling / packaging. Because the package is explicitly scoped to work with bref.cloud, adopting it is also a de facto decision to evaluate the paid Bref platform — treat that as a separate line item, not a freebie.

When to Consider This Package

Adopt when all of these hold:

• The Laravel app runs (or is about to run) on AWS Lambda via Bref — outside that context the package has almost no value.
• You need health semantics that respect Lambda realities (cold starts, container reuse, invocation-scoped execution) rather than an ALB polling /up.
• You are open to or already evaluating bref.cloud; the README points there directly.
• The team has limited ops bandwidth and prefers an official-maintainer artifact over bespoke scripts.
• An MIT license and a small, replaceable surface area satisfy procurement.

Look elsewhere when:

• You are on ECS, Fargate, Kubernetes, Forge, or Vapor — use spatie/laravel-health or Laravel's built-in /up route.
• You need deep APM, tracing, or log correlation — that is Sentry/Datadog/New Relic territory, and no health-check package substitutes for it.
• You want zero vendor coupling to a commercial platform.
• You need a broad, extensible check catalog today; this is a narrow companion, not a framework.

Adoption caveat to state plainly: 1 star, 0 dependents, README-and-releases-only maturity. That is expected for an end-application companion package rather than a library, and Bref's maintainer reputation is the real trust anchor — but pin the version, wrap it behind a small internal interface, and keep the exit ramp cheap.

How to Pitch It (Stakeholders)

For executives: We are considering a small, free, MIT-licensed package maintained by the Bref project that adds health checks to our Laravel app on AWS Lambda. The business case is risk reduction, not features: it tells us quickly and automatically when the serverless app is broken, so we catch outages before customers do and can roll back releases with confidence. It is a low-cost, reversible decision — a few days of engineering, no license fee — and it de-risks the larger serverless roadmap decision. The one thing to note is that it is designed to pair with Bref's commercial cloud offering, so it is also an early look at that vendor.

For engineering: First-party Bref health checks for Laravel on Lambda, MIT, thin surface area, purpose-built for invocation-scoped execution rather than ALB polling. It gives us a post-deploy gate and a paging signal without building our own probe Lambdas. It is early — single-digit stars, no dependents, README-level docs — so treat it as a spike: pin the version, wrap it behind one internal interface, and confirm it detects the failures we actually care about (DB, cache, queue, secrets) before it lands in the deploy pipeline. Ask: two days to evaluate, and a written recommendation on whether health-check ownership sits with this package or with our existing APM.