Emails your app depends on, delivered to the inbox.
Send password resets, receipts, sign-in codes and alerts from your own domain, over SMTP or a simple HTTP API. See what happened to every message.
- From $69/month for 10,000 emails
- Your domain, signed with DKIM, checked with SPF and DMARC
- Works with Laravel, WordPress, Node.js, Django and any SMTP app
# Send a password reset from your app curl -X POST https://postal20.phluit.net/api/v1/send/message \ -H "X-Server-API-Key: $PHLUIT_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "from": "Acme <noreply@mail.acme.com>", "to": ["ana@example.com"], "subject": "Reset your password", "html_body": "<p>Choose a new password…</p>" }' # → {"status": "success", "data": {"message_id": "…"}}
Reliable email, without running a mail server
Your app hands us the message; we sign it, send it, retry it, and tell you what happened.
Live in minutes
Add your domain, copy four DNS records, create a key and send. If your app can send email over SMTP, it already works with us.
Built for the inbox
Every message is signed with your domain's DKIM key and leaves from an IP that carries transactional mail only. Addresses that bounce go on a do-not-send list automatically.
Costs you can predict
A fixed monthly plan with an hourly limit. Busy month? Extra emails are $3.50 per 1,000, capped at 100% more than your plan, so there is never an open-ended bill.
Send your first email in four steps
Everything happens on the Email page of your Phluit portal. No new dashboard to learn.
- 1
Add your sending domain
Add a domain such as
mail.acme.comand copy the SPF, DKIM, return path and DMARC records to your DNS. - 2
Verify it
Click Check DNS. As soon as the DKIM record is found, the domain can send.
- 3
Create a key
An SMTP key is your SMTP password; an API key goes in the
X-Server-API-Keyheader. Use one per app. - 4
Send
Point your app at
postal20.phluit.net:587or post to the API, and watch messages arrive in your activity log.
# Send a password reset from your app curl -X POST https://postal20.phluit.net/api/v1/send/message \ -H "X-Server-API-Key: $PHLUIT_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "from": "Acme <noreply@mail.acme.com>", "to": ["ana@example.com"], "subject": "Reset your password", "html_body": "<p>Choose a new password…</p>" }' # → {"status": "success", "data": {"message_id": "…"}}
# .env MAIL_MAILER=smtp MAIL_HOST=postal20.phluit.net MAIL_PORT=587 MAIL_ENCRYPTION=tls MAIL_USERNAME=your-username # shown on your Email page MAIL_PASSWORD=your-smtp-key MAIL_FROM_ADDRESS=noreply@mail.acme.com // anywhere in your app Mail::to($user)->send(new PasswordReset($token));
import nodemailer from 'nodemailer'; const mail = nodemailer.createTransport({ host: 'postal20.phluit.net', port: 587, secure: false, auth: { user: process.env.SMTP_USER, pass: process.env.SMTP_KEY }, }); await mail.sendMail({ from: 'Acme <noreply@mail.acme.com>', to: 'ana@example.com', subject: 'Your receipt #1042', html: receiptHtml, });
import os, smtplib from email.message import EmailMessage msg = EmailMessage() msg["From"] = "Acme <noreply@mail.acme.com>" msg["To"] = "ana@example.com" msg["Subject"] = "Your sign-in code" msg.set_content("Your code is 482913") with smtplib.SMTP("postal20.phluit.net", 587) as s: s.starttls() s.login(os.environ["SMTP_USER"], os.environ["SMTP_KEY"]) s.send_message(msg)
# Any SMTP plugin, e.g. WP Mail SMTP → "Other SMTP" SMTP Host postal20.phluit.net Encryption TLS SMTP Port 587 Authentication On SMTP Username your-username SMTP Password your-smtp-key From Email noreply@mail.yourshop.com # Order emails, password resets and form notices # now go out through Phluit, signed with your domain.
Know what happened to every email
When a customer says “I never got the email”, you can check in seconds.
- Search every message by recipient
- See what was sent, held or bounced, and why
- A do-not-send list that stops mail to addresses that bounce
- This month's usage, with any extra emails, at a glance
| Time | To | Subject | Status |
|---|---|---|---|
| 10:42 | ana@example.com | Reset your password | Sent |
| 10:41 | li.wei@example.org | Your receipt #1042 | Sent |
| 10:39 | old.mail@example.net | Welcome to Acme | Bounced |
| 10:37 | sam@example.com | Your sign-in code | Sent |
| 10:35 | joe@example.io | Your order has shipped | Held |
A clean IP, because nobody sends newsletters from it
Inbox providers judge mail by where it comes from. Ours carries only mail people expect.
What you can send
- Password resets and sign-in codes
- Receipts, invoices, order and shipping updates
- Account notices, and alerts your users set up
What you can't send
- Newsletters, promotions and other marketing
- Cold email, or mail to bought or scraped lists
- Mail on behalf of other businesses
We review every new account before it can send (usually within one working day), start new senders at half their hourly limit for 30 days, and pause sending that looks like abuse. See our Acceptable Use Policy.
Plans that scale with your email
Billed monthly, cancel any time. Every plan includes SMTP, the HTTP API, the activity log and bounce handling.
Starter
10,000 emails a month
- 10,000 emails a month included
- Up to 500 emails an hour
- Extra emails $3.50 per 1,000
- SMTP (587/25) and HTTP API
- Activity log and do-not-send list
Business
50,000 emails a month
- 50,000 emails a month included
- Up to 2,000 emails an hour
- Extra emails $3.50 per 1,000
- SMTP (587/25) and HTTP API
- Activity log and do-not-send list
Custom
More than 50,000 emails a month
- Volume and hourly limits sized to your app
- Help moving from another provider
- A setup review with our team
Email Sending FAQs
What is transactional email?
Email a person gets because of something they did or because they have an account with you: password resets, sign-in codes, receipts and invoices, order and shipping updates, account notices and alerts they set up. It is expected, personal and usually urgent, which is why it has to reach the inbox.
Can I send newsletters or marketing email?
No. Email Sending is for transactional email only: no newsletters, promotions, cold email or mail to bought or scraped lists. Keeping marketing off our sending IP is what keeps it trusted by Gmail, Outlook and Yahoo. For newsletters, use an email marketing provider alongside us.
How do I connect my website or app?
Over SMTP (postal20.phluit.net, port 587 or 25 with STARTTLS) or with one HTTP request to our API. Anything that can send through SMTP works: Laravel, Rails, Django, Node.js, PHP, WordPress plugins and most SaaS tools. Your Email page in the portal shows your exact settings.
Which DNS records do I need?
Four: SPF and DKIM (TXT), a return path (CNAME) that receives bounces, and a DMARC record we recommend. The portal shows each value with a Copy button and checks them live; your domain can send as soon as its DKIM record is found.
What happens if I send more than my plan?
Extra emails cost $3.50 per started 1,000, on an invoice on the 1st of the next month, up to 100% more than your plan. After that, new messages are held until the 1st, so a bug in your app can never run up an open-ended bill. Each plan also has an hourly limit.
Why do new accounts need approval?
We review every new account before it can send, usually within one working day, and new senders start at half their hourly limit for 30 days. It keeps abusers off the shared IP, so mail from every customer, including yours, keeps landing in the inbox.
Who can order Email Sending?
Customers with an active hosting or app service at Phluit and at least one paid invoice. A domain on its own doesn't qualify. You order it from the Email page of the portal.
Can I receive email or get mailboxes with it?
No. Email Sending only sends email from your apps. Replies go to whatever address you set as Reply-To, such as your existing support mailbox.
Send your first
email today
Add your domain, create a key and connect your app in minutes. Not sure it fits what you send? Ask us first.
