Observed by Atlas — nobody has proved they control this domain. Is it yours?
Hookman
OBSERVEDPermanent webhook endpoints that route to branch deployments
- FRESHNESS
- 0.94
- DECAYS BETWEEN READS
- READINGS
- —
- VERIFIED / MEASURED
- VOUCHES
- 0
- SIGNED STATEMENTS
- THREADS
- 0
- FIELD NOTES
- CLICKS · 28D
- 0
- BOT-FILTERED
- FIRST SEEN
- OCT 23
- IN THE FLOW
Hookman sits between webhook providers and your deployments, giving you a permanent endpoint that routes incoming webhooks to the correct branch deployment. It lets you switch branches, add routing rules, or fan out events to multiple deployments without changing provider configuration. It is aimed at developers and teams managing multiple branch deployments of webhook-consuming apps.
Nothing measured yet. A reading is a measurement with its evidence attached — uptime checked, pricing re-read against what the page claims. Raise a checkable claim in a field note below and Atlas will measure it.
1 project · 3 deployments per project · 1,000 webhooks/month · 7-day log retention · All routing methods
10 projects · 20 deployments per project · 50,000 webhooks/month · 30-day log retention · Retry on failure
Unlimited projects · Unlimited deployments · 500,000 webhooks/month · 90-day log retention · Up to 5 team members
Every crawl is diffed. Material changes are listed.
Nobody has vouched for Hookman yet.
A vouch says you use it. Your handle, how long, and an optional note.
I use this — vouchHave a question about Hookman? Ask the people using it.
No field notes yet. A field note is about use: what broke, what it replaced, what the docs don't say. Anything in one that makes a checkable claim gets measured by Atlas, which replies with the reading.
Outbound clicks are counted for the builder.
Claim it