Switchyard

Know when a failed job will make you miss a deadline.

Switchyard monitors your cron jobs, pipelines and backups. When one fails or runs late, the alert tells you which deadlines depend on it and the latest time it can be fixed. Plan launches as tasks linked to those jobs, and see what a delay would do to the date before you commit.

Free for 20 checks and 5 people. No card needed. Setup is one curl line in your crontab.

What if the job runs late?

Illustrative
  1. Warehouse loadscheduled job · pings each night
  2. Prepare reporttask · starts after the load
  3. Customer export 09:00deadline · due 09:00

Export ready08:40

Covered by spare time0 min

Past the deadline0 min

Illustrative example with 20 minutes of spare time before a 09:00 deadline. In the app, what-ifs use your own jobs, tasks and dates, and never change your plan, checks or alerts.

From a failed job to the deadline it affects

Next Live board
  1. Your jobs report in. Each cron job, pipeline or backup pings a URL when it starts, finishes or fails. Switchyard knows its status from the job itself, not from someone updating a ticket. Websites can be checked on a schedule instead.
  2. Link jobs to the work that needs them. Give a job a deadline (“by 09:00 daily”), or make a launch task wait on it. Tasks can also wait on other tasks.
  3. See the risk as soon as a job stops. Switchyard shows which deadlines and launches are now at risk, how much spare time is left, and the latest time the job can be fixed and still make it.
  4. Try a delay before you decide. Pick one or more jobs or tasks, push them back, and see where every date lands. Nothing is saved until you change the plan yourself.

How the app draws it

  • Each launch is a line. Its tasks are the stops, and its launch date is the end of the line.
  • A job a task waits on joins the line. Its pings show when it last ran.
  • Dashed marks are projections. Where the dates are expected to land, never what has already happened.
  • A red diamond is a failed job. Everything after it on the line is held up.

A live board for a spare screen

Next Status page

Every job is a row that updates the moment it pings. When a job misses its schedule, the row turns late, then down once its grace period runs out. The board updates on its own, so you can leave it open on a spare screen.

Departures 4 checks
Queue consumer every 30 seconds
Up
Invoice sync every 5 minutes
Up
Search index rebuild every hour
Up
Cache warmer every minute, staging
Up
  • Ping, run finished
  • Run started
  • Run failed
  • Down: no pings
Illustrative simulation, sped up so a few minutes pass in half a minute. Invoice sync misses its schedule: Switchyard marks it late, then down once the grace period runs out, and sends an alert. When it pings again, you get a recovery alert.

A status page your customers can read

Next Slow runs

Choose which checks are public and share one link. Anyone can see their current status and 90 days of daily uptime without signing in.

Service status /status/acme

All systems running

Queue consumer99.93%
Invoice sync99.96%
Nightly database backup100.00%
90 days agoToday

Catch slow runs before they turn into missed deadlines

Next Alerts

Ping /start when a job begins and Switchyard times every run. After eight runs it learns the job’s usual run time, and flags any run that takes one and a half times as long or more. Deadline projections use the same usual run times.

Search index rebuild ran slow 9 min 6 s. Usually 4 min.

Alerts by email, Slack, Discord or webhook

Next Setup

Send alerts to email, Slack, Discord, or your own endpoint (signed with HMAC-SHA256). You get one message when a job goes down, one when it recovers, one for a slow run, and one when a deadline can no longer be met. A down alert names the deadlines it blocks and the time the job must be fixed by. Failed deliveries are retried.

POST your endpoint
X-Switchyard-Signature: sha256=5c0e91…a7
Content-Type: application/json

{
  "event": "check.down",
  "occurredAt": "2026-09-22T03:14:08Z",
  "impact": "Blocks Customer export (09:00 UTC): must finish by 08:54 UTC.",
  "check": {
    "name": "Nightly database backup",
    "status": "down",
    "tags": ["prod", "db"]
  }
}

Setup is one line in your crontab

Next Pricing

Add a curl after the command you already run. Send the exit code so a failure is flagged straight away, and post the job’s output to keep it with the run. Use the REST API to manage checks and launches from scripts and CI.

# Back up at 03:00, then check in
0 3 * * *  /opt/backup.sh && curl -fsS useswitchyard.com/ping/k7r2x9

Pricing

Both plans include every feature on this page. They differ only in how many checks you can run and how many people you can add.

Free

$0

20 checks · 5 people

Create account

Pro

Coming soon

1,000 checks

Not on sale yet. Start on Free today; nothing you set up is lost when Pro arrives.

  • Deadlines, launch plans and what-if delays
  • Live board and launch calendar
  • Public status page with 90-day uptime
  • Slow-run detection
  • Email, Slack, Discord and signed webhook alerts
  • Website checks
  • Teams with roles and invite links
  • REST API