Skip to content
3AVA Mail

Introduction

3AVA Mail is a self-hosted, Resend-compatible email API. It does two jobs:

  1. Transactional sending — single emails fired by your app: receipts, password resets, magic links.
  2. Marketing campaigns — bulk sends to lists with AI-assisted templating, IP rotation, and engagement tracking.

Both run on the same sending pipeline, the same IPs, and the same domains. Both feed the same webhook stream and dashboard.

Why another email API?

Section titled “Why another email API?”

If Resend works for you, use Resend. 3AVA Mail exists for teams that want:

  • Per-send economics close to zero — you bring your own SMTP relays and IP pools.
  • Wire-level compatibility with Resend — drop-in SDKs, same request bodies, same webhook events.
  • Marketing tooling on the same platform — campaigns, list verification, AI subject generation, warmup orchestration.
  • Self-hosted control — your domains, your IPs, your reputation, your data.

What it ships with

Section titled “What it ships with”
  • REST API (reference)
  • SvelteKit dashboard for domains, lists, campaigns, and email inspection
  • Async worker pool (arq) for outbound sending, bounce handling, and warmup pacing
  • Postgres + Redis for state and queueing
  • Built-in HMAC tracking pixel + click rewriter
  • VERP bounce processing
  • One-click RFC 8058 unsubscribe

What it doesn’t do

Section titled “What it doesn’t do”
  • Run your SMTP relays — you provide them. 3AVA Mail rotates across them.
  • Buy IPs for you — bring your own pool.
  • Replace Postmaster Tools / SNDS — use those for inbox-side reputation monitoring.
  • Block based on a content moderation classifier — that’s on your stack to add.

The shape of an integration

Section titled “The shape of an integration”
your app  ──HTTPS──▶  3AVA Mail API  ──SMTP──▶  your relay pool  ──▶  recipients
                          │                                              │
                          ▼                                              │
                    Postgres + Redis   ◀──VERP bounces / inbound replies─┘
                          │
                          ▼
                  webhooks → your app

You hold three things: an API key, a verified domain, and a webhook endpoint. Everything else is handled.

Where to next

Section titled “Where to next”