Why do teams look for an alternative to Mailgun and SendGrid inbound?
The limits Mailgun and SendGrid inbound documents itself:
- Mailgun includes 1 inbound route on its Free plan and 5 on Basic; Foundation and Scale include unlimited routes. source: mailgun.com
- Mailgun's store() action keeps a message for up to 3 days. source: documentation.mailgun.com
- SendGrid's pricing page lists the Inbound Parse Webhook on Pro and Premier, not on Essentials. source: twilio.com
- SendGrid drops inbound messages it cannot deliver to the webhook after 3 days, and the total message size limit is 30MB. source: twilio.com
What does Mailgun and SendGrid inbound do well?
- Mailgun routes can match by recipient or header and forward to several URLs or addresses. source: documentation.mailgun.com
- SendGrid can run an optional spam check on messages of 2.5 MB or smaller and add the report to the payload. source: twilio.com
What are the alternatives?
nofeb
- Point the MX at nofeb instead, and get SPF, DKIM, ARC and DMARC verification and spam and virus checks before acceptance.
- A rotatable organization token on every provider URL; rotating it stops every earlier token at once.
- A prompt-injection score and a sender trust level on every message, whichever provider it arrives through, using that provider's authentication results.
Postmark inbound
Inbound processing on its Pro and Platform plans, posting JSON with an optional RawEmail field. source: postmarkapp.com
Cloudflare Email Routing
Free forwarding to addresses, and processing through Email Workers. source: developers.cloudflare.com
How does a Mailgun and SendGrid inbound setup map to nofeb?
| On Mailgun and SendGrid inbound | On nofeb |
|---|---|
| Mailgun route with forward() | Forward to your nofeb Mailgun URL, which ends in /mime so Mailgun posts the raw message. |
| SendGrid Inbound Parse | Set your nofeb SendGrid URL as the destination and tick "POST the raw, full MIME message". |
| Your parsing code | reply_text, safe_body, one-time codes, links and attachment text on every message. |
| Your storage and threading | Inboxes, threads, folders and typed metadata, with raw messages downloadable byte-exact. |
| Your retry and dedup logic | Redeliveries are delivered once; message.received is emitted once per message and inbox. |
How does pricing compare?
- Mailgun and SendGrid inbound: Mailgun Basic costs $15 a month for 10,000 emails and includes 5 inbound routes. source: mailgun.com
- Mailgun and SendGrid inbound: SendGrid Pro starts at $89.95 a month and lists the Inbound Parse Webhook as included. source: twilio.com
- nofeb Free: $0 a month, inboxes 10, 3,000 messages processed a month, usage past the allowance refused.
- nofeb Build: $19 a month, inboxes Unlimited, 25,000 messages processed a month, usage past the allowance billed.
- nofeb Scale: $99 a month, inboxes Unlimited, 250,000 messages processed a month, usage past the allowance billed.
- nofeb Enterprise: Custom, inboxes Unlimited, custom messages processed a month, usage past the allowance billed.
The pricing page has nofeb's unit prices.
When is Mailgun and SendGrid inbound the better choice?
- You only need a parsed POST of each email and already handle storage and threading. source: documentation.mailgun.com
Frequently asked questions
What is an alternative to SendGrid Inbound Parse?
If the mail is for an agent, an inbox API that stores, threads and parses it: nofeb receives on its own MX or behind SendGrid, and calls your webhook with message.received.
Do I have to move my MX to use nofeb?
No. Keep Mailgun, SendGrid, Postmark or Cloudflare in front and forward with your inbound token.
Status of everything on this page
Every capability named above, with its status as reconciled against the engine.
| Capability | What it does | Status |
|---|---|---|
| Inbound from the provider you already use | Receive through Cloudflare Email Routing with an Email Worker on your own zone, a Postmark inbound stream, a Mailgun route, SendGrid Inbound Parse, or any service that can POST a raw message. Each path is authenticated by your organization's inbound token, which you can rotate at any time, and delivers only to your own inboxes and verified domains. | Shipped |
| Inbound mail server that checks mail at the door | nofeb's own MX receives mail for the shared domain and your custom domains, with STARTTLS. It checks every recipient before accepting any data, verifies SPF, DKIM, ARC and DMARC, and scans for spam and viruses before it answers. Mail that fails a DMARC reject policy, carries a virus or is clearly spam is refused during delivery instead of bounced later; likely spam and DMARC-quarantined mail is filed into Junk. Every message carries a security verdict with its authentication, spam, virus and TLS results. | Shipped |
| Reply extraction | Each message carries its new text with quoted history and signature removed. | Shipped |
| safe_body for untrusted mail | The message's new text with zero-width and direction-altering characters, hidden HTML and forgeable quoted history removed, wrapped in a provenance header that tells the model whose words these are. | Shipped |
| One-time code and link extraction | Verification codes and classified links are pulled out of every message and returned as fields. | Shipped |
| Attachment text | Attachments are listed with their extracted text and can be downloaded byte-exact. | Shipped |
| Byte-exact raw messages | Download any stored message exactly as it was received. | Shipped |
| Signed webhooks with required scope | Standard Webhooks signatures, retries and a delivery log. Scope (organization, pod or inbox) is required, so a subscription never silently widens to everything. | Shipped |
| Injection scoring and quarantine | Every inbound message gets a prompt-injection score from 0 to 1 with its reasons: hidden text, invisible and look-alike characters, instructions aimed at an AI, role and chat-template tokens, tracking beacons, data-carrying links and encoded payloads. Above the threshold you set per organization, pod or inbox, the message is quarantined (or only flagged) for a person to release or delete, and its content stays out of the delivery event. | Shipped |
| Sender trust on every message | Each inbound message is labelled trusted, known, unknown or suspicious, with the reasons: its authentication results, your sender lists, look-alike domains, display-name spoofing, and whether the inbox has corresponded with the sender before. | Shipped |