Architecture

Truncus separates email delivery into two distinct layers.

Transport layer

Email transport is handled by AWS SES (eu-west-1).

SES provides global deliverability infrastructure, established mailbox provider relationships, and bounce and complaint detection.

Truncus uses SES strictly as the transport layer. SES is not exposed in the API surface.

Control plane

The Truncus control plane runs in EU infrastructure.

Responsibilities:

• Deterministic delivery state resolution
• Event storage (90-day retention)
• Webhook dispatch and retry
• Idempotency enforcement
• Replay system
• Suppression list management

Your API key, account data, delivery events, and webhook history are stored in EU infrastructure. SES handles only the transport.

Delivery flow

1. API request received by control plane
2. Request validated (API key, payload, domain authorization)
3. Email submitted to transport layer (SES)
4. Terminal state resolved from SES feedback
5. Event stored in EU control plane
6. Webhook dispatched to your endpoint

Why this separation exists

Most email APIs expose transport acceptance as their delivery status. Acceptance means the receiving server agreed to process the message — not that it reached the inbox.

By maintaining a separate control plane on top of the transport layer, Truncus can:

• Resolve and store terminal delivery state independently of transport
• Keep all EU-regulated data in EU infrastructure
• Provide replay without re-sending
• Enforce idempotency across retries

Data residency

Transport layer: AWS SES (global, eu-west-1).

Control plane: EU infrastructure.

Account data, event logs, webhook history: EU.

Van Moose, KvK 97411698 (Netherlands).