Skip to main content
Back to blog

The Fourth Corner of the Email-API Shortlist: Smaller Providers — Resend, Amazon SES, Mailgun, and Postmark

The tri-corner comparison closed with a dangling 'fourth corner' of smaller providers. This post closes that loop: a registry recap of the published-vs-published benchmarks, break-even math with no invented numbers, the same parity-honesty contract as the three sister posts, a walked decision tree, a buyer-run verification checklist, and honest placement for each vendor — including where Orbit loses.

Orbit Editorial Team

The three-corner comparison that frames the email-API shortlist — Mailgun vs Postmark vs SendGrid — closes by naming a "fourth corner" of smaller providers, and the migrate-or-compare hub groups its head-to-heads around the same four-vendor loop. Neither post, however, actually built that fourth corner. This post does. It is the stack-dismantling series' registry recap for the vendors outside the big-three triangle, with the same parity-honesty contract the evaluation guide and the tri-corner post already hold.

What the fourth corner actually is

The tri-corner grouped SendGrid, Postmark, and Mailgun because they hold the market's canonical email-API queries. The fourth corner is everything a shortlist picks up after those three clear: the developer-ergonomics sender (Resend), the AWS-native engine (Amazon SES), and the consolidated omnichannel answer that makes email only one line of a single account (Devotel Orbit). None of these three is a scaled-down imitation of the triangle — they differ on posture, not on size alone.

  • Resend is a developer-focused transactional email API. Email is the whole product: REST send endpoint plus official SDKs, templates rendered with React Email components rather than a dashboard editor, inbound routing by webhook. The Orbit vs Resend head-to-head and the /compare/resend page score it row by row.
  • Amazon SES is the raw send engine inside AWS: the lowest headline rate in the field, with dedicated IPs, event destinations, and the deliverability tooling priced as separate add-ons. The Orbit vs Amazon SES post and the /compare/amazon-ses page run the same criteria battery.
  • Devotel Orbit is the AI-first omnichannel platform whose Email API shares one account, one consent record, one unified customer profile, and one pay-as-you-go bill with SMS, WhatsApp, RCS, voice, video, and a built-in contact center. Orbit puts itself in frame with a disclosure, not a neutrality claim — this is a vendor-authored series.

The parity-honesty contract, restated

The three sister posts in the email-API lane — the alternatives evaluation guide, the tri-corner, the migrate-or-compare hub — share one sourcing discipline:

  1. Published or nothing. Where a comparison row cannot be verified against the vendor's published pricing page, docs, or product surface, the table leaves the cell partial rather than asserting a categorical gap.
  2. Like-for-like benchmarks, not invented numbers. No post quotes a "typical" invoice that was never seen. Break-even math is run only on published list rates across vendors — the pricing overview is the canonical anchor, and a buyer re-runs the same arithmetic on their own monthly volume.
  3. The disclosure, upfront. Orbit-in-frame paragraphs are labeled as such. The vendor-neutral table rows (Resend's code-first posture, SES's raw-engine posture) are asserted as scope, not spun as weakness.

The fourth corner keeps that contract. Every claim below resolves to a vendor's public pricing page, a public docs surface, or a shipped Orbit surface the reader can open.

The walked decision tree

The triangle maps cleanly onto the three programs an email buyer actually runs. Walk it in order; the corner you stop at depends on which question your program asks first.

1. Marketing-email volume dominates. The buyer whose sends are mostly broadcast — newsletters, promotions, lifecycle blasts — is not an email-API buyer so much as a marketing-ESP buyer. Postmark rejects that load by design; SendGrid bundles Marketing Campaigns in the same account; Mailgun carries marketing-side features without a separate product. Resend keeps the same transactional-only discipline here, and SES is an engine, not a marketing product — the broadcast-tier tooling around it belongs to a different AWS surface. The walk ends on the SendGrid or Mailgun lane, or on leaving the email-API lane entirely.

2. Mixed transactional plus marketing. The triangle's real fight. SendGrid's bundle gives both under one account, with the inbound-parse and event-destination tier ladder quoted separately; Mailgun prices on tiers with dedicated-IP options and keeps the marketing surface narrower. The trade-off is SendGrid's consolidation against Mailgun's standalone scope, and the honest answer is volume-shaped: run both on published list rates at your own monthly send volume, then read the break-even.

