The Email Localization Stack Explained: What Actually Sends Your Emails?

The Confusion

You need to send localized emails. A quick search turns up:

• Dyspatch - "Email template management platform"
• Lokalise - "Translation management system with email support"
• SendGrid - "Email delivery platform"
• Braze - "Customer engagement platform"

Do you need all of them? Just one? Which one actually sends the email?

This confusion costs companies thousands of dollars a year in redundant tooling. Let's clear it up.

The Email Localization Stack

Here's the reality: most of these tools don't send emails. The email localization stack has four distinct layers, and only one actually delivers messages to inboxes.

+-------------------------------------------------------------------+
|                    THE EMAIL STACK                                |
+-------------------------------------------------------------------+
|                                                                   |
|  Layer 4: SENDING (ESPs)                                          |
|  -- Actually delivers emails to inboxes                           |
|                                                                   |
|  Layer 3: ORCHESTRATION                                           |
|  -- Triggers emails based on events and user journeys             |
|                                                                   |
|  Layer 2: TEMPLATE MANAGEMENT                                     |
|  -- Visual builders, approval workflows, version control          |
|                                                                   |
|  Layer 1: TRANSLATION / i18n                                      |
|  -- Manages translations, locales, translation memory             |
|                                                                   |
+-------------------------------------------------------------------+

Let's break down each layer.

Layer 1: Email Sending (ESPs)

This is the ONLY layer that actually delivers emails.

What they do:

• SMTP/API email delivery
• IP reputation management
• Deliverability optimization
• Bounce/complaint handling
• Basic template storage

What they don't do well:

• Visual template editing (basic at best)
• Translation management
• Multi-language support
• Approval workflows

Example: AWS SES

AWS SES is the extreme case. It's purely a sending engine:

"SES is a sending (and receiving) engine only. You'll need to create your transactional emails elsewhere. No visual builder or UI tools. Everything is code-based."

This is why most teams need additional layers.

Layer 2: Template Management

These tools help you design and manage email templates, then export to ESPs.

What they do:

• Drag-and-drop email builders
• Brand consistency enforcement
• Approval workflows
• Version control
• Export to ESPs (SendGrid, Mailchimp, etc.)

What they don't do:

• Actually send emails
• Full translation management
• Translation memory/glossaries

How Dyspatch Works

From Dyspatch's own documentation:

"Dyspatch's built-in integrations include support for SendGrid. With this real-time integration, importing published Dyspatch email templates to SendGrid is just a couple of clicks away."

The workflow:

1. Design email in Dyspatch visual builder
2. Localize to 300+ locales
3. Approve via workflow
4. Click "Export to SendGrid"
5. SendGrid actually sends the email

Dyspatch explicitly states: they manage templates, ESPs send them.

Layer 3: Translation / i18n

These tools manage the content in multiple languages.

What they do:

• Translation management
• Translation memory
• Glossaries
• AI/MT translation
• API for content delivery

What they don't do:

• Actually send emails
• (Most) Visual email editing

The Translation Layer Problem

Most TMS platforms treat email as an afterthought:

• Lokalise: Email support via Mailchimp/Braze integrations
• Crowdin: Exports PO files, you import elsewhere
• Phrase: Requires separate Dyspatch integration

This creates a fragmented workflow:

1. Design in Dyspatch
2. Export to Lokalise
3. Translate
4. Export back to Dyspatch
5. Export to SendGrid
6. Send

That's 6 steps and 3 tools for one localized email.

Layer 4: Orchestration

These tools decide when to send emails based on user behavior.

What they do:

• Event-triggered messaging
• User journey automation
• Multi-channel (email + push + SMS)
• Segmentation and personalization

What they don't do:

• Actually send emails (use ESPs)
• Deep translation management

Braze's Localization Approach

Braze offers multi-language support, but it's limited:

"Multi-language support and locales in messages are currently in early access. You can add up to 200 locales."

For full translation management, Braze recommends integrating with Crowdin or Transifex.

The Cost Problem

Here's what a typical enterprise email localization stack costs:

And this doesn't include:

• Integration maintenance
• Manual export/import workflows
• Version control headaches
• Training across 4 platforms

A Simpler Approach

What if you could combine template management and translation in one platform?

IntlPull's Email Templates

IntlPull combines Layers 2 + 3:

Template Management:

• Visual WYSIWYG editor
• Block-based templates
• Version history
• Publish workflows

Translation:

• All translations in one place
• Translation memory
• AI translation (GPT-4, Claude)
• Glossary enforcement

API Rendering:

• Render localized HTML via API
• Variable interpolation
• Send via ANY ESP

Code Example

TypeScriptCopy
1// 1. Render localized email (IntlPull API)
2const response = await fetch(
3  'https://api.intlpull.com/v1/projects/{id}/emails/render',
4  {
5    method: 'POST',
6    headers: {
7      'X-API-Key': 'ip_live_xxxxx',
8      'Content-Type': 'application/json',
9    },
10    body: JSON.stringify({
11      slug: 'welcome-email',
12      language: 'es',
13      variables: {
14        name: 'Maria',
15        company: 'Acme Inc'
16      }
17    })
18  }
19);
20
21const { html, subject, preview_text } = await response.json();
22
23// 2. Send via your ESP (Resend, SendGrid, Postmark, etc.)
24await resend.emails.send({
25  from: 'hello@yourapp.com',
26  to: 'maria@example.com',
27  subject,
28  html
29});

Cost Comparison

When You Need Each Layer

Not every team needs every layer. Here's a decision guide:

Startup / Side Project

Stack: IntlPull Free + Resend Free

• Cost: $0/mo
• Handles: Up to 3,000 emails/mo + 500 strings

Growing Startup

Stack: IntlPull Growth + SendGrid Essentials

• Cost: ~$100/mo
• Handles: 50K emails/mo + 15K strings + branches

Scale-up

Stack: IntlPull Business + SendGrid Pro

• Cost: ~$290/mo
• Handles: 100K emails/mo + 50K strings + OTA

Enterprise

Stack: IntlPull Pro + SendGrid Enterprise + (optional) dedicated orchestration

• Cost: ~$450+/mo
• Handles: SSO, audit logs, SLA, unlimited scale

Feature Comparison

The Key Takeaway

Most email template and translation tools don't send emails. They manage content and export to ESPs.

Understanding this distinction helps you:

1. Stop paying for redundant tools: You don't need 4 platforms
2. Simplify your workflow: Fewer integrations = fewer bugs
3. Choose the right architecture: ESP for sending, one tool for content

Getting Started

If you're setting up email localization from scratch:

1. Pick an ESP: Resend or SendGrid are great defaults
2. Use one platform for templates + translations: IntlPull handles both
3. Add orchestration later: Only if you need complex journeys

TerminalCopy
1# Quick start with IntlPull
2npx @intlpullhq/cli init
3npx @intlpullhq/cli emails create welcome-email
4npx @intlpullhq/cli emails translate --language es

Conclusion

The email localization market is confusing because vendors don't clearly explain what they do vs. what they integrate with.

Here's the simple truth:

• SendGrid/Resend/Postmark = Actually sends emails
• Dyspatch/Stripo = Visual template management
• Lokalise/Crowdin/Phrase = Translation management
• IntlPull = Templates + translations in one platform

Most teams are overpaying for 3-4 separate tools when one unified platform can handle templates and translations, leaving you to pick your preferred ESP for delivery.

Ready to simplify your email localization? Try IntlPull free and see how one platform can replace your fragmented stack.