A running log of what we shipped, what we improved, and what we fixed. Newest first. No 'major releases' theatre — small changes belong here too if they affect how you use the product.
We opened up the roadmap. No NDAs, no theatre. You can see what is in production today, what we are actively building, and what we are weighing for later. The cards link out to the relevant feature pages where they exist, and we will update the dates as items move. If something on the considering list matters to you, write in and tell us — that is how the ordering gets nudged.
Three lanes: Shipped, In Progress, Considering
Tagged by area: deliverability, api, marketing, dev-experience, infrastructure, billing
ItemList schema so Google can pull individual items into rich results
SMTP2GO is a 2007-era SMTP relay with passive monitoring. The piece walks through where it still holds up (the SMTP relay basics) and where it falls behind in 2026 (no active reputation control, no marketing rail, the dashboard looks its age). Same comparison-page format as the other nine: hero, twelve-row table, three differentiators, FAQ.
12-row feature table, no fake wins
Active reputation management vs passive monitoring framing
SparkPost is interesting because it is genuinely good at monitoring and genuinely weak at acting on what it monitors. The Bird acquisition added marketing tooling but the deliverability side stayed observational. We wrote up how the Anomaly Cortex flips that — same signals, automated response, one stack for transactional and marketing instead of two.
Side-by-side on monitoring vs acting
Pricing math against SparkPost's per-message tiers
A proper landing page for our SMS API. Same routing engine, same dashboard, same audit trail — different rail. The page covers the basics: OTP latency, throughput, country coverage, DLT compliance for India. If you already use sendmsg for email, SMS is an account toggle, not a separate integration.
OTP + transactional + promotional SMS coverage
DLT compliance noted up front for Indian senders
Same auth + audit + webhook surface as the email API
Mailchimp Transactional is the rebrand of Mandrill, and it still has the weird requirement that you carry a paid Mailchimp marketing account just to use the transactional API. We wrote up the math on what that actually costs, why the block-pricing feels worse than it looks once you cross the threshold, and what a unified setup buys you.
Block pricing vs. linear per-email pricing, worked example
Why the bundled-marketing-account requirement bites
Postmark is genuinely best-in-class at transactional. The honest version of this page is not 'we win every row' — it is 'here is where Postmark is great, here is where you outgrow it, and here is what you can do about it without giving up the deliverability.' If you are happy on Postmark and not yet sending marketing, you are probably fine. If you are bolting marketing on, the math gets ugly fast.
Honest take on where Postmark stays ahead
Where unified transactional + marketing pulls ahead
Active reputation management vs Postmark's signal-only approach
Not a sendmsg comparison — a head-to-head between the two ESPs we get asked about most often. Pricing, deliverability, developer experience, scale. We pulled real pricing numbers from both vendors and worked them out at 100k, 1M, and 10M sends per month. There is a third-option note at the end, because of course there is, but the body is fair and we link out to both vendors.
Public, instant audit of any sending domain. Checks SPF, DKIM, DMARC, MX records, and a couple of common misconfigurations we see all the time. No signup, no email gate, no PDF wall — the result renders in the browser. There is a 12-page report you can request by email if you want the full breakdown, but the dashboard scoring is free and there is no upsell during the check itself.
SPF + DKIM + DMARC + MX in one pass
Runs over Cloudflare DNS-over-HTTPS — no rate limits to hit
Optional 12-page report by email, dashboard is free
Full event coverage on webhooks: delivered, bounced, deferred, blocked, complained, opened, clicked, unsubscribed. Payloads are signed, retries use exponential backoff out to 24 hours, and there is a per-endpoint dead-letter view in the console for the ones that never made it through. If your endpoint goes down for an hour, you do not lose events — we just keep retrying.
The piece of infrastructure that we are most proud of. The Cortex watches ISP signals every 30 seconds across 15 MTAs and three IP pools, and adjusts sending speed, daily limits, and warmup state per domain in real time. The point is not that we monitor — every ESP monitors. The point is the response loop is automated and fast enough that a bad hour on one domain does not turn into a bad week on the account.
30-second control loop across 15 MTAs
Per-domain reputation isolation (transactional vs marketing)
Bug fixes that nobody noticed, internal refactors, and infrastructure tweaks that do not change behavior — those stay off this page. What lands here is anything you might want to know about because it changes how the product behaves or what it can do.
Ready to send with confidence?
Dedicated sending infrastructure with 5-level reputation protection and live domain health scoring. Your reputation is managed for you.
