Skip to content

Centrali

Build webhook-backed applications with Centrali. Receive third-party webhooks, store them as records, react with functions and triggers, and send outbound webhooks from one backend.

Receive a Webhook create-centrali-app API Overview

Follow the Core Path

  • Receive a webhook

    Accept third-party events through HTTP triggers, verify signatures, and queue work without blocking the sender.

    Webhook Ingestion

  • Store as records

    Persist accepted payloads as durable records so you can inspect them later, trigger follow-up work, and keep a long-lived event history.

    Collections & Records

  • React with functions and triggers

    Run code when records change, on a schedule, on demand, or through synchronous endpoints. Add automations when one function is not enough.

    Triggers

  • Send outbound webhooks

    Fan record changes out to customer systems, partner integrations, or internal services with signed outbound deliveries.

    Outbound Webhooks

Build with Your Framework

Centrali is the backend layer. Pair it with Next.js, React, Vue, or your existing auth stack.

  • create-centrali-app

    Scaffold a configured app with the SDK and start from a supported React + Vite or Next.js template.

    Scaffold an App

  • Next.js Quick Start

    Use Centrali from server components or API routes when you want the most direct framework-specific path.

    Next.js Guide

  • SDK for React, Vue, or Custom Apps

    Use the JavaScript/TypeScript SDK directly when you want to bring your own UI stack and keep Centrali behind it.

    SDK Reference

  • Bring Your Own Auth

    Keep Clerk, Auth0, Okta, or another OIDC provider in front of Centrali and pass user tokens through BYOT.

    External Auth (BYOT)

Need a Different Starting Point?

  1. New here? Start with Getting Started for setup, first app paths, and workspace basics.
  2. Need the product map? Start with Build Overview for the core backend workflow and supporting capabilities.
  3. Need auth first? Start with Authentication for service accounts, BYOT, and authorization flow.
  4. Need exact routes? Start with API Overview for current service prefixes and endpoint families.
  5. Prefer code examples? Start with Examples for end-to-end build guides.
  6. Integrating AI clients? Start with AI Agents for MCP, hosted agents, and troubleshooting.

Why Centrali?

  • One backend for webhook-backed apps — Ingest events, persist records, run code, and fan changes back out without stitching together separate services.
  • Durable event history — Keep accepted payloads as records you can inspect, reconcile, and react to long after the sender stops retaining them.
  • SDK-first application architecture — Pair Centrali with Next.js, React, Vue, or a custom frontend instead of locking yourself into a hosted UI surface.
  • Flexible auth and execution — Use service accounts, BYOT, synchronous endpoints, async webhooks, event-driven triggers, and automations from the same platform.

See how Centrali compares