> ## Documentation Index
> Fetch the complete documentation index at: https://notifizz.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What is Notifizz?

> Notifizz is the event-driven notification platform with an AI orchestrator. Plug any event, even incomplete — the orchestrator enriches it automatically and ships the notification across every channel, with no redeploy when Marketing creates a new campaign.

# What is Notifizz?

Notifizz is the **event-driven notification platform for your whole team**. Your backend emits one event — even an incomplete one. The **AI orchestrator** enriches it with your live business data, picks the channels, builds the recipients, and dispatches the notification. Marketing edits campaigns from the dashboard; developers ship events from code; the same primitive powers transactional and lifecycle notifications.

Instead of building notification infrastructure from scratch — queues, storage, real-time delivery, widget UI — you integrate two SDKs and let Notifizz handle the rest.

## How it fits together

Two SDK families work in tandem:

<CardGroup cols={2}>
  <Card title="Event Tracking" icon="satellite-dish" href="/docs/sdks/event-tracking/overview">
    Track events from your backend (Node.js, Java/Kotlin, PHP). Generate widget auth tokens. Expose enrichers (Node-only today).
  </Card>

  <Card title="Notification Center" icon="bell" href="/docs/sdks/notification-center/overview">
    Drop a real-time notification widget into your app (React, Angular, Vanilla JS).
  </Card>
</CardGroup>

**The flow, in three steps:**

1. **Plug any event** — even incomplete — from your backend with `await client.track(eventName, properties)`.
2. **The AI orchestrator enriches it automatically** with your live business data via [enrichers](/docs/why/enrichers). The AI detects what's missing and produces actionable dev tasks (one-click executable from your IDE via MCP).
3. **The notification ships** — across every channel the campaign configures. New campaign? Config in the dashboard, **no code redeploy**.

The Notification Center widget receives new messages in real time — no polling, no refresh.

## Available SDKs

| SDK               | Package                      | Purpose                                                              |
| ----------------- | ---------------------------- | -------------------------------------------------------------------- |
| **Node.js**       | `@notifizz/nodejs`           | Track events, generate widget auth tokens, expose enrichers          |
| **Java / Kotlin** | `com.notifizz:notifizz-java` | Track events, generate widget auth tokens                            |
| **PHP**           | `notifizz/php`               | Track events, generate widget auth tokens                            |
| **React**         | `@notifizz/react`            | `NotifizzInbox` component, `NotifizzProvider` + `useNotifizz` hook   |
| **Angular**       | `@notifizz/angular`          | `<notifizz-bell>` standalone component, `NotifizzService` injectable |
| **Vanilla JS**    | `@notifizz/vanilla`          | Framework-agnostic `createNotifizz()` API                            |

## Key capabilities

* **Event-driven by design** — your call site never picks a campaign, channel, or recipient list. Server-side routing keeps Marketing autonomous and the SDK minimal.
* **AI orchestrator** — Marketing describes a campaign in plain language; the AI generates the orchestrator (recipients, enrichments, branching) and proposes dev tasks for any gap.
* **Live data via enrichers** — no warehouse sync. The orchestrator fetches live business data from your systems at notification time.
* **Real-time widget delivery** — new messages stream straight to the bell.
* **Idempotent emits** — every `track()` carries an idempotency key; duplicate emits short-circuit with `{ duplicate: true }`.
* **Flexible widget auth** — Firebase, backend token, publicly-signed JWT (Auth0 / Clerk / Cognito / Supabase), or none for dev.
* **Customisable UI** — default bell + dropdown out of the box, or replace with your own component while Notifizz manages data and state.

## Next steps

<CardGroup cols={2}>
  <Card title="How Notifizz works" icon="diagram-project" href="/docs/concepts/how-it-works">
    The pipeline end to end — event in, notification out.
  </Card>

  <Card title="Work with a Certified Partner" icon="handshake" href="/docs/partners/certified-partners">
    Vetted experts ship a measurable programme in weeks, not quarters. The fastest path to value.
  </Card>

  <Card title="Backend quickstart" icon="rocket" href="/docs/quickstart/backend">
    Send your first event in under five minutes.
  </Card>

  <Card title="Events and workflows" icon="diagram-project" href="/docs/concepts/events-and-workflows">
    The four building blocks: events, properties, campaigns, recipients.
  </Card>
</CardGroup>