hook-serve

What problem does it solve?

Operators and engineers need a reliable, auditable, and configurable pipeline to receive, validate, normalize, and deliver webhook events without writing custom glue code or risking event loss during downstream outages.

Core Features & Use Cases

• Contract-driven configuration: Define ingress, routes, and egress adapters in a single contract.toml and switch behavior by profile.
• Durable Kafka backbone: Ingest events into per-source topics, fan-in via relay, and consume from a core topic with replay and DLQ support.
• Security and validation: Per-source HMAC validation, strict fail-closed contract validation, payload sanitization, and timestamp/replay protections.
• Pluggable adapters and plugins: HTTP/WebSocket/MCP/Kafka adapters with ordered plugins (event_type_alias, require_payload_field, add_meta_flag) for flexible routing and enforcement.
• Use case: Run self-hosted webhook ingestion for GitHub and Linear, fan events into Kafka for downstream AI agents, and ensure required deliveries to egress systems with retry and DLQ semantics.

Quick Start

Start the serve runtime with the default-openclaw profile to validate contracts and begin publishing sanitized EventEnvelopes into the Kafka core for downstream relay and smash processing.