scribase
Scribase Mail

Self-hosting a Resend-compatible email API: what it really takes

People search for a self-hosted Resend because they want to own their sending or avoid another vendor. Here is what that means in practice, and what Scribase Mail offers instead: a hosted Resend-compatible API, not a package you run. Scribase Mail does not offer a self-hosted version today.

Last checked November 13, 2026.

What you need to run yourself

Postal is a mature open-source mail server if you do want to run the whole thing, including your own MTA and IPs. It does not speak the Resend API, so your resend SDK code changes.

  • An outbound path. Most clouds block port 25 for new accounts, so you end up relaying through a provider anyway (Oracle Cloud Email Delivery, Postmark, Mailgun or similar), which is what Scribase Mail does too.
  • DKIM signing per domain, SPF and DMARC records, and a check that they resolve before anyone sends.
  • A queue with retries and backoff, bounce and complaint handling, a suppression list and one-click unsubscribe headers.
  • Webhook signing and delivery with its own retries.
  • Reputation: warm-up, daily caps for new senders, and a way to pause a bad sender before it hurts the rest of your mail.

What Scribase Mail gives you instead

A hosted Resend-compatible API at mail-api.scribase.com: verified domains with DKIM, SPF and DMARC, signed webhooks the resend verifier accepts, test keys that simulate sends, suppressions and one-click unsubscribe, teams with roles, and a dashboard. Your resend SDK code keeps working with a new base URL.

Not yet: contacts, broadcasts, templates, inbound email, SMTP submission and a self-hosted build.

Scribase Mail plans (USD a month), from the live /billing/plans endpoint
PlanPriceEmails a monthDaily capDomainsWebhook endpointsOver the quota
Free$03,00010011Sending stops
Pro$2050,000None105$0.80 per 1,000
Scale$90150,000None1,00020$0.60 per 1,000

Start in four steps

  1. Step 1

    Sign in

    Magic link at https://mail.scribase.com. No password, no card.

  2. Step 2

    Add your domain

    Publish the DKIM, SPF and DMARC records the dashboard shows, then verify.

    sh
    curl -X POST https://mail-api.scribase.com/domains \
      -H "Authorization: Bearer $SCRIBASE_MAIL_KEY" \
      -H "Content-Type: application/json" \
      -d '{"name":"mail.example.com"}'
  3. Step 3

    Create a key

    A full_access key for setup, a sending_access key locked to one domain for app servers, or an sk_test_ key to try everything without a domain.

  4. Step 4

    Point the resend SDK at the new host

    One option, or one environment variable.

    ts
    const resend = new Resend(process.env.SCRIBASE_MAIL_KEY, { baseUrl: 'https://mail-api.scribase.com' })
FAQ

Questions people ask

Is it really Resend-compatible?

For sending, yes: the official resend npm SDK pointed at mail-api.scribase.com reaches the server and gets Resend-shaped responses, and webhooks verify with resend.webhooks.verify(). Contacts, audiences, broadcasts, templates and inbound routes are not served yet.

Can I run Scribase Mail on my own server?

Not today. Scribase Mail is a hosted service and its source is not published. If you need to run your own mail server, Postal is the usual open-source choice.

Does it include marketing email?

Not yet. There are no contacts, audiences or broadcasts. One-click unsubscribe headers and a suppression list are included for transactional mail.