SELF-HOSTED · SMTP-POWERED · API-FIRST
DISPATCH SYSTEM / READYYour applications
have mail to send.
A quiet, dependable dispatch room for transactional email—one central SMTP account, isolated project keys, durable queues, and a complete paper trail.
SMTP credentials never enter this browser.
ONE PRIVATE DELIVERY LAYER
A self-hosted transactional email API for applications
Phefo Mail keeps one central SMTP account on the server and gives each application a separate, revocable API key. Accepted messages enter a PostgreSQL-backed queue before a worker attempts delivery, leaving an inspectable operational record.
Revoke one application without interrupting the rest of the project.
Reject unapproved From addresses before they reach the delivery queue.
Use stable event keys so network retries do not create duplicate email.
Send direct HTML or text, reusable templates, and up to ten attachments.
OPERATIONAL ANSWERS
Frequently asked questions
What is Phefo Mail?
Phefo Mail is a self-hosted transactional email API. Applications submit email over HTTP, Phefo stores each accepted message in PostgreSQL, and a background worker delivers it through a configured SMTP account.
How does Phefo Mail prevent duplicate transactional emails?
A stable idempotency key identifies one business event. If an application retries that event with the same key, Phefo returns the existing message instead of creating another delivery.
Can multiple applications use different sender addresses?
Yes. Each application can use its own revocable API key, while every From address must also be approved and active for the project before Phefo accepts it.
Does “sent” guarantee inbox delivery?
No. Sent means the configured SMTP server accepted at least one recipient. It does not guarantee inbox placement, which is decided later by receiving mail systems.