One bill. No tiers to shop.
Pay for what you send.
Transactional email is live today at a flat per-send rate. WhatsApp is listed below as a planned channel. No card to start, no per-seat fee, no platform fee.
No card. No waitlist. / Pay only for what leaves the API.
the rate sheet
Two rates live.
Three on the way.
Email is billed at a flat per-send rate. WhatsApp arrives on the same model when it ships: a flat per-send rate, no plan, no platform fee. Which engine powers a channel is our problem, not yours.
Prices in USD. Updated 2026-05-26.
-
email
Transactional only. Receipts, alerts, account events. No marketing, no bulk, no newsletters.
first 1,000 / month free
$0.20 / 1k sent -
whatsapp · utility
Receipts, shipping updates, account confirmations. Conversations are 24 hours, billed by category.
coming soon -
whatsapp · authentication
Verification codes and login challenges. Templated, region-priced and passed through at cost.
coming soon -
whatsapp · marketing
Promotional templates. Subject to opt-in policy and platform category review.
coming soon -
verified domains
DKIM, SPF, and DMARC verified at the account level. Two are free; each additional domain is a flat monthly line item.
first 2 free
$2 / month / domain
Spending grows with sending. Each recipient counts as one send: a request to ten addresses is ten billable sends, whether you batch them or post them one at a time. There is no minimum, no annual commitment, no per-seat fee, no platform fee. Volume discounts on email begin at one million sends per month and are negotiated, not posted.
do the math
What you'd pay this month.
Drop in your monthly transactional email volume and how many domains you verify. The free tiers are subtracted automatically. WhatsApp joins the estimator when that channel ships.
Estimate only. The free tier is applied per calendar month.
in every send
These six aren't paid add-ons.
All six are in every send. The same set ships on the free tier as at a million sends a month. There is no upgrade tier.
-
Multi-engine fallback.
When the primary engine times out, the chain falls through to the next. The send lands; the failed attempt stays on the record.
-
Engine abstraction.
The wire format is the contract. When the underlying delivery engine changes for cost, performance, or compliance, your code does not.
-
Retry budgets.
Configured per channel, capped per message. Failed attempts don't bill the next one as a new send.
-
Normalized errors.
Six error categories across every engine, so one failure path covers all of them.
-
90-day delivery log.
Full per-attempt history, searchable. Storage is not a paid add-on.
-
Scheduled sends.
ISO 8601 in the payload, the engine holds and dispatches. No queue to run on your side.
questions, answered
Six things people ask first.
-
What counts as one send?
One delivery to one recipient on one channel. A request with ten recipients is ten billable sends, whether you batch them in a single API call or post them one at a time. A retry by the orchestrator after a provider timeout does not count as a new send; you pay once per recipient, even if delivery took three attempts.
-
When does WhatsApp ship?
Email is the only billable channel today. WhatsApp arrives on the same request shape you already see in the docs and uses the same flat per-send pricing model when it ships. Which underlying engine handles a channel is an internal decision and may change without changing the API.
-
Why only transactional email?
Comms is built for receipts, alerts, codes, and account events: low-latency, high-deliverability traffic where every send matters. Marketing email is a different deliverability problem (warmup, segmentation, complaint loops) and we don't want to compromise transactional reputation by sharing the same IP pool.
-
Do you charge for failed deliveries?
No. A message that's never accepted by any provider in the fallback chain is not billed. A message that's accepted and later bounces is billed for the accepted send, the same way every provider in the industry handles bounces.
-
Can I self-host the orchestrator?
Not today. The platform runs as a managed service; self-hosted is on the roadmap but not committed. If you need an air-gapped deployment, talk to us first.
-
What happens if we outgrow this page?
At one million email sends per month or comparable volume on WhatsApp, the rate becomes negotiated, not posted. Reach out and we'll quote it.
ready when you are
Send your first message in fifteen minutes.
No card. No waitlist. The API key is one click away.