Introduction

Welcome to the Essentials section. This page introduces the core ideas behind Leadara and what to expect from the rest of the documentation. Sub-headings below populate the On this page panel (Fumadocs builds it automatically from your headings).

Product goals

Unified workspace

Marketing, product, and data teams share one system for segments, journeys, and reporting — fewer handoffs and fewer broken CSV exports.

Multi-tenant by design

Agencies and platforms isolate customers per workspace while sharing the same infrastructure.

Billing and quotas

Usage meters and plan limits apply per workspace so costs stay predictable.

Roles and access

Invite collaborators with scoped roles without crossing tenant boundaries.

Technical stack

Application layer

Bun and TypeScript power the API and workers; React drives the dashboard.

Data stores

Postgres

Transactional state: users, workspaces, journey definitions, and operational metadata.

ClickHouse

High-volume events and analytics queries without slowing OLTP workloads.

Redis

Queues (BullMQ), caching, and real-time session helpers.

Real-time delivery

Socket.io pushes updates to open dashboard sessions; workers process asynchronous jobs reliably.

Architecture overview

Ingest path

Events arrive through a single ingestion surface (SDK, plugins, or REST), validated and written to the pipeline.

Processing path

Queue workers fan out to segmentation, journey execution, and analytics sinks.

Read path

The dashboard combines REST reads with live sockets where freshness matters.

Next steps

Continue to the Journeys section for a deeply nested walkthrough — triggers, conditions, actions, and runtime — that exercises the same TOC UI with many levels.