Open contractsPortable deliveryManaged control

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.

Live route / syntheticready
01Contractorders.v1
02Routeprimary
03Deliversigned
04Observemetadata
202 acceptedsignature verifiedpayload-free status
Pre-release

Public source is available. No hosted account, package release, or service-level commitment exists yet.

14
public package candidates

Contracts, signing, adapters, CLI, and portal building blocks.

4
delivery runtime profiles

Ephemeral evaluation plus PostgreSQL, Redis, and Kafka modes.

0
hosted dependencies

The public source evaluation runs without a HookShip account.

01The system

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.

01
Describe

Toolkit

Import OpenAPI or AsyncAPI. Validate compatibility, generate fixtures and types, sign events, and build the portal experience.

Contract truth
02
Deliver

Hook service

Accept events durably, sign exact payload bytes, dispatch safely, retry with evidence, and operate the queue on your infrastructure.

Portable runtime
03
Operate

Platform

Coordinate contracts, endpoints, delegated portal access, delivery metadata, governance, and backend portability.

Managed control
02Repository map

Know 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.

03Operating principles

Portability is a product feature, not a migration project.

The architecture is designed to make boundaries visible before they become lock-in.

01

Contracts are portable

Keep schemas, compatibility decisions, fixtures, and signing behavior independent of the delivery vendor.

02

Delivery stays replaceable

Run the data plane yourself, preserve stable identities, and avoid making the control plane part of every delivery request.

03

Metadata before payloads

Operate from bounded delivery evidence. Payload retention is explicit, scoped, encrypted, and time-limited.

04

Unsupported means visible

Capability differences are shown before action. The product does not simulate parity that a backend cannot provide.

Current signal

Built enough to evaluate. Early enough to influence.

Public sourceAvailable
Public releasesNot yet
Hosted serviceNot operated
Tester intakeOpen
Read the honest status

Have 30 minutes and a webhook problem?

Take the source for a spin.
Tell us where the map breaks.

Choose an evaluation trackOpen tester intake