Contract-first webhook infrastructure with portable delivery.
HookShip combines an open contract and developer-experience toolkit, a portable outbound delivery data plane, and a private hosted control plane. The open foundation covers contract validation and compatibility, fixtures and types, Standard Webhooks-compatible signing, adapter primitives, a CLI, and self-hosted delivery.
Important
HookShip is in pre-release development. No public packages, releases, hosted service, or support commitments are available yet.
Website: https://hookship.github.io/website/
| Repository | Purpose | Status |
|---|---|---|
.github |
Organization profile and shared community defaults | Public |
toolkit |
Public libraries, CLI, adapters, and contracts | Public, pre-release; no public release |
hook-service |
Portable outbound webhook delivery data plane and protocol | Public, pre-release; no public release |
platform |
Private managed control-plane and hosted-product engineering | Private; not an operated public service |
website |
Public web presentation, navigation, and status | Public; deployed with GitHub Pages |
HookShip separates concerns into three tiers so that public foundations stay reusable and private product engineering stays isolated:
toolkit— the open foundation. Public libraries, CLI, adapters, and webhook contracts with their validation, compatibility, and signing primitives. Everything else builds on it, and it is the source of truth for public package interfaces.hook-service— the portable data plane. A self-hostable outbound delivery service that consumestoolkitand owns the delivery protocol and its capability surface. It builds ontoolkitcontracts rather than restating them.platform— the private control plane. The managed, hosted-product engineering that consumes the public foundation. It is private, is not an operated public service, and never publishes public foundation changes that belong intoolkitorhook-service.
The .github repository holds only organization-wide profile and
community-health content; it ships no product code. The website repository
owns public web presentation and links back to repository-local sources of
truth.
- Repository placement is the authoritative policy for where issues, changes, and documentation belong.
- Source of truth defines which copy of a shared artifact is canonical.
- Release policy defines the branch-protection and release baseline for every repository.
Read the repository placement policy before opening an issue or proposing a change. Repository-specific documentation takes precedence over these shared defaults.
The early tester program provides two public, source-based evaluation tracks plus an invite-only managed design-partner path. It explains which repository to use, what is available today, how to submit safe public feedback, and what must never be posted.