Live status
Check whether the Access-protected Hooklane origin is ready. The facade returns only a small public status.
Hooklane is a small webhook delivery system that separates accepting an event from delivering it downstream. This page is a safe, fixed-input demonstration of that reliability boundary.
Check whether the Access-protected Hooklane origin is ready. The facade returns only a small public status.
Send one fixed portfolio event, then perform a small number of status checks. There is no public payload or destination input.
What the demo makes visible
Hooklane commits the event before acknowledging it, so an accepted request has a durable starting point.
Delivery can be repeated around failure windows. Downstream consumers use an event identity to deduplicate side effects.
Repeated requests with the same key and content converge on one logical event; conflicting content is rejected.
Retryable failures use bounded backoff. Exhausted or non-retryable work moves to a dead-letter path.
Work left pending by a stopped worker can be claimed and attempted again without pretending delivery is exactly once.
The facade has three documented routes, a fixed origin, a fixed event, bounded upstream work, and a native rate limit.
Architecture
The Service Token belongs to the Worker and is never handed to public users. Cloudflare Access protects the origin; the Named Tunnel connects it to the Debian edge. The demo Worker uses Service Auth only for its two fixed upstream calls.
Scope, stated plainly
This is a single-node, non-production portfolio/demo surface. It does not claim production traffic, high availability, long-running stability, production readiness, or abuse-proof operation. The public Worker is a facade; the existing D1/Queues backend and the Redis backend remain separate.