Composable backend for developers and AI-assisted builders

Build what you imagine. Centrali powers what makes it work.

A composable backend for applications built with code, AI agents, or both. Bring data, functions, queries, workflows, and event delivery together in one platform.

Start with event-driven workflows. 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.

Need a webhook destination for a quick test?

Centrali Play gives you a temporary capture URL and JSON event reads, without an account.

Explore Centrali Play →
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.

Connect a compatible MCP client to query workspace data and work with backend tools. Setup requires authentication and workspace permissions; review proposed writes before authorizing changes.

Start your backend in minutes

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

Takes less than 5 minutes to get started.

FAQ

Common questions

Questions developers ask while evaluating Centrali.

What is Centrali?

Centrali is a composable backend for applications built with code, AI agents, or both. It brings together data, event ingestion and delivery, functions, queries, workflows, and operational visibility. For example, verify an incoming webhook, keep it as a queryable record, run logic, and replay it if downstream processing fails.

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. Centrali Pages is retired; build application frontends outside Centrali using the SDK or REST API. Database: no, Centrali stores your data in its own collections so the SDK, search, and webhook records all live in one place.