Muster

Muster watches your scheduled tasks and tells you when one stops reporting in. A nightly backup, an hourly import or a queue sweeper is supposed to run on a rhythm. When it quietly stops, nothing complains. Muster is the thing that complains.

Each task gets a monitor: a record of how often that task is expected to report in. Every time the task runs, it sends Muster a short message called a check-in. If a check-in does not arrive inside its window, Muster marks the monitor late, then missed, and can email you or call a webhook.

What Muster does and does not do

• It keeps one monitor per task, each with an expected cadence and a grace period.
• A connected Laravel application registers every one of its scheduled commands as a monitor on the command's first run, using the command's real cron expression and timezone. You register nothing by hand.
• It tracks starts, finishes, non-zero exits, skipped runs and runs that never finished.
• Each monitor can send email and webhook alerts, and you choose per channel which failures it carries.
• Every Monday it emails a digest of the previous week's failures, including an all-clear when there were none.

Muster is not a metrics store or a log store. It never reads or stores your task's output. It answers one question: did the thing report in on time?

How it fits with Scalpels

Scalpels installs Muster into your team's own GitHub and Laravel Cloud accounts. It forks the repository, provisions the database, managed queue and scheduler Muster declares, runs the migrations and deploys. See Install a product for how installs work in general.

Muster is an Experimental app in the catalog. Installing it through Scalpels is open to supporters and partner teams.

Muster is not a Scalpels provider. Scalpels does not attach your other apps to it; you connect each application yourself, from that application, as described in Connecting your apps.

In these docs

• Getting started covers what the install provisions, signing in and checking that the instance is really watching.
• Monitors explains monitor states, cadence and grace, and the screens for creating and editing monitors.
• Alerts and the weekly digest covers email and webhook alerts, the webhook payload and the Monday digest.
• Connecting your apps covers the Laravel client package and the plain HTTP heartbeat for everything else.
• Configuration lists the settings that affect a running Muster and a connected application.
• Use Muster from your agent describes the two read-only MCP tools.
• Troubleshooting lists the failures you are most likely to meet and what to do about each.

Want a branded address for this deployment? Use your own domain.