Deployment alerts for small engineering teams.
Starro watches your deploys and tells the people who need to know. Connect a pipeline, choose who hears about what, and stop refreshing dashboards during a release.
Most teams start with deploy failures and rollback confirmations, then add the on-call handover once they trust it. Every alert links back to the run that produced it, so the first question anyone asks — which deploy was this? — is already answered.
Starro reads from GitHub Actions, GitLab CI, and CircleCI. Setup is a webhook and a list of who to tell. There is no agent to install and nothing to run on your own machines.
Alerts go to Slack, email, or text. Teams on call tend to pick text for failures and Slack for everything else, which is why routing is set per event rather than per team.
Pricing is per project rather than per seat. The number of people who want to hear about a failed deploy is not something you should have to budget for.
Starro Labs LLC is a small team in Charleston, South Carolina, building tools for people who ship on Fridays anyway.