Postmark vs Resend for a UK indie hacker in 2026: the actual decision

You shipped your MVP last weekend with Claude Code. You wired up Resend because it was in the tutorial. You have 50 signups and everything works. Then someone mentions Postmark and you start second-guessing yourself.

Stop. This post is the UK-grounded version of that decision - with GBP pricing, UK ISP deliverability notes, DUA Act 2025 data residency implications, and a clean decision matrix by use case. No US-centric hedging, no vague "it depends."

TL;DR

First 12 months of a UK indie SaaS: Resend. Free tier covers most MVPs (3,000 emails/mo with a custom domain on Hobby), the React Email and Next.js 16 integration is native, and EU data residency makes UK GDPR compliance straightforward.

When password resets and payment receipts genuinely cannot miss the inbox: Postmark. The Microsoft 365 deliverability edge, strict IP reputation management, and built-in transactional vs broadcast separation become worth the higher entry cost once you have paying users.

Start with Resend. Migrate to Postmark (or add it as a secondary stream) when your revenue justifies it. The migration takes a weekend.

GBP pricing breakdown

Both services publish in USD. Converted at a typical 2026 rate of GBP 1 = USD 1.27.

Resend pricing in GBP

Tier	USD/mo	GBP equiv	Included emails	Custom domain	EU region
Free	$0	GBP 0	3,000/mo	No (shared subdomain)	No
Hobby	~$20	~GBP 16	3,000/mo	Yes	Yes
Pro	~$100	~GBP 79	50,000/mo	Yes	Yes
Pro (100k)	~$190	~GBP 150	100,000/mo	Yes	Yes

A note on the free tier: you get 3,000 emails per month on a shared Resend subdomain. For a UK SaaS in beta with no domain auth, that is fine for internal testing but not for production - UK users' spam filters will penalise the shared sending domain. Hop to Hobby at GBP 16/mo as soon as you want reliable inbox placement on your own domain.

VAT note: Resend Inc. invoices from the US without a GB VAT line item. UK-VAT-registered businesses can handle under reverse charge; most below-threshold indie hackers cannot reclaim. Factor this in if you are close to the GBP 90,000 VAT registration threshold.

Postmark pricing in GBP

Tier	USD/mo	GBP equiv	Included emails	Notes
Developer (free)	$0	GBP 0	100/mo	Yes, only 100 - barely enough for dev testing
Starter	~$15	~GBP 12	10,000/mo	Custom domain, both streams
Growth	~$50	~GBP 39	40,000/mo	Included open/click analytics
Business	~$100	~GBP 79	100,000/mo	Priority support SLA

Over 100,000 emails: per-1,000 pricing kicks in, roughly USD 1.25/1,000 (GBP ~0.98/1,000).

Postmark's Developer free tier is a trap. 100 emails per month is 3-4 emails a day - enough to trigger a signup confirmation in dev but not production. Budget GBP 12/mo from day one of production sends, even at low volume.

Postmark invoices via a UK entity and applies UK VAT correctly - cleaner for bookkeeping than Resend's US invoices.

Free-tier reality: the maths for an early-stage UK indie SaaS

Scenario	Emails needed	Resend free	Postmark free
50 signups, welcome + activation sequence	~150 emails	Covered	Covered (just)
200 signups, welcome + 3-step onboarding	~800 emails	Covered	Not covered - need paid tier
500 signups, welcome + receipts + nudges	~2,500 emails	Covered (free)	Not covered - GBP 12/mo
1,000 signups, full onboarding + weekly digest	~6,000+ emails	Not covered - GBP 16/mo	Not covered - GBP 12/mo

At MVP stage with sub-200 signups, Resend's free tier is genuinely viable. Postmark's 100-email free tier is a developer sandbox, nothing more. This difference alone makes Resend the default for a UK indie SaaS in months 1-6.

UK-specific deliverability quirks

This is the section that does not exist anywhere else in the Postmark vs Resend discourse. Here is what actually matters for UK inboxes.

BT Internet, Virgin Media, Sky, TalkTalk

UK consumer ISPs run their own MTAs with varying spam tolerance. For clean transactional sends from a properly configured domain - SPF, DKIM 2048-bit, DMARC at least p=none - both Resend and Postmark perform reliably. The deliverability gap at consumer ISP level is negligible if your domain auth is clean; when it goes wrong it is almost always a misconfigured SPF or missing DKIM, not the provider's IP reputation.

TalkTalk's MTAs are the most aggressive of the four - they reject mail from shared sending IPs fastest. One more reason to move off Resend's shared subdomain onto your own domain via Hobby at GBP 16/mo as early as possible.

