knocker.dev

What it is

Knocker is a loadable SQLite extension with thin language bindings for Bun, Elixir, Go, Node, Python, and Ruby. It is designed for applications that already have an HTTP service, a SQLite database, and existing business logic, with the goal of reliably receiving and processing inbound webhooks without adding a hosted control plane. Its core flow is: persist every HTTP receipt as a Delivery first; for valid requests, create or associate an Event; then let a worker in the same process or another process handle the records that have already been committed to SQLite.

Core capabilities

Knocker focuses on common production webhook problems: whether the request has been written to the database before returning 2xx, whether provider retries cause duplicate processing, why an event did not run, and whether events can be replayed manually. It supports event-level deduplication, auditing of valid/invalid/duplicate/orphan deliveries, async workers, retries, dead letters, replay, requeue, and retention plus pruning for records such as handled, ignored, and orphan-delivery. Signature verification integrations cover Stripe, GitHub, Shopify, Slack, Postmark, Resend, Paddle, Lemon Squeezy, Standard Webhooks/Svix, Clerk, Twilio, SendGrid, Linear, Meta, Discord, Zendesk, Intercom, HubSpot, and others. It also supports token/basic/bearer auth patterns.

Pricing and openness

The captured text does not disclose the license, whether it is open source, any commercial edition, or pricing information, so its cost model cannot be determined. In terms of product form, it is not a SaaS product, but a local SQLite extension with language bindings. The documentation explicitly states that it does not provide hosted relays, an operator API server, an HTML console, a general-purpose queue API, or exactly-once side effects.

Ease of use and documentation

The documentation is well structured, covering Quick start, Concepts, SQLite contract, language bindings, Frameworks and ORMs, Verified ingress, Operator surface, Operator runbook, Retention and pruning, and Roadmap. Its strengths are a clear mental model and visibility into the underlying SQL extension calls. The downside is that it does not include built-in adapters for frameworks such as FastAPI, Express, Rails, Phoenix, Gin, Django, or Flask, so developers need to read the raw body themselves, pass headers/query parameters, and return the appropriate status code during integration.

Who it is for and access from China

Knocker is suitable for SQLite-first teams, monoliths, or lightweight services that want to minimize external dependencies. It is especially well suited to reliably persisting and processing webhooks from payment, email, CRM, and code hosting systems. It is not a good fit for scenarios that require a hosted console, a cross-team webhook platform, or a general-purpose distributed queue. The captured text does not provide information about access from China; domain reachability, package downloads, and payments all need to be tested in practice. Comparable options include Svix, Hookdeck, and Convoy, while task-queue-oriented needs may point to Sidekiq, Oban, or Celery.