The backend for the webhooks you receive

Catching the webhook is the easy part.

Verify it, keep it as a queryable record, run JavaScript when it lands, and replay it when something downstream breaks — from one SDK.

Start building freeSee how it works

Stripe, Shopify, Clerk, Resend, or any HMAC sender. Bring your own auth and frontend.

A Stripe charge.succeeded webhook is signature-verified and stored in a durable buffer that replay re-enters. A Centrali JavaScript function then calls an external fulfillment API and writes a row to the orders collection, with the arrival, the run, and the call tied together in one Event Log by correlation id.
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.

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 JavaScript.

Verify webhook senders with Clerk

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

Also sending webhooks?

The other direction is built too — signed HMAC delivery, configurable retries, a dead-letter queue, and per-delivery logs.

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.

View pricing
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.

Set up MCP

Start your backend in minutes

No credit card. Create an endpoint, paste the signing secret, and every handler runs only on verified events.

Start building freeSee how it works

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 the webhooks you receive. Configure an HTTP trigger with signature validation: verified arrivals are buffered before function dispatch. Opt into collection persistence for queries and search; replay retained buffer rows through the trigger's current configuration. Centrali also sends signed outbound webhooks to your own customers.

What can I receive webhooks from?

Configure common-provider signature presets or a compatible custom HMAC scheme. Verified HTTP-trigger arrivals are buffered; enable optional collection persistence or normalize records in your function for queries, search, and reactions.

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 JavaScript 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.