codehooks.io

Developers who receive webhooks from services like Stripe, Shopify, GitHub or Twilio typically need more than a delivery gateway: they need to verify signatures, transform payloads, store events, query them over time, retry failed processing, and often deliver webhooks onward to their own users. Webhook gateways such as Svix or Hookdeck handle ingestion, retries and delivery logs, but then hand the event off to a separate backend that the developer still has to build and wire up: a database, queues, workers, and cron. That means setting up infrastructure, provisioning services, and maintaining a second system just to actually act on the data, which slows down building and iterating on webhook logic.

Codehooks provides a complete backend behind every webhook endpoint instead of just a gateway. It covers inbound ingestion (signature verification, queuing, retries, transform, storage) and outbound delivery (fan-out, signing, retries, delivery logs), with per-provider guides and templates for common providers already built. Behind each endpoint sits a queryable NoSQL database with MongoDB-like queries, a key-value store, queues with workers, CRON jobs, JWT/JWKS authentication, and REST API and static hosting. Everything is defined as code and deployed via a CLI (coho deploy) in under 5 seconds, with no build steps, containers, or CI pipelines, and the platform is designed to be operated by coding agents (Claude Code, Cursor, Codex) as well as humans. Templates like a webhook inspector or a delivery system let developers deploy a working, complete backend in minutes.

The page emphasizes that AI coding agents can now build and deploy webhook backends directly via CLI, and that flat-rate pricing lets an agent iterate many times without cost concerns, positioning the product for an agent-driven development workflow.