What it does
MailPace sends application emails through HTTP or SMTP and converts incoming messages into JSON for your webhook. It combines delivery tracking and bounce handling with reply processing. A free plan for up to 100 emails per month is available by contacting support; paid usage counts both sending and receiving.
MailPace can receive at an address that was not created in advance. After a domain and webhook are configured, different local parts such as a project or conversation identifier can reach the same inbound application flow. For a service that accepts replies by email, this lets the receiving application decide which record a message belongs to rather than requiring a mailbox to be provisioned for every conversation.
The initial inbound setup requires a domain, a destination webhook and the documented DNS record. Sending is available through HTTP or SMTP. Usage billing counts both sent and received emails, so reply-heavy applications need to budget for both directions. A free plan of up to 100 emails per month is available by requesting it from [email protected]. Standard retention is 30 days, with a different period arranged through support.
Register using your email and a password to manage domains and delivery. On paid accounts, usage above the base allowance is added automatically to that billing period's charge.
Strengths
- Inbound addresses do not need to be individually defined beforehand
- The service combines outgoing delivery with incoming webhook processing
Watch out for
- Received messages contribute to usage billing as well as sent messages
- The small free plan requires contacting the vendor for access
Best for
- Application teams handling email replies as structured application events
Sources
- MailPace - Fast Transactional Email API for Developers | Privacy-First, EU-Hosted (Oct 25, 2026)
- MailPace - Receive and process inbound emails with ease — MailPace (Oct 25, 2026)
- Pricing - MailPace (Oct 27, 2026)
- Register - MailPace (Oct 27, 2026)