Overview

Shipyrd is a deployment dashboard for development teams. It answers the question "what's deployed where, and when?" without anyone having to ask in Slack or other channels.

When you’d use this

Most teams don’t have a single place that shows every deploy across every app and environment. Deploy notifications live in Slack history, CI logs, Honeybadger, AppSignal, and the heads of whoever happened to be on call. So when someone asks “did the migration go out yet?” or “who deployed staging at 3am?”, the answer takes a few minutes of digging — or never quite arrives.

Shipyrd is for teams that want one timeline of deploys, accurate attribution for every one of them, and lightweight controls (locks, office hours, Slack alerts) so people stop stepping on each other’s toes.

How it fits together

Shipyrd has three concepts you’ll see throughout these docs:

• Apps — each codebase you deploy is one app in Shipyrd. Most teams have a few.
• Destinations — the environments an app deploys to. production, staging, eu-west, anything you want.
• Deploys — events recorded against an app + destination. Each one captures who deployed, what version, when, how long it took, and (when available) the commits included.

Deploys reach Shipyrd through one of the send-deploy paths: your CI, your Kamal hooks, an error monitor like Honeybadger/AppSignal/Rollbar, or a plain curl call. Once they’re in the dashboard, notifications push events back out — most commonly to Slack.

Around that core, Shipyrd has a few features that make day-to-day deploys safer and quieter:

• Deploy locks prevent two people from deploying the same destination at the same time.
• Office hours auto-lock destinations outside the hours your team is online.
• Deploy badges are shields you can drop into a README or status page to show when the last deploy went out and whether a destination is locked.
• Slack bot posts notifications and lets people see lock state without leaving Slack.

Pick where to go next

• If you’re setting up Shipyrd for the first time, pick how you want to send deploys: Ruby gem (Kamal), plain HTTP (any language/CI), or Honeybadger / AppSignal / Rollbar if you already have those.
• If you’ve got deploys flowing in and want to wire up Slack, see Notifications and the Slack bot.
• If your team has had a deploy collide once already, jump to Deploy locks or Office hours.