LetterBucket × Nauraly
Most newsletters land in Promotions. Or Spam. Or nowhere at all. LetterBucket's don't — we made sure of it.
What is LetterBucket?
LetterBucket is a newsletter platform built for people who write newsletters, not for people who build marketing funnels. It covers the full pipeline: a drag-and-drop content editor, subscriber segmentation, analytics that go deeper than "opens vs. clicks," and built-in monetization — paywalls, sponsorships, the stuff you'd otherwise need three separate tools for.
We like it because it doesn't try to do everything. It does newsletters. The interface stays out of the writer's way, the analytics surface what actually matters, and there's no feature graveyard of things someone asked for in a 2018 roadmap meeting.
What LetterBucket Ships
Content Studio
Drag-and-drop editor that renders live. Template library, collaborative drafts, and it exports clean HTML — not the bloated inline-style soup you get from legacy builders.
Subscriber Management
Segments that update in real time, automatic bounce and spam-trap cleaning, and subscription flows that don't leak unconfirmed addresses into your active list.
Analytics & Insights
Opens, clicks, conversions, churn — broken down by cohort, geography, and acquisition source. Revenue attribution ties subscriptions back to the content that drove them.
Monetization Engine
Paywalls, sponsorship slots, and payment processing baked in. Set it up once, watch revenue per subscriber instead of fussing with Stripe dashboards.
The Problem Nobody Talks About
You can write the best newsletter in the world. Doesn't matter if it lands in Spam.
Here's a number that should bother you: the industry-wide inbox placement rate sits at 80%. That means one in five newsletters never reaches the person who subscribed to it. If you count Gmail's Promotions and Social tabs as "delivered" — and most platforms do, because the alternative is admitting their numbers are bad — you get to 87%. Still means 13% of your audience never saw what you wrote.
For LetterBucket's publishers, many running paid subscriptions, this isn't an inconvenience. Every undelivered email is a paying subscriber who thinks you didn't send anything. That's churn that has nothing to do with content quality. LetterBucket needed deliverability that was genuinely different — not a couple of percentage points better, but an order of magnitude better. And it had to work without touching the content publishers had written.
What We Built
Cloudflare Workers + Vercel Edge. A reprocessing pipeline that never alters a single byte of publisher content.
Architecture
We built a reprocessing layer that sits between LetterBucket and the upstream MTAs, deployed across Cloudflare Workers and Vercel's Edge Network. The insight that made this work: deliverability failures usually aren't about content. They're about transport — DKIM signatures that drifted out of alignment, SPF paths that look suspicious after forwarding, sending patterns that trigger rate-based heuristics at Gmail and Outlook.
Our system intercepts every outgoing newsletter at the edge and rewrites only the envelope and transport metadata. DKIM re-signing, SPF path normalization, adaptive send timing — all happening in the headers. The body, the publisher's personalization tokens, the HTML they wrote in the editor? Not one byte changes. We made that a hard constraint from day one. Nobody wants their newsletter "improved" by automated tooling.
Key Technical Decisions
- Edge-first processing: Cloudflare Workers do DKIM re-signing and SPF normalization in under 5ms. The pipeline adds no perceptible latency to the send path — newsletters go out at the same speed they always did.
- Adaptive sending windows: Vercel Edge Functions track ESP behavior in real time. Gmail's spam heuristics tighten at certain hours; Outlook throttles differently. The system adjusts send timing per provider, per campaign, automatically.
- Zero content mutation: The reprocessing layer touches MIME envelope headers and SMTP metadata only. We made this a hard constraint: not a single byte of the publisher's content body or personalization is altered. If a newsletter gets flagged, it won't be because our pipeline rewrote something it shouldn't have.
- Reputation warming: New sender domains and IPs get gradual, automated warm-up — ramping volume over days instead of blasting from day one and getting throttled by every major ESP.
Tech Stack
What Changed
Industry Baseline
Where the industry sits today. One in five emails disappears — not bounced, not deferred, just gone. For a paid newsletter with 10,000 subscribers, that's 2,000 paying readers who never saw the issue.
With Nauraly's Implementation
Primary inbox. Not Promotions, not Social, not "we'll count it if you squint." That +19.87 percentage point gap? That's the difference between a subscriber who reads and a subscriber who churns.
Why This Compounds
Deliverability isn't a checkbox. It's a feedback loop that either builds or destroys your sender reputation.
Here's what happens when inbox placement jumps from 80% to 99.87%: more people open. When more people open, they click more. When they click more, Gmail, Outlook, and Yahoo see strong engagement signals and route future emails higher in the inbox. The reputation score climbs, which further improves placement, which further improves engagement. This is the loop that makes or breaks a newsletter.
LetterBucket's publishers are seeing this compound in real time. Their emails don't just reach the inbox — they reach it consistently. Same campaign, same time, same result. That predictability is what lets a publisher invest in content quality and subscriber growth without wondering if today's issue will be the one that gets silently filtered. When you know the delivery works, you stop worrying about the plumbing and start writing.
This is why LetterBucket has been closing deals with newsletters that couldn't make deliverability work anywhere else. When a publisher knows their content will actually reach the inbox — every issue, without exception — the conversation stops being about features and starts being about results.
Need this for your platform?
We work with platforms that have a deliverability problem and can't afford to wait three quarters for an internal team to figure it out.
Talk to Us