3. Omnichannel consolidation. The buyer who sends email beside SMS, WhatsApp, voice, and AI agent workflows asks a third question the triangle never resolves: does email stay a silo, or does it share one account, one unified customer profile, one consent record, and one bill with the rest of the stack? Resend deliberately ends at the email boundary — a second channel means a second vendor, a second integration, a second security review. SES ends at the AWS service boundary. On Orbit, the Verify API for OTP flows, the unified inbox the omnichannel shared-inbox guide walks, and the CDP hooks the CDP-vs-CRM decision frames all share the same account as email — one consent record written once, not synchronized forever. The walk ends on Orbit's Email API when that consolidation is the goal, and the /compare/pricing-overview hub holds the comparable table.

The verification checklist a buyer runs per vendor

The registry recap is only as good as what a buyer can check independently. Run this checklist on each vendor before quoting a decision upward:

  1. Published pricing page. Open the vendor's pricing page and confirm the per-message rate at your actual monthly volume, published in the table — not behind a "contact sales" gate. Orbit publishes per-channel rates against the same standard.
  2. Deliverability tooling surface. Confirm where SPF, DKIM, and DMARC verification lives: an in-product alignment check on your sending domain, or DNS instructions and a ticket queue. The deliverability playbook walks the tenant-supplied checklist.
  3. Sandbox or sandbox-key access. Send a test message against a sandbox environment or scoped test key before any DNS moves. Resend and the AWS SES sandbox both expose it; Orbit's sending-domain verification flow is built for the same order of operations.
  4. Lifecycle webhook shape. Subscribe to sent/delivered/bounced events and verify the payload on the receiving end. Orbit signs every lifecycle event per message; check each vendor's webhook docs for the same signed-receipt posture.
  5. Suppression handling. Bounces, complaints, and unsubscribe events must feed one suppression store your next send consults. On Orbit the suppression record spans email, SMS, and voice — check whether the vendor keeps it in scope or hands it to you to re-sync.

Honest placement for each vendor

The parity-honesty contract binds both directions.

  • Where Resend wins. A pure-email program run by a code-first team — templates as React components, one REST endpoint, nothing to consolidate — is a real fit. Orbit loses there not on the send core but on the ask: if email is the whole program, the omnichannel account is scope you did not buy.
  • Where Amazon SES wins. Extreme bulk on AWS with no adjacent-channel need, where the tenant operates the IP-warmup, event-forwarding, and suppression-sync work itself. Orbit does not out-price SES's raw shared-IP rate at that scale, and it does not pretend to.
  • Where the triangle still wins. SendGrid for the buyer already standardized on Twilio; Postmark for the transactional-only program that treats its scope as a deliverability feature; Mailgun for the mid-market sender who wants a standalone vendor with per-tier options.
  • Where Orbit loses. A team that wants a marketing-only ESP — broadcast lists, drag-and-drop campaign editors, marketing automation — is better served by a dedicated marketing vendor. Orbit's Email API is email as a channel, not a marketing-blast product, and the honest answer for a marketing-only program is to pick the ESP that owns it.

Frequently asked questions

Is the fourth corner one vendor or several?

Several. The triangle omits the developer-focused sender (Resend), the AWS-native engine (Amazon SES), and the consolidated omnichannel platform (Devotel Orbit) — three different postures, each with a head-to-head page linked above.

Does Resend run SMS or voice?

No. Resend is email-only by design; a second channel is a second vendor. Orbit's Email API shares an account with SMS, WhatsApp, RCS, voice, and video, so the consolidation question — not a feature gap — is the deciding axis.

Does the fourth-corner loop imply Orbit wins every row?

No. The Orbit vs Resend walkthrough names the pure-email loss explicitly, and the Orbit vs Amazon SES comparison concedes the raw bulk-on-AWS scale. The loop closes with the placement that matches the program, not with a universal verdict.

Published 15 September 2026.

The Fourth Corner of the Email-API Shortlist: Smaller Providers — Resend, Amazon SES, Mailgun, and Postmark — Orbit by Devotel