Dispatchlane is an integration reliability platform for webhook ingestion, outbound event delivery, retries, dead-letter handling, replay, and operational visibility.
Dispatchlane is being built in public. The repository is intentionally developed with small commits, reviewable pull requests, ADRs, and CI discipline from day one.
Integration systems usually become brittle first at the reliability boundary, not at the CRUD boundary.
Dispatchlane exists to handle the hard operational parts of integration traffic:
- inbound webhook ingestion
- signature verification
- canonical event persistence
- deduplication and fingerprinting
- outbound delivery attempts
- retry scheduling
- dead-letter handling
- replay
- delivery inspection and auditability
- health, readiness, metrics, and operator visibility
The current repository scaffold intentionally includes only:
- Node.js and TypeScript project setup
- Fastify runtime baseline
- environment loading
- minimal API entrypoint
GET /healthz- CI checks for install, typecheck, and build
The first scaffold does not yet include database, workers, replay, ingestion, or delivery logic.
- HTTP ingestion endpoint for generic webhook sources
- HMAC-SHA256 verification with timestamp tolerance
- immutable ingress receipts
- immutable canonical events
- subscription-based HTTP delivery
- retry policy enforcement
- dead-letter state
- replay by event and bounded range
- inspection APIs for events, deliveries, and attempts
- health, readiness, metrics, and structured logs
- exactly-once delivery claims
- Kafka or RabbitMQ integration
- arbitrary transformation scripting
- no-code workflow builder
- multi-region active-active deployment
- frontend-heavy operator console
- Node.js 20+
npm installnpm run devnpm run typecheck
npm run buildcurl http://localhost:3000/healthz- explicit contracts over hidden behaviour
- durable state before acknowledgement
- immutable history where auditability matters
- operational clarity over architecture theatre
- small, reviewable changes
- documentation that matches real behaviour
mainstays stable and reviewable- work lands through short-lived branches and pull requests
- important design decisions are captured as ADRs
- CI expands with the codebase instead of being added late
- documentation is maintained alongside implementation
Apache-2.0