The backend for webhooks in and out

Webhooks in. Workflows out. One SDK.

Ingest third-party webhooks, store them as data, and send your own workflows and webhooks — from one TypeScript SDK.

Works with any auth. Bring your own frontend. Connect any service.

A Stripe charge.succeeded webhook hits a Centrali function, which writes a row to the orders collection; the subscription fires automatically and a signed order.paid webhook is delivered to acme.com/hooks.
What are you building?

Pick the closest fit

Each links to a deeper guide or landing page with code, examples, and a template you can ship.

Send customer webhooks

Let your customers subscribe to events from your app — with delivery logs, retries, and replay built in.

Ingest Stripe events

Land Stripe webhooks as queryable records and join them with your own data in a single query.

Ingest GitHub webhooks

Receive pushes, PRs, and issues as typed records. Search history, replay failures, react with TypeScript.

Verify webhook senders with Clerk

Authenticate webhook sources and route events with auth context — without bolting on a separate auth layer.

Pricing

Simple, transparent pricing

Start free with generous limits. Pay only as your usage grows. No hidden fees. No per-seat billing.

Pay only for what you exceed. No per-seat fees. No lock-in.

AI-ready

Run Centrali from your AI.

Point Claude, Cursor, or any MCP client at your workspace. Query your data, manage your flows, call your APIs, and build new features — all in plain English. No manual wiring.

Start your backend in minutes

No credit card. No setup. Just run the CLI and start building.

Takes less than 5 minutes to get started.

FAQ

Common questions

Questions developers ask while evaluating Centrali.

What is Centrali?

Centrali is the backend for webhooks in and out. Ingest events from Stripe, Shopify, GitHub, HubSpot, or any source, store them as queryable records, run workflows when they arrive, and send your own signed webhooks back out — all from one TypeScript SDK.

What can I receive webhooks from?

Anything that sends a webhook. Centrali validates signatures from common providers like Stripe, GitHub, Shopify, and Clerk out of the box, and lets you add custom verification for anything else. Events land as typed records you can query, search, and react to.

What do I get out of the box?

A signed inbound endpoint, a database, search, retries, delivery logs, replay, and a console UI to see all of it. You write TypeScript for the parts that need logic — everything else is already wired up.

Do I bring my own database, auth, or frontend?

Auth and customer-facing frontend, yes — Centrali works with any auth provider (Clerk, Auth0, custom) and any frontend stack for your app. For internal dashboards over your records and events, Pages (in beta) is built in, so you don't need a second frontend project just to see your data. Database: no, Centrali stores your data in its own collections so the SDK, search, and webhook records all live in one place.