How rahmon-tech/emailsystem works
EmailBlast is a self-hosted campaign platform. Teams compose standard or image-first messages, import recipients, configure senders and providers, then schedule or launch campaigns. The worker prepares campaigns and processes durable deliveries through provider-aware routing, safety limits, and pacing; provider events reconcile outcomes for Activity and tracking. The graph preserves documented experiment and operational capabilities. Source excerpts and the README support the shown relationships; unsampled subsystems are included where the tree and README establish them, with uncertain links omitted.
Main entry points: engine.ts Delivery engine · campaigns.ts Campaign lifecycle · index.ts PostgreSQL · route.ts HTTP API
Components 23
Web experience
- Campaign composer
apps/web/components/blast.tsx - Image campaign
apps/web/components/image-blast.tsx - Activity console
apps/web/components/activity.tsx - HTTP API
apps/web/app/api/[...path]/route.ts
Campaign management
- Campaign lifecycle
packages/core/src/campaigns.ts - Recipient imports
packages/core/src/imports.ts - Email rendering
packages/email-renderer/src/index.ts
Delivery runtime
- Queue worker
apps/worker/main.ts - Delivery engine
packages/core/src/engine.ts - Pacing dispatcher
packages/core/src/dispatcher.ts - Event reconciliation
packages/core/src/events.ts - Click tracking
packages/core/src/tracking.ts
Safety and experiments
- Safety governor
packages/core/src/safety.ts - Delivery experiments
packages/core/src/experiments.ts - Experiment evidence
packages/core/src/experiment-evidence.ts
Providers and state
- Provider management
packages/core/src/providers.ts - Provider adapters
packages/providers/src/index.ts - Provider webhooks
packages/providers/src/webhooks.ts - PostgreSQL
packages/db/src/index.ts - Redis coordination
packages/core/src/redis.ts
Other components
- Campaign team
- Email providers
- Email recipient
Connections 29
- Campaign team → Campaign composer: composes
- Campaign team → Image campaign: composes
- Campaign composer → HTTP API: submits
- Image campaign → HTTP API: submits
- HTTP API → Campaign lifecycle: routes campaign requests
apps/web/app/api/[...path]/route.ts - Campaign lifecycle → Recipient imports: uses recipient lists
packages/core/src/campaigns.ts - Campaign lifecycle → Email rendering: renders message
packages/core/src/campaigns.ts - Campaign lifecycle → PostgreSQL: persists campaign state
packages/core/src/campaigns.ts - Queue worker → Campaign lifecycle: prepares campaign
apps/worker/main.ts - Queue worker → Delivery engine: processes deliveries
apps/worker/main.ts - Queue worker → Event reconciliation: reconciles events
apps/worker/main.ts - Delivery engine → PostgreSQL: records attempts
packages/core/src/engine.ts - Delivery engine → Pacing dispatcher: acquires pacing
packages/core/src/engine.ts - Delivery engine → Safety governor: checks safety
packages/core/src/engine.ts - Delivery engine → Delivery experiments: applies experiment pacing
packages/core/src/engine.ts - Delivery engine → Experiment evidence: appends outcome evidence
packages/core/src/engine.ts - Delivery engine → Provider adapters: sends through adapter
- Provider management → Provider adapters: tests provider
packages/core/src/providers.ts - Provider management → PostgreSQL: stores connection
packages/core/src/providers.ts - Email providers → Provider webhooks: posts delivery events
- Provider webhooks → Event reconciliation: normalizes events
- Event reconciliation → PostgreSQL: updates delivery state
- Safety governor → Redis coordination: coordinates limits
packages/core/src/safety.ts - Activity console → HTTP API: requests status
- HTTP API → Campaign lifecycle: serves lifecycle actions
apps/web/app/api/[...path]/route.ts - Email recipient → Click tracking: follows tracked link
- Click tracking → PostgreSQL: records aggregate activity
- Delivery experiments → PostgreSQL: stores run state
packages/core/src/experiments.ts - Delivery experiments → Experiment evidence: uses evidence base
packages/core/src/experiments.ts