// developers · integrations

Fits the stack you already run.

Drin speaks standard REST, SMTP and webhooks — so it slots into the tools you already use. Send your Supabase auth mail through Drin, ship your key as a Vercel env var, relay from any framework, and receive events on your own endpoint.

supabase auth · smtp settings
# Supabase → Project Settings → Auth → SMTP
host      smtp.drin.run
port      465
username  drin
password  $DRIN_API_KEY
sender    auth@yourapp.com
// connects with[01/03]

No glue code required.

These aren't bespoke integrations to maintain — they're the open protocols Drin already speaks. If a tool can point at an SMTP host, set an environment variable, or POST to a URL, it works with Drin today.

Setup guides in the docs →

SupabaseAuth SMTP
VercelEnv & deploy
SMTPAny app
WebhooksYour endpoint
// how it wires up[02/03]

Two of the most common setups.

Supabase — Auth SMTP provider

Point your Supabase project's Auth SMTP at smtp.drin.run on port 465, use drin as the username and your API key as the password. Supabase confirmation, magic-link and reset emails now send through Drin — authenticated, suppressed and tracked like any other send.

Vercel — env var & deploy

Add your key as a DRIN_API_KEY environment variable in your Vercel project, then read it from any serverless function, route handler or edge route. No SDK lock-in — a plain fetch to the REST API works on every Vercel runtime.

SMTP — any app

Already have a mailer? Repoint Nodemailer, Django, Rails or Postfix at smtp.drin.run with your key as the password. No rewrite, same delivery pipeline as the REST API.

Webhooks — your endpoint

Register an HTTPS endpoint and Drin POSTs signed delivery, bounce, complaint and open events as they happen. Verify the signature, update your database, and react in real time.

// pairs well with[03/03]
// wire it up

Slot Drin into your stack today.

Grab a key, set one env var or four SMTP settings, and you're sending. Test in the sandbox; production starts at $3 a month.