Architecture & Lifecycle

Request Lifecycle

Reelevant is the only content-first personalisation engine. Build Content once — the platform creates millions of individualised versions at the moment of interaction, not at send time. The following sequence diagram shows the end-to-end flow from a user opening an email (or visiting a page) to receiving personalised Content.

Lifecycle Steps in Detail

Request: Your ESP/website/app includes a Reelevant URL (https://reelevant.run/{workflowId}?uid={customerId}). The user’s client requests it.
Edge routing: The CDN terminates TLS and routes to the nearest execution region.
Customer identification: The URL contains a customer identifier (query parameter) mapped to Datasource records. This identifier is public by design — use opaque IDs.
Data retrieval: The Runner fetches the customer’s current data from connected Datasources (from in-memory cache with live fallback).
Workflow execution: The DAG evaluates Conditions, retrieves additional data via Data Nodes, and traverses Branches to select the appropriate Output Node.
Content rendering: The selected Content is rendered with individual data (product images, prices, offers, text) and returned as image, HTML, or JSON.
Event capture: An impression event is recorded. Click interactions are captured via redirect URLs for future Workflow logic and analytics.

Infrastructure Guarantees

Metric	Guarantee
Availability	99.9% SLA (measured monthly)
Data encryption at rest	AES-256
Data encryption in transit	TLS 1.3
Data residency	EU (additional regions planned)
Throughput	100M+ personalised Content renders/month per client
Failover	Multi-region active-active

Environments

Reelevant operates a single production platform. There is no separate sandbox, development, or test environment for customers. Your organisation gets one tenant, and separation between environments happens inside it: you create dedicated Teams — QA, pre-production, or per-market — and the RBAC/ABAC model scopes every Workflow, Content, Datasource, user, and API token to the Team that owns it. See Authentication & SSO for the model and Teams for the configuration.

Property	Behaviour
QA / pre-production	Dedicated Teams within your tenant, each with its own Workflows, Contents, Datasources, users, and API tokens
Representativeness	The same platform version, infrastructure, performance, and APIs as your live Workflows — nothing is stubbed
Isolation	Enforced by the RBAC/ABAC scoping: a token or user granted the QA Team cannot read or write resources of another Team
Pre-release validation inside a Team	Workflow states (Draft / Live / Inactive), Real-Time Testing, and debug mode with a short-lived token
Reelevant internal environments	Private, never exposed to customers, and fully disconnected from each other — separate physical servers, no shared data path

Because QA runs on the production platform, what you validate is exactly what your recipients get.

Next Steps

Data Ingestion

DataHub source types and ingestion modes.

Data Access & Export

BigQuery views, analytics API, and feeding your own data platform.

Integration Channels

Email, web, mobile, and JSON API patterns.

Overview

For Technical Evaluators

Request Lifecycle

Lifecycle Steps in Detail

Infrastructure Guarantees

Environments

Next Steps

Data Ingestion

Data Access & Export

Integration Channels

​Request Lifecycle

​Lifecycle Steps in Detail

​Infrastructure Guarantees

​Environments

​Next Steps

Data Ingestion

Data Access & Export

Integration Channels

Request Lifecycle

Lifecycle Steps in Detail

Infrastructure Guarantees

Environments

Next Steps