Contracts, signing, adapters, CLI, and portal building blocks.
Webhook infrastructure / rearranged
Ship the experience.
Keep the exit.
Build a polished webhook product without welding contracts, delivery, and customer experience to one vendor or one runtime.
Public source is available. No hosted account, package release, or service-level commitment exists yet.
Ephemeral evaluation plus PostgreSQL, Redis, and Kafka modes.
The public source evaluation runs without a HookShip account.
One webhook product. Three replaceable layers.
Each layer has one job and one source of truth. Adopt the open pieces independently, or connect them into a complete product surface.
Toolkit
Import OpenAPI or AsyncAPI. Validate compatibility, generate fixtures and types, sign events, and build the portal experience.
Contract truthHook service
Accept events durably, sign exact payload bytes, dispatch safely, retry with evidence, and operate the queue on your infrastructure.
Portable runtimePlatform
Coordinate contracts, endpoints, delegated portal access, delivery metadata, governance, and backend portability.
Managed controlKnow exactly where the work belongs.
HookShip is intentionally split by ownership. Product behavior stays with its code; the website summarizes and routes rather than duplicating specifications.
toolkit
Public libraries, CLI, adapters, contract tooling, signing, and portal components.
- Apache-2.0
- 14 package candidates
- No hosted dependency
hook-service
Self-hostable outbound webhook delivery with durable acceptance, retries, DLQ, and payload-free status.
- Apache-2.0
- Single-VM ready
- At-least-once delivery
platform
Private multi-tenant product engineering for contracts, portals, metadata, governance, and operations.
- Private source
- Not an operated service
- Invite-only pilot
.github
Repository placement, release controls, community defaults, security, support, and tester intake.
- Shared policy
- Tester program
- Reusable CI
website
The source for this site, its public narrative, status summaries, and evaluation navigation.
- Next.js
- Static export
- GitHub Pages
Portability is a product feature, not a migration project.
The architecture is designed to make boundaries visible before they become lock-in.
Contracts are portable
Keep schemas, compatibility decisions, fixtures, and signing behavior independent of the delivery vendor.
Delivery stays replaceable
Run the data plane yourself, preserve stable identities, and avoid making the control plane part of every delivery request.
Metadata before payloads
Operate from bounded delivery evidence. Payload retention is explicit, scoped, encrypted, and time-limited.
Unsupported means visible
Capability differences are shown before action. The product does not simulate parity that a backend cannot provide.
Have 30 minutes and a webhook problem?