The problems Shipyard solves
One person can write software for fifty repositories. Keeping fifty repositories maintained, released and explained is a different job. These are the problems Shipyard takes over.
1. Nobody watches everything
Issues, failing CI, security alerts and stale pull requests arrive in fifty places. Shipyard collects them into one queue for the repositories you opt in. One screen, one list, sorted by project.
2. Small fixes never get done
A dependency bump or a two-line bug fix costs more in context switching than in typing. Label an issue agent-ready and Shipyard turns it into a tested pull request. You review; nothing merges on its own.
3. Releases depend on memory
Merged changes sit unreleased because nobody remembers to tag. Shipyard batches approved changes into a release every 48 hours per project. No changes, no release.
4. Alerts wake you up without context
An Alertmanager webhook lands in Shipyard, is matched to its project and starts a diagnostic run. By the time you look, the run log already holds the metrics and the first findings.
5. Work disappears on restart
Runs live in a durable SQLite queue with leases and heartbeats. A crashed worker loses nothing: the lease expires and the run is picked up again. Idempotency keys stop the same job from running twice.
6. Projects go quiet
Software that ships but never explains itself looks abandoned. Once a week Shipyard scores topics for each project and drafts an article when one clears the threshold of 70. Below the threshold it skips the week.
What it costs to run
One static binary, one SQLite file, one log directory. It runs on a Raspberry Pi.