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

# Technical Overview

> Assess Reelevant integration complexity — architecture, data flow, SDK ecosystem, and implementation effort for the content-first personalisation engine.

## What Reelevant Is

Reelevant is a **content-first personalisation engine** that renders individualised Content at the moment of user interaction — not at send time. A single Content definition produces millions of unique variants based on real-time customer data, Workflow logic, and live Datasource state.

The platform handles the full pipeline: data ingestion, real-time decisioning, Content rendering, delivery, event capture, and incrementality measurement.

## Core Components

| Component      | Role                                                                                                      |
| -------------- | --------------------------------------------------------------------------------------------------------- |
| **Workflow**   | Directed acyclic graph (DAG) of Data Nodes, Logic Nodes, and Output Nodes — defines personalisation logic |
| **Datasource** | Typed data store (Product, CRM, Location, Analytics, Generic) fed via batch or streaming ingestion        |
| **Content**    | Visual template with data bindings — rendered at request time with individual data                        |
| **Runner**     | Execution engine at `reelevant.run` — resolves Workflows and returns personalised responses               |
| **DataHub**    | Ingestion layer supporting URL, S3, GCS, BigQuery, Snowflake, Kafka, FTP/SFTP sources                     |

## Section Contents

<CardGroup cols={2}>
  <Card title="Architecture & Lifecycle" icon="diagram-project" href="/why-reelevant/technical-evaluators/architecture">
    System architecture, data flow, and request lifecycle with sequence diagram.
  </Card>

  <Card title="Data Ingestion" icon="database" href="/why-reelevant/technical-evaluators/data-ingestion">
    DataHub source types, ingestion modes, and Datasource categories.
  </Card>

  <Card title="Integration Channels" icon="plug" href="/why-reelevant/technical-evaluators/integrations">
    Email, web, mobile, and JSON API integration patterns.
  </Card>

  <Card title="Authentication & SSO" icon="lock" href="/why-reelevant/technical-evaluators/authentication">
    Platform access control, SSO configuration, and API authentication.
  </Card>

  <Card title="Security & Compliance" icon="shield-check" href="/why-reelevant/technical-evaluators/security">
    SOC 2, GDPR, encryption, vendors, audit logging, and security contact.
  </Card>

  <Card title="Releases & Backward Compatibility" icon="rocket" href="/why-reelevant/technical-evaluators/releases">
    Release policy, 30-day notice for major releases, and compatibility guarantees.
  </Card>

  <Card title="Status & Monitoring" icon="signal" href="/why-reelevant/technical-evaluators/status-page">
    Real-time platform status, SLA monitoring, and incident communication.
  </Card>
</CardGroup>