Microsoft 365 (UK B2B inboxes)

This is where Postmark earns its premium. Microsoft 365 is the dominant inbox for UK B2B SaaS customers - if your SaaS sells to UK businesses, most of your users' email arrives via M365 tenants administered by an IT team that has probably tightened EOP (Exchange Online Protection) rules.

Postmark has a measurable edge on M365 deliverability for time-sensitive transactional sends. Their strict at-signup account screening (they will reject your account if your sending patterns look bulk) means their IP pools carry strong reputation scores with Microsoft's anti-spam infrastructure. Password resets and payment confirmation emails from Postmark land in M365 primary inboxes faster and with fewer Junk folder incidents than Resend.

Resend performs well on M365 for standard sends, but if your UK SaaS is B2B with a password reset that a user is waiting for right now, Postmark's M365 reputation advantage is tangible.

Gmail UK Workspace

Both providers perform well on Gmail (consumer and Google Workspace). Google's reputation signals are brand-level (your domain) rather than IP-level for established senders, so once your domain is warmed up and DMARC is tightened past p=none, the provider gap closes. No strong preference here.

Data residency: DUA Act 2025 and UK GDPR Chapter V

Every generic Postmark vs Resend article skips this entirely. UK founders cannot.

Resend: EU processing (Ireland)

Resend processes data in Ireland, covered by the UK's adequacy decision for EU/EEA countries. Email data stays in an adequacy-covered jurisdiction - no IDTA, no SCCs required for the transfer leg.

Your privacy policy needs to disclose Resend as a sub-processor and state EU processing. That is it.

Postmark: US processing (Virginia)

Postmark processes data in the United States (Virginia). The UK has not granted the US adequacy status, which means a UK-to-US transfer of personal data (which email data is - it contains email addresses at minimum) requires a valid transfer mechanism under UK GDPR Chapter V.

The standard route is the IDTA - the UK Addendum to the EU SCCs, approved by the ICO. Postmark supplies a DPA you can sign in their dashboard; reference the IDTA in your privacy policy and ROPA. Thirty-minute admin task, not a blocker - but additional overhead that Resend's EU processing avoids.

DUA Act 2025 specifics

The DUA Act 2025 updated the UK's data governance framework but did not change the international transfer rules governing email processors. It emphasises accountability and transparency - your ROPA must reflect which sub-processors handle email data and where. Both providers need an Article 28 DPA; Postmark additionally needs the IDTA documented.

Developer experience for a UK indie hacker

Resend

Resend was built for modern JavaScript stacks. If you are shipping with Next.js 16, TypeScript, and React Email, the integration is native - import { Resend } from 'resend' and you are sending in 5 minutes. React Email components render identically in development and production, killing the "looks fine in dev, broken in Gmail" problem.

Resend Audiences is the built-in contact management layer - segment contacts, tag them, and wire up a newsletter without a separate tool. For a UK indie SaaS targeting its first 1,000 subscribers, this removes the need for any other email marketing service.

Webhook-first event model: delivery, open, click, bounce, and spam complaint events push to a webhook endpoint. Straightforward to wire into Supabase or a Vercel function.

Postmark

Postmark's developer experience is mature but older in feel. The Mustachio templating system is powerful (server-side template management with version history) but feels clunky compared to React Email components in your repo. If you are building with Lovable, Replit, or Base44 and your email templates live as managed assets outside your codebase, Postmark's template management is fine. If you are a Claude Code or Cursor user who wants email templates colocated with your component code, Resend's approach is cleaner.

Message Streams are Postmark's standout feature. You create separate streams for transactional (password resets, receipts) and broadcast (newsletters, marketing). Each stream has its own IP pool and reputation, which means a poorly performing marketing campaign cannot damage your transactional deliverability. For a UK SaaS that eventually runs both product emails and a newsletter, this separation is architecturally valuable - and directly maps to PECR compliance (more on that below).

Inbound email parsing is Postmark-only in this comparison. If your UK SaaS needs to receive email - support ticketing, reply-to-thread, or email-to-action workflows - Postmark parses inbound mail to a JSON webhook. Resend has no inbound parsing.

Reputation engineering: how each provider manages senders

This difference matters more than most comparison posts acknowledge.

Postmark manually reviews accounts at sign-up. If your sending patterns suggest bulk or newsletter-first sending, they will decline or delay your account. This is intentional - their IP pool reputation depends on keeping bulk senders out. The consequence: strong IP reputation that benefits every sender on those pools. The trade-off: onboarding friction for early-stage products that cannot yet demonstrate clean patterns.

