Send email over SMTP without rewriting your application.

Point Nodemailer, Rails, Django, Laravel, or your internal tools at Bird’s regional SMTP servers by swapping your host and credentials. Your existing mailer code and MIME messages stay as they are, and your sends gain automatic DKIM signing, hard-bounce suppression, real-time delivery webhooks, and searchable message logs.

Trusted by engineering and product teams
shipping at global scale.

Verify your sending domain and DNS
before you switch your traffic over.

Pointing production mail at an unverified domain causes immediate rejections or spam placement. Ask Bird MCP from your editor to confirm that your DKIM and return-path DNS records are verified, then drop your regional SMTP host and API key into your app’s environment variables.

Keep your existing mailer code and set
delivery defaults on each API key.

Drop Bird’s regional host, port, and API key into your mail library and keep your existing HTML templates, custom headers, and file attachments untouched. You can assign category, IP pool, tag, and open or click tracking defaults to each API key so your billing service, CRM, and internal tools each send with their own rules.

Connect over implicit TLS on port 465 or STARTTLS on ports 587 and 2525, and include an idempotency header so SMTP client retries after a dropped connection do not send duplicate emails.

Track deliveries, bounces, and webhooks
just like an API send.

Traditional SMTP relays leave you guessing what happened after your server hands off a message. Bird returns a trackable message ID in the SMTP response, streams acceptance, delivery, deferral, and bounce events to your dashboard and signed webhooks, and automatically suppresses hard bounces and spam complaints.

Your domain.
Your reputation.

Verify your domain and separate transactional and marketing traffic to protect your sender reputation. Bird automatically suppresses addresses after a hard bounce.

SMTP relay, explained.

What credentials does Bird SMTP use?

Set the SMTP username to bird and use a regional API key with email sending permissions as the password. Connect to eu1.smtp.bird.com or us1.smtp.bird.com to match your key’s region. Giving each application its own API key lets you set separate IP pool, category, and tracking defaults, and revoking a key cuts off its SMTP access within seconds.

Which ports are supported?

Use port 465 for implicit TLS, or ports 587 and 2525 for STARTTLS over TLS 1.2 or 1.3. Port 2525 is a drop-in alternative when your cloud network or firewall blocks port 587. Bird requires TLS encryption before accepting credentials and does not offer port 25 for mail submission.

Can SMTP render a stored Bird template?

No. Bird SMTP sends the exact MIME message your application submits, including your rendered HTML, plain-text body, headers, and attachments up to 20 MB. This works well when your framework or internal tool already builds messages in code; when you want Bird to render a stored template with dynamic variables, send through the Email API instead.

Scale without losing control.

Separate production and sandbox traffic into dedicated workspaces, scope API keys to the exact channels each service or agent needs, and track permission changes in the audit log.

Go further.
With Email.

Transactional sending, marketing campaigns, and deliverability tools in one place.

Start with one channel and expand as you grow.

Add new channels, verification, and connectivity in the same workspace, using the same API keys, webhooks, and SDKs.

Your next idea. Ready to connect.

Start building with Bird in minutes.