Delivery Setup

Use Delivery if you don't want to set up an email provider. Instead of configuring SMTP credentials, you add a single delivery key and Own Auth handles the sending, queueing, and retries.

Use your own email provider if you need full control over email infrastructure, custom sender domains from day one, or if you'd rather not depend on a managed service.

Create a Delivery account and open the Own Auth dashboard. This is separate from the own-auth package because Delivery is a managed service with its own dashboard.

In the dashboard, create an app. The app name should match the product because it appears in emails sent to its users.

In the Settings tab, under Link mode, choose how auth links in emails should work.

See Hosted Links for hosted-link setup.

Go to the Keys tab and create a delivery key. Copy the key because it's shown once.

OWN_AUTH_EMAIL_DELIVERY_KEY=oad_...

In your auth.ts, configure managed email delivery with the delivery key. Set baseUrl to the website or app URL used to build auth links.

import { OwnAuthManagedEmailProvider, createOwnAuth } from "own-auth";

export const auth = createOwnAuth({
  tokenPepper: process.env.OWN_AUTH_TOKEN_PEPPER,
  baseUrl: "https://app.example.com",
  emailProvider: new OwnAuthManagedEmailProvider({
    deliveryKey: process.env.OWN_AUTH_EMAIL_DELIVERY_KEY
  })
});

That's it. Calls to requestMagicLink, requestEmailVerification, requestPasswordReset, and inviteMember now send email through Delivery instead of requiring your own email provider.

Delivery sends auth emails. That's it. Specifically:

• Receives the email request from the own-auth package running in your backend.
• Sends the email with the auth link.
• Queues and retries on temporary failures.
• Logs the delivery status (accepted, delivered, failed).

Delivery does not:

• Create users.
• Verify tokens.
• Create sessions.
• Touch your database.
• Store your user data.
• Make auth decisions.

Your backend runs own-auth, which creates the token and builds the auth URL. Delivery receives that URL and sends it in an email. The own-auth package in your backend does all the auth work.

A delivery key works in local development and sends real emails. Delivery does not provide a sandbox mode. Use a local mail catcher through a custom email provider when development messages should remain on the local machine.

To stop using Delivery, replace OwnAuthManagedEmailProvider with an EmailProvider implementation backed by the email service or SMTP client used by the application. Auth method calls do not change.

import { createOwnAuth, type EmailProvider } from "own-auth";

const emailProvider: EmailProvider = {
  async send(message) {
    await emailClient.send({
      from: "My App <no-reply@example.com>",
      to: message.to,
      subject: "Continue to My App",
      html: `<a href="${message.url}">Continue</a>`
    });
  }
};

export const auth = createOwnAuth({
  tokenPepper: process.env.OWN_AUTH_TOKEN_PEPPER,
  baseUrl: "https://app.example.com",
  emailProvider
});

Review Delivery Logs, or configure Hosted Links for a managed website or app bridge.