Resend has lighter onboarding - you can be sending within minutes. The flip side: the shared free-tier subdomain carries more mixed reputation than Postmark's pools. Once you are on your own domain (Hobby at GBP 16/mo), Resend's deliverability is strong - your domain's reputation is what matters, not the shared pool.

Resend's lighter onboarding is a practical advantage at MVP stage. Postmark's stricter gating is a feature once you have paying users whose emails actually matter.

Inbound email: Postmark only

If your UK SaaS needs to receive email as part of its product, this section ends the comparison.

Only Postmark handles inbound email parsing. Configure an inbound stream, point your MX records at Postmark's servers, and incoming emails arrive at your webhook as structured JSON - headers, body, attachments, sender, recipient. Common use cases: support ticketing via email replies, reply-to-thread, email-to-action workflows. If your product does not need inbound parsing, ignore this section. If it does, Postmark is the only answer in this comparison.

Compliance for UK SaaS

SPF, DKIM, DMARC setup

Both providers require the same baseline DNS configuration. Here is the correct setup for a UK SaaS.

SPF record (add to your domain's TXT records):

v=spf1 include:spf.resend.com ~all

or for Postmark:

v=spf1 include:spf.mtasv.net ~all

If you are using both simultaneously: v=spf1 include:spf.resend.com include:spf.mtasv.net ~all - watch your DNS lookup count (max 10 SPF lookups total across all includes).

DKIM - both providers give you a CNAME or TXT record to add to DNS. Always request or verify a 2048-bit DKIM key (not 1024-bit). Resend uses resend._domainkey.yourdomain.com; Postmark uses pm._domainkey.yourdomain.com. They can coexist.

DMARC - add this TXT record at _dmarc.yourdomain.com and start permissive:

v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com

Set p=none to start (monitoring only). After 2-4 weeks of clean sends, tighten to p=quarantine, then p=reject. Never jump straight to p=reject on day one - you will block legitimate sends.

PECR and transactional vs broadcast

PECR (Privacy and Electronic Communications Regulations) governs unsolicited electronic communications in the UK. The key rule for a UK indie SaaS:

• Transactional emails (password resets, purchase receipts, account notifications triggered by a user action) do not require prior consent under PECR. You can send them to any registered user.
• Marketing emails (newsletters, promotional sends, feature announcements sent to a list) require either prior consent (opt-in) or a valid "soft opt-in" (existing customer relationship, similar products/services, easy opt-out).

Postmark's Message Streams enforce this separation at the infrastructure level. Your transactional stream and your broadcast stream have separate IP pools, separate tracking, and separate reporting. This maps directly to the PECR distinction - it is not possible to accidentally route a marketing email through your transactional stream.

Resend requires you to manage this separation in your code. Resend Audiences is for broadcast/newsletter sends; resend.emails.send() calls should be transactional only. Nothing in the API prevents a marketing email going through the transactional route - you need process discipline or code review gates to enforce the split.

UK GDPR Article 28: Data Processing Agreements

Both are data processors under UK GDPR Article 28 - you need a signed DPA with each. Resend's DPA is in account settings. Postmark's is on their legal pages; UK customers need to supplement it with the IDTA for the US transfer leg. Document both in your ROPA. 20 minutes, not a legal project.

Decision matrix by use case

Use case	Winner	Reason
First MVP (no users yet)	Resend	3,000 free emails/mo, custom domain on Hobby at GBP 16/mo, no IDTA overhead
Consumer SaaS, low volume, marketing focus	Resend	Audiences built-in, React Email native, simple compliance posture
Critical password reset / payment receipt at scale	Postmark	M365 deliverability edge, IP pool reputation, strict stream separation
UK B2B SaaS (M365-heavy customers)	Postmark	Measurably better Microsoft 365 inbox placement
Inbound email feature (support, reply-to-thread)	Postmark	Only Postmark handles inbound parsing
Newsletter for first 1,000 UK subscribers	Resend	Audiences removes need for a separate tool; soft opt-in wiring is 2 minutes
Multi-region SaaS (UK + EU customers)	Resend	EU region as primary keeps data in adequacy zone; no IDTA needed
Strictest PECR/UK GDPR posture	Postmark	Message Streams enforce transactional/broadcast separation at infrastructure level

Migration path: Resend to Postmark in one weekend

You will do this. Here is how to do it without losing reputation.

Friday evening:

1. Apply for Postmark - manual review takes 1-2 days, so apply midweek before your migration weekend.
2. Create a Transactional stream and (if needed) a Broadcast stream.
3. Add Postmark's DKIM TXT record (pm._domainkey.yourdomain.com) alongside your Resend record. Both selectors coexist in DNS.
4. Verify your domain in the Postmark dashboard.
5. Add include:spf.mtasv.net to your SPF record. Count total DNS lookups - max 10.

Saturday: 6. Route one email type (password reset) through Postmark. Leave everything else on Resend. 7. Test on Gmail, Google Workspace, and M365 if you can get a test address. 8. Monitor Postmark's Activity dashboard for bounce and spam rates. 9. If you need inbound email, configure an inbound stream and update your domain's MX records.

Sunday: 10. Route remaining transactional emails to Postmark. Broadcast sends can move to Postmark's Broadcast stream or stay on Resend Audiences - no rule against running both. 11. Remove the Resend DKIM record only after 3-5 days of clean Postmark delivery. 12. Update your privacy policy to add Postmark as sub-processor with IDTA reference. 13. Update your ROPA.

Five UK failure modes to avoid

These are the patterns that catch UK indie hackers out. Avoid them.

1. DMARC stuck at p=none forever

p=none is monitoring only - it does not protect your domain from spoofing. Set a calendar reminder: p=quarantine after 4 weeks, p=reject after 8. Under ICO guidance, failing to protect your domain from spoofing is a foreseeable security risk you could have mitigated.

2. No UK SPF entry for Resend or Postmark IPs

The most common deliverability failure: a developer adds Resend or Postmark but forgets to update the SPF record. Email passes DKIM but fails SPF, DMARC marks it as fail, and UK ISPs quietly bin it. Always update SPF on day one.

3. Resend Audiences misused for transactional sends

Resend Audiences requires PECR-compliant consent - it is for marketing and newsletters. Sending a password reset via Audiences is a PECR misclassification. Keep Audiences for marketing; use resend.emails.send() for transactional.

4. No signed Article 28 DPA with your email provider

UK GDPR Article 28 requires a written contract with any data processor. Not having one is an ICO-actionable compliance gap. Both providers make this easy - execute it today, not after your first user complaint.

5. Hard bounces from UK consumer ISPs ignored in the dashboard

BT Internet and TalkTalk generate hard bounces for invalid or full mailboxes. Both Resend and Postmark suppress these addresses automatically. The failure mode is not acting on the data - a growing suppression list often signals a bad sign-up flow, fake addresses, or missing email verification. Check bounce rates weekly in the early months.

30-minute ship-it checklist

Resend setup checklist

1. Create account at resend.com
2. Add your domain and publish the DKIM CNAME (resend._domainkey.yourdomain.com)
3. Add include:spf.resend.com ~all to your SPF TXT record
4. Add DMARC: _dmarc.yourdomain.com TXT v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com
5. Verify domain in dashboard (green tick)
6. Select EU region in account settings if required
7. Generate API key with Send access only
8. npm install resend then import { Resend } from 'resend'
9. npm install @react-email/components
10. Send a test to Gmail and (ideally) an M365 address
11. Execute Resend's DPA in account settings
12. Update privacy policy: Resend as sub-processor, EU (Ireland) processing
13. Update ROPA

Postmark setup checklist

1. Apply for a Postmark account - expect 1-2 business days for manual review
2. Create a Transactional message stream
3. Add your sending domain: Domains > Add Domain
4. Publish Postmark's DKIM TXT record (pm._domainkey.yourdomain.com)
5. Add include:spf.mtasv.net to your SPF record (check total lookup count - max 10)
6. Verify SPF and DKIM in Postmark dashboard
7. Add DMARC TXT record if not already present
8. If you need inbound email: create an Inbound stream, add Postmark's MX records to your domain
9. Generate a Server API token from the server settings
10. npm install postmark and initialise the client with your token
11. Send a test email and confirm it appears in the Activity dashboard
12. Execute Postmark's DPA and add the IDTA addendum for UK-to-US transfers
13. Update privacy policy: add Postmark as sub-processor, state US (Virginia) processing, reference IDTA
14. Update ROPA
15. Set a calendar reminder to tighten DMARC to p=quarantine in 4 weeks

---

Ready to pick your UK SaaS stack? IdeaStack's free reports cover the full infrastructure picture for UK indie hackers building in 2026 - email, payments, hosting, compliance, and monetisation. No fluff, no US-centric assumptions.

Browse the free reports at ideastack.co/reports