Architecture Guide

Security, Outbox & Blind Indexing Architecture

How CraftMyFunnel enforces multi-tenant data isolation, guarantees zero event drop with the Transactional Outbox pattern, and searches encrypted PII using deterministic HMAC-SHA256 blind indexing.

1. Multi-Tenant Data Isolation

Every database entity in CraftMyFunnel (Lead, Campaign, SequenceStep, ConnectedMailbox) is strictly scoped to a validated teamId.

Database queries enforce server-side tenant scoping derived exclusively from cryptographic Clerk / NextAuth JWT sessions. Client-provided workspace cookies are cross-checked against database membership records prior to executing any read, write, or delete operation.

2. Deterministic HMAC-SHA256 Blind Indexing

To protect sensitive prospect information at rest while retaining high-performance exact-match search capabilities, CraftMyFunnel implements the Blind Indexing Pattern (BlindIndexService):

// Deterministic Blind Hash Generation

1. PII field (e.g. email/phone) is normalized (lowercase, trimmed)

2. Computed hash: HMAC-SHA256(normalized_value, BLIND_INDEX_SALT + ":" + teamId)

3. Raw PII is stored encrypted with AES-256-GCM / Fernet

4. Exact lookups query the indexed blind hash column with zero plaintext exposure

3. Transactional Outbox Pattern

Direct background queue dispatching in distributed systems is prone to partial-failure anomalies (database write succeeds, but message broker crashes before job enqueue).

CraftMyFunnel utilizes an atomic Transactional Outbox (OutboxService):

Atomic Business Transaction

Domain changes and corresponding OutboxEvent records are committed inside a single ACID database transaction.

Optimistic Lock Worker Relay

Background relay workers poll pending outbox events using versioned lease-locks, publish events to workers, and mark status as PUBLISHED.

At-Least-Once Delivery & Idempotency

Consumer workers utilize idempotency keys to guarantee safe retry handling without duplicate sends.

Deliverability Guide REST API & Webhooks

Loading CraftMyFunnel...

1. Multi-Tenant Data Isolation

Every database entity in CraftMyFunnel (Lead, Campaign, SequenceStep, ConnectedMailbox) is strictly scoped to a validated teamId.

2. Deterministic HMAC-SHA256 Blind Indexing

To protect sensitive prospect information at rest while retaining high-performance exact-match search capabilities, CraftMyFunnel implements the Blind Indexing Pattern (BlindIndexService):

// Deterministic Blind Hash Generation

1. PII field (e.g. email/phone) is normalized (lowercase, trimmed)

2. Computed hash: HMAC-SHA256(normalized_value, BLIND_INDEX_SALT + ":" + teamId)

3. Raw PII is stored encrypted with AES-256-GCM / Fernet

4. Exact lookups query the indexed blind hash column with zero plaintext exposure

3. Transactional Outbox Pattern

Direct background queue dispatching in distributed systems is prone to partial-failure anomalies (database write succeeds, but message broker crashes before job enqueue).

CraftMyFunnel utilizes an atomic Transactional Outbox (OutboxService):

Atomic Business Transaction

Domain changes and corresponding OutboxEvent records are committed inside a single ACID database transaction.

Optimistic Lock Worker Relay

Background relay workers poll pending outbox events using versioned lease-locks, publish events to workers, and mark status as PUBLISHED.

At-Least-Once Delivery & Idempotency

Consumer workers utilize idempotency keys to guarantee safe retry handling without duplicate sends.

Security, Outbox & Blind Indexing Architecture

1. Multi-Tenant Data Isolation

2. Deterministic HMAC-SHA256 Blind Indexing

3. Transactional Outbox Pattern

Ready to govern your pipeline?

Security, Outbox & Blind Indexing Architecture

1. Multi-Tenant Data Isolation

2. Deterministic HMAC-SHA256 Blind Indexing

3. Transactional Outbox Pattern