Verified webhooks
Each domain has its own secret webhook token, plus an optional Svix signature check; the message body is then fetched back from Resend with that domain’s key.
Email holds your customers’ most sensitive conversations, so RelayRow is secure by default: every inbound webhook is verified, provider keys live in a vault, the database enforces who can see what, and untrusted HTML never runs in your browser.
Updated
Each domain has its own secret webhook token, plus an optional Svix signature check; the message body is then fetched back from Resend with that domain’s key.
Resend and AI provider keys are stored in Supabase Vault, write-only from the interface, and never sent to the browser.
Every table enforces access in the database itself, so a workspace can only ever read its own domains, mailboxes and mail.
HTML messages render in a locked sandbox with scripts disabled and remote images blocked.
Every inbound message is scored before anyone opens it, and rules can quarantine it.
Owner, admin, domain admin and operator roles, plus viewer, agent and owner seats per mailbox.
| Database | PostgreSQL on Supabase with row-level security on every table |
|---|---|
| Secrets | Supabase Vault; only the last characters of a key are ever shown |
| Inbound mail | Per-domain token, optional Svix signature, fetch-back with the domain’s key |
| Webhooks out | HMAC-SHA256 signature header on every automation webhook |
| AI usage | Every call logged with feature, model, mailbox and cost |
| Audit | System logs for inbound mail and automation runs |
Connect your first domain in minutes — no mail server, no IMAP, no glue code. AI and automations included.