For one
Gosling
One person, a couple of repos, the honks that matter.
[FREE]forever
- Up to [N] flows
- GitHub and Slack
- Every built-in condition
- Snooze from Slack
Pricing
Pay for the goose, not the noise.
Every plan gets the whole patch board. You pay by how many flows you keep plugged in, never by how many honks get sent.
For a teamMost flocks
Goose
A team that wants reviews moving without a standup about it.
[PRICE PER FLOW]per active flow / month
- Unlimited flows
- Shared flows and channels
- Quiet hours per person
- Run log, last [N] days
For an org
Gaggle
Lots of teams, lots of repos, one place to keep the noise down.
[CUSTOM]talk to us
- Everything in Goose
- SSO and audit log
- Custom webhooks in and out
- Priority support
Fair questions.
What counts as a flow?
One source, any conditions you chain onto it, and the outputs it honks at. Paused flows don’t count.
Do you charge per notification?
No. Charging per honk would reward us for being noisy. You pay for flows, and the honks are on the house.
What does honk read from GitHub?
The webhook events you choose: titles, labels, branches, who’s involved. It doesn’t need to read your code.
What if Slack is down?
honk keeps the honk and retries for [RETRY WINDOW]. If it still can’t get through, it tells you what it missed once Slack is back.