Kite meters per event, not per seat. Every plan includes signature verification, CloudEvents normalization, replay, and a dead-letter queue — the paid tiers raise your monthly event allowance and how long events are retained.
High volume, on-prem, or compliance? Talk to us about Enterprise →
Autonomous agents can bill themselves over HTTP with x402 wallet billing — bootstrap an ephemeral team, settle the 402 Payment Required invoice, and start receiving events without a human opening the dashboard.
Yes. The free tier covers a fixed allowance of events with no credit card and no time limit, which is enough to build and test a full integration. Paid plans raise the monthly event allowance and retention window. The CLI and the wire protocol are MIT licensed, so the client side is free forever regardless of plan.
ngrok exposes a port on your machine to the public internet; every request that reaches your tunnel reaches your process. Kite terminates webhooks at a managed endpoint first, verifies the sender's signature, normalizes the payload into a CloudEvents envelope, and persists it to a durable queue before streaming it to you. That means events survive your laptop being closed, can be replayed later, and never require an inbound public URL pointing at your machine.
No. The Kite CLI opens an outbound connection to the relay and events stream down it, so the machine receiving events can sit behind NAT, in a container, or on a laptop. You register the Kite endpoint URL with your provider once and it never changes.
Kite validates each provider's signature scheme at the edge before an event is accepted — HMAC-SHA256 for Stripe, GitHub, Slack, Linear, Shopify, and PagerDuty, and HMAC-SHA1 for Twilio — and rejects timestamps outside the provider's replay window where one is defined. Anything that fails verification never enters your queue.
They are retained in your durable queue rather than dropped. Delivery is retried, and events that exhaust their retries land in a dead-letter queue you can inspect and replay from the CLI. Nothing is lost because a consumer was offline.
Yes. Every event carries a sequence number and an idempotency key, and `kite queue replay` re-delivers by sequence, time range, source, or predicate — against your local machine or a staging environment. Replay is how most people debug a handler without waiting for the provider to fire again.
CloudEvents is a CNCF specification for describing event data in a common envelope. Kite wraps every incoming webhook — whatever the provider's original shape — in a CloudEvents 1.0 envelope, so a single handler, filter expression, or agent prompt works across every source instead of being rewritten per provider.
Yes. Alongside normal subscription billing, Kite supports x402 wallet billing: an agent can bootstrap an ephemeral team over HTTP, receive a 402 Payment Required invoice, pay it, and start receiving events without a human ever opening the dashboard.
No credit card. Install the CLI and stream your first webhook in about two minutes.