Mailjet vs Dedicated IP Infrastructure

When the Paris-headquartered hybrid marketing and transactional email platform — founded in 2010 by three French co-founders, acquired by Swedish CPaaS Sinch in December 2021 as part of the $1.9 billion Pathwire deal that also brought Mailgun under the same corporate parent, 100,000 customers across 150 countries, real-time collaborative template editing as the differentiating feature — runs into the dedicated-IP gating, automation-depth ceiling, and per-message visibility limits that come with mid-tier shared-pool ESPs operating under publicly-listed parent company quarterly reporting pressure

Mailjet is the email platform founded in 2010 in Paris, France, by Julien Romanetto, Wilfried Durand, and Alexis Renard. The original product positioning was distinctive: rather than competing on raw deliverability or aggressive marketing automation depth, Mailjet focused on real-time collaborative template editing — a Google Docs-style multi-user editor for email design that allowed marketing teams, designers, and copywriters to work simultaneously on the same campaign. The collaboration feature remains the platform's most genuinely differentiated capability sixteen years later.

The platform's second distinctive contribution to the email category is the MJML markup language — an open-source responsive email framework that Mailjet developed and released to the broader email community. MJML compiles into responsive HTML email that renders consistently across mobile and desktop clients, eliminating much of the historical pain of email design. The framework has been adopted broadly across the email industry and remains a meaningful technical contribution beyond Mailjet's own product.

A defining strategic event for procurement teams is the December 2021 acquisition by Sinch (Stockholm-listed Swedish CPaaS, ticker STO: SINCH) through the $1.9 billion Pathwire deal. Pathwire was the holding company under which Mailjet, Mailgun, and Email on Acid had been consolidated; Sinch's acquisition of the entire Pathwire portfolio brought all three under common corporate ownership. The strategic rationale was Sinch's expansion from SMS and voice CPaaS into email, with Mailjet positioned as the marketing-friendly product alongside Mailgun's developer-focused transactional positioning. The combined Mailjet + Mailgun infrastructure now processes over 300 billion emails per year (Black Friday 2025 alone delivered 20.4 billion emails across the combined portfolio, +32% year-over-year).

The product positioning today targets EU-based marketing and developer teams needing both transactional and marketing email through a single platform. Mailjet's specific market position is the middle ground — more developer-capable than Mailchimp, more marketing-friendly than Mailgun, with native EU jurisdiction (Paris-incorporated under Sinch's Stockholm parent — both EU/EEA member countries). Customer concentration is in EU SMB and mid-market with substantial French and continental European representation.

This page approaches the question from the EU SMB and mid-market lens. When the variables that matter become email volume at scale, automation depth beyond basic workflows, dedicated IP control without forced Premium 100K tier upgrade, AI content generation gap, or per-message forensic logging, at what point does dedicated PowerMTA infrastructure become the better operational answer? The crossover happens at three distinct points: when the Sinch-portfolio cannibalization between Mailjet and Mailgun creates strategic uncertainty, when the automation depth limitation becomes operationally meaningful, and when peak-period deliverability needs dedicated IP control without the $95/month Premium 100K tier minimum.

Pricing 2026: tiered transactional + marketing with dedicated-IP gating at $95/month

Mailjet operates an email-volume-based pricing structure (rather than the contact-based pricing common across SMB ESPs), which produces a meaningfully different economic profile for senders with large lists but moderate send volume. All paid plans include unlimited contacts (a procurement advantage for senders with large dormant lists) and combine marketing and transactional email through a unified subscription.

The full economic picture for a Mailjet deployment includes line items beyond the headline pricing:

• The Essential-Premium gating: the $17/mo Essential plan deliberately excludes automation and A/B testing — capabilities that competitor entry plans (Brevo, MailerLite) include at lower price points. The forced upgrade to Premium ($27/mo) for any meaningful marketing operation effectively makes Premium the realistic entry tier rather than Essential.
• Annual billing discount: 10% off the monthly rate on 12-month prepayment.
• Dedicated IP only at Premium 100K and above: customers requiring dedicated IP for deliverability isolation must commit to the $95/month Premium 100K plan with 100,000 monthly email allocation. Lower volumes cannot access dedicated IP — a meaningful constraint for SMB senders requiring deliverability isolation but not the 100K monthly volume.
• Mandatory 2-6 week IP warm-up: dedicated IPs require structured warm-up before reaching steady-state deliverability. Mailjet's documentation acknowledges the warm-up requirement explicitly — a procurement detail to budget into deployment timelines.
• Subaccount complexity: subaccounts useful for agencies but add overhead for single companies. Pricing for subaccount management is bundled into Premium and above tiers.
• Slow onboarding verification: customer reviews on Trustpilot consistently mention onboarding verification taking weeks rather than days, particularly for higher-volume new accounts. Procurement teams should plan onboarding timelines accordingly.
• SMS via SimpleTexting: Mailjet itself does not offer SMS marketing; Sinch parent company offers SimpleTexting separately. Customers wanting SMS-and-email under unified billing must engage Sinch SMS products directly.
• NO AI content generation in 2026: notable gap versus MailerLite (AI Assistant Advanced+), Brevo, and broader category. Mailjet's roadmap has not announced AI content capabilities at the time of this writing.

The Sinch acquisition and the Mailjet–Mailgun cannibalization question

The December 2021 Sinch acquisition of the Pathwire portfolio for $1.9 billion brought Mailjet, Mailgun, and Email on Acid under common corporate ownership for the first time. The strategic rationale was Sinch's expansion from SMS and voice CPaaS into email, and the Pathwire portfolio's existing relationships with major brands (DHL, Lyft, Microsoft, Wikipedia, Iterable) were operationally valuable.

For procurement teams in 2026, the Sinch ownership creates a specific strategic dynamic worth understanding. Mailjet and Mailgun are positioned as complementary rather than competitive:

• Mailjet: marketing-friendly positioning with collaborative template editing, drag-and-drop campaign builder, MJML editor, segmentation, A/B testing. Targeted at marketing teams.
• Mailgun: developer-focused transactional positioning with raw API performance, webhook depth, email validation as built-in feature, inbound email parsing. Targeted at developers.
• Email on Acid: email-rendering-test platform for QA before send. Complementary to both.

The complementary positioning is genuine in product strategy but creates two procurement concerns. First, the strategic uncertainty: under Sinch's publicly-listed quarterly reporting pressure, the company could rationalize the portfolio at any point, consolidating brands or migrating customers between platforms. Second, customers who chose Mailjet specifically for its marketing-friendly positioning sometimes find Mailgun's transactional capabilities preferable for specific use cases — but switching between Mailjet and Mailgun means staying within the Sinch ecosystem, not reducing dependency on a single corporate parent. Customers seeking true platform diversity must look outside the Sinch portfolio entirely.

A late-2025 strategic signal is worth noting: Mailgun's Foundation plan price doubled in late 2025 (from prior Flex tier rates), suggesting Sinch is exercising pricing power across the portfolio. Mailjet has not announced equivalent dramatic increases at the time of this writing, but historical patterns across portfolio-managed SaaS platforms suggest pricing alignment between sister products is a recurring outcome under publicly-listed parent quarterly reporting pressure.

The collaborative template editing differentiator

Mailjet's most genuinely differentiated capability is the real-time collaborative template editing — a Google Docs-style multi-user editor that allows multiple team members to work simultaneously on the same email campaign. Marketers, designers, copywriters, and approval stakeholders can all be in the editor at once, with cursor positions visible across collaborators, comment threads tied to specific elements, and change history preserved. The capability is meaningfully unique in the email category — competitors like Mailchimp, ActiveCampaign, and Brevo offer single-user editors with sequential review workflows rather than true real-time multi-user collaboration.

The capability is paired with Mailjet's Brand Kit feature, which generates a brand visual identity (colours, fonts, logo placements) from a website URL automatically — accelerating template setup for new accounts and ensuring design consistency across sends. Combined with the MJML editor's responsive output and the ~65-70 template library, the design system produces functional creative consistency for SMB and mid-market marketing teams.

For procurement teams whose marketing operations involve multiple stakeholders working concurrently on campaigns — agencies serving multiple clients, in-house teams with distributed designers and copywriters, marketing operations functions managing approvals across stakeholders — the collaboration capability produces operational value that competitors do not match. The value is most pronounced for organisations that previously managed campaign creation through email back-and-forth, design tool exports, and manual reconciliation between contributors.

The trade-off: customers attracted to Mailjet specifically for the collaboration feature sometimes find the platform's other capabilities (automation depth, AI content, advanced segmentation) inadequate for their broader marketing operations needs. The collaboration differentiator is real but narrow.

EU jurisdiction: Paris incorporation under Stockholm parent

Mailjet is incorporated in France (Paris-headquartered, EU member state) under the corporate parentage of Sinch (Stockholm-listed Swedish company, EU/EEA jurisdiction). The dual EU/EEA corporate structure produces native EU GDPR applicability without the documented-mitigation framework that US-incorporated competitors require. For European customers operating under Schrems II compliance scrutiny, the jurisdictional positioning represents one of the more favourable arrangements in the email category.

The EU jurisdictional position pairs Mailjet with a small group of email platforms operating under native EU corporate structures: Brevo (Paris-incorporated, French independent), Emarsys (post-2020 SAP German parentage), GetResponse (Gdańsk-incorporated, Polish), and MailerLite (Vilnius Lithuanian + Polish Vercom parent). The Mailjet specific positioning within this group is the marketing-and-transactional unified offering plus the collaboration differentiator — neither Brevo nor GetResponse offers equivalent collaborative template editing.

Sinch itself is publicly listed on the Stockholm Stock Exchange (STO: SINCH), subject to EU market disclosure standards and Swedish FSA oversight. The public-company governance produces transparency that privately-held US SMB SaaS competitors do not match. Procurement teams whose vendor onboarding process requires corporate governance verification find the publicly-listed parent simpler to evaluate.

For French and continental European customers specifically, Mailjet's customer support team operates with multilingual capability across French, English, and several other European languages — a meaningful operational detail for procurement teams whose support requirements include native-language coverage during European business hours.

Technical architecture: API v3.1, mandatory DKIM, SPF alignment quirk

Mailjet's technical implementation reflects sixteen years of operational maturity but carries some specific quirks that procurement teams should understand. The v3.1 Send API is the recommended endpoint for new integrations, with the prior v3 API maintained for legacy compatibility. The v3.1 API limits batch sends to 50 messages per call — meaningful for high-volume transactional flows that need to architect around the per-call limit.

DKIM signing is mandatory on Mailjet, with specific technical requirements:

• Mailjet selector required in DNS records.
• 2048-bit RSA keys default since April 2024 (upgraded from prior 1024-bit standard).
• 4096-bit RSA keys available for customers requiring stronger key strength — operationally meaningful for regulated industries.
• Automatic key rotation supported via DNS-published selector updates.

A specific technical quirk worth flagging: SPF alignment fails by default on Mailjet because the Return-Path is set to a Mailjet-controlled domain rather than the customer's sender domain. For DMARC enforcement, customers must rely on DKIM alignment alone — a workable but non-standard configuration that some compliance frameworks flag during vendor security review. Customers requiring strict SPF + DKIM dual alignment for DMARC enforcement (financial services, healthcare, regulated industries) need to engage Mailjet's enterprise team for custom Return-Path configuration.

A second technical limitation: Mailjet does not support the send_at parameter for transactional emails. Scheduled transactional sends require either client-side scheduling logic or middleware that buffers messages until the desired send time — operationally meaningful for transactional workflows that need precise delivery timing (financial settlement notifications, time-sensitive alerts).

Webhook coverage is competent: delivery, open, click, bounce, spam, blocked, and unsubscribe events are all available. The webhook delivery is reasonably reliable per customer reviews, though not as battle-tested as SendGrid or Postmark for high-volume transactional reliability.

Per-message visibility: Mailjet reports vs PowerMTA acct.csv

Mailjet's reporting suite covers the standard email category metrics: campaign performance dashboards (open, click, bounce, unsubscribe), per-recipient delivery status, A/B test variant analysis, segmentation engagement breakdowns, and the unified marketing-plus-transactional reporting that the platform's positioning emphasises. The reporting is operationally appropriate for SMB and mid-market marketing operations.

For a deliverability practitioner trying to determine why a particular recipient at a major enterprise domain experiences elevated SMTP-accept times while peers at the same domain accept under two seconds, the platform-level reporting layer aggregates too much to support the diagnostic work. The underlying SMTP transaction — verbatim dsnDiag from the receiving MX, source IP for the specific delivery attempt, TLS capabilities negotiated, throttling state at submission time — is not surfaced in Mailjet's reporting layer because the granular transaction data is not retained at that level.

PowerMTA's acct.csv records this per message:

d,2026-04-27 16:14:52+0000,2026-04-27 16:14:49+0000,
order-confirmation@send.example.eu,
m***@orange.fr,,relayed,
2.0.0,smtp;250 2.0.0 OK 1714234492 d29-20020a05600c4d9b00b00415f3e5d2f1si,
mx-orange.fr (52.218.96.4),delivery,smtp,
mta-eu-fr1 (192.168.7.10),smtp,185.224.4.51,185.224.4.51,
"ENHANCEDSTATUSCODES,8BITMIME,STARTTLS,SMTPUTF8",,
vmta-eu-fr1,job-q2-2026-04,env-ecommerce-transactional,
orange.fr.rollup/vmta-eu-fr1

Pivoted into a query layer, this data answers questions like "show me all order-confirmation deliveries to French ISP domains over the past 60 days where time-to-accept exceeded 5 seconds, grouped by hour-of-day and recipient ESP" with a single SQL query. Mailjet's reporting layer cannot answer this question because the granular transaction data does not exist in its tracking model — operationally meaningful for ecommerce and SaaS customers where transactional message delivery directly drives revenue events and per-recipient incident investigation matters.

When Mailjet is the right answer

Mailjet is the right choice when:

• Real-time collaborative template editing is operationally important — multi-stakeholder campaign creation, agency-client collaboration, distributed marketing teams working concurrently on campaigns.
• You need marketing and transactional email through a unified API rather than managing separate platforms with separate sender reputations and separate billing.
• You operate as an EU-headquartered business where the French + Swedish (Sinch) EU/EEA jurisdictional positioning matches your compliance posture.
• The MJML responsive email framework aligns with your engineering practices and the open-source heritage matters operationally.
• Email volume sits in the 5K-100K monthly range where the volume-based pricing is competitive and the unlimited-contacts inclusion produces value for senders with large dormant lists.
• You are willing to accept the Essential-Premium gating ($17 to $27 forced upgrade for automation and A/B testing) and Premium 100K dedicated-IP gating ($95/month minimum).
• The publicly-listed Sinch parent corporate transparency is acceptable from a vendor governance perspective.
• Multilingual customer support across European languages matches your operational requirements.
• You don't currently need AI content generation — Mailjet's roadmap has not delivered AI capabilities at parity with MailerLite or competitors at the time of this writing.

When dedicated infrastructure wins

The crossover happens when:

• Email volume passes 500,000 messages per month. At Premium 100K and above tiers, the cost-per-message economics start favouring dedicated infrastructure with full deliverability isolation.
• Dedicated IP is operationally required below the 100K monthly volume threshold. SMB senders below 100K messages cannot access dedicated IP within Mailjet — dedicated infrastructure provides dedicated IP at any volume.
• Automation depth becomes operationally meaningful. The workflow builder handles standard drip sequences but lacks behavioral triggers, complex multi-path journeys, and predictive segmentation that ActiveCampaign or Brevo offer at competitive pricing.
• AI content generation enters the operational requirement. Mailjet's lack of AI content capabilities in 2026 is increasingly noticeable as competitors (MailerLite, Brevo, Iterable, Klaviyo) deliver AI features.
• Sinch portfolio cannibalization concerns raise long-term platform commitment questions. Customers seeking true platform diversity must look outside the Sinch ecosystem entirely.
• The SPF alignment quirk creates compliance friction. Regulated industries requiring strict SPF + DKIM dual alignment for DMARC enforcement face procurement-review friction that EU-incorporated alternatives like Brevo address natively.
• The send_at limitation impacts transactional workflows. Time-precise transactional delivery (financial settlements, regulatory notifications) requires either Mailjet middleware or alternative transactional providers.
• Per-message audit logging is required for compliance audits or deliverability investigations that aggregate Mailjet dashboards cannot support.
• Onboarding-verification timelines documented in Trustpilot reviews (often weeks) create deployment-timeline friction that dedicated infrastructure avoids.

The Mailjet API and integration architecture

Mailjet provides a broad REST API (v3 legacy and v3.1 recommended) plus SMTP relay covering subscribers, lists, segments, campaigns, automations, transactional messages, and reporting endpoints. The API documentation is mature and the API surface area reflects the platform's hybrid marketing-and-transactional positioning. Native SDK availability covers Node.js, PHP, Python, Ruby, .NET, Java, and Go through Mailjet-maintained libraries — better SDK coverage than typical SMB ESPs and reflecting the platform's developer-aware positioning.

Native integrations cover Zapier (extending to thousands of apps), Salesforce CRM, HubSpot CRM, Shopify, WooCommerce, WordPress, and the major ecommerce platforms. The integration depth is appropriate for the SMB and mid-market positioning but materially smaller than HubSpot's 1,000+ ecosystem or Mailchimp's 300+ catalogue.

For hybrid stack patterns where Mailjet handles marketing-and-transactional unified email at SMB volumes and dedicated infrastructure handles high-volume marketing at scale, the architecture is workable through Mailjet's email-routing options. The middleware pattern routes specific Mailjet campaign workflows through PowerMTA via SMTP relay; engagement events flow back through Mailjet's webhook coverage for closed-loop reporting. Engineering effort runs 4-6 weeks for a properly-scoped hybrid build.

For full migrations away from Mailjet, the export workflow is straightforward through subscriber, segment, campaign, and webhook endpoints. Sixteen years of operational maturity have delivered robust data-export tooling. Total export effort runs 3-4 engineering weeks for SMB and mid-market accounts; accounts heavily using the collaborative template library and MJML-based responsive design system face additional reconstruction effort because MJML compilation requires reproduction in destination platforms (most modern ESPs support MJML import; some require manual HTML conversion).

Side-by-side: Mailjet Premium 100K vs CSE Bulk Professional

For an EU SMB or mid-market sender requiring dedicated IP and processing approximately 100,000 messages per month — a typical Mailjet Premium 100K customer:

The pattern: at 100K monthly email volume, Mailjet Premium 100K is dramatically cheaper than CSE Bulk Professional — €88 versus €990 represents approximately 11× the monthly cost. The platform constraints are similarly clear: Mailjet delivers real-time template collaboration, marketing-plus-transactional unified API, and competitive volume-based pricing that CSE does not; CSE delivers per-message forensic visibility, send capacity headroom for growth past 1 million messages monthly, strict SPF + DKIM alignment for DMARC enforcement, multiple dedicated IPs without volume gating, and freedom from the Sinch portfolio cannibalization risk. For SMB and mid-market EU senders within the Mailjet target profile and where the collaboration differentiator is operationally critical, the platform remains operationally appropriate; for accounts where revenue-critical email at scale or strict DMARC alignment enters the procurement equation, the conversation shifts.

Migration timeline: Mailjet to dedicated infrastructure

A migration from Mailjet to dedicated infrastructure runs 12-16 weeks end-to-end:

• Weeks 1-2 — Audit and architecture. Inventory of subscribers, lists, segments, automation workflows (typically 10-25 active automations on mid-market accounts), MJML templates (which often require careful preservation given the responsive design investment), transactional message types, sending domains, and the collaboration-driven approval workflows that may need internal capability replacement.
• Weeks 3-4 — DNS and authentication configuration. SPF, DKIM (2048-bit minimum to match Mailjet's standard), DMARC alignment on new sending domains; VMTA pool design; subscriber and engagement event export from Mailjet via REST API v3.1.
• Weeks 5-12 — Staged IP reputation cultivation. Eight weeks of incremental IP-warming on two dedicated EU IPs — IP A handling transactional volume, IP B carrying marketing campaigns. Per-VMTA throttling profiles tuned to the leading global receivers (Google, Microsoft, Yahoo, Apple) and the major European regional ISPs.
• Weeks 13-15 — Automation reconstruction and platform replacement. Mailjet automations reimplemented in destination orchestration (Mautic for behavioural automation, MailWizz for broadcast); MJML templates ported (most modern ESPs support MJML import; manual HTML conversion may be required for specific destinations); collaboration workflow replaced by approval workflows in destination platforms or external collaboration tools.
• Weeks 15-16 — Cutover. Mailjet subscription cancelled at billing cycle end; sending fully on dedicated infrastructure; multi-platform stack running on the new architecture.

For accounts using Mailjet primarily for transactional API integration with minimal marketing campaign complexity, the timeline can compress to 8-10 weeks. For accounts heavily using collaborative template editing with multi-stakeholder approval workflows, the timeline extends to 18-22 weeks because the operational replacement of the collaboration capability requires careful change-management with marketing teams.

Production case study: a French ecommerce brand on Mailjet Premium 100K

An anonymised but representative migration profile.

Starting point. A French ecommerce brand operating from Lyon, ~28 employees, selling artisanal home goods to French and broader European markets. On Mailjet for seven years (originally drawn to the platform partly by the French local origin and partly by the collaborative template editing for the in-house design + marketing team). 145,000 active subscribers across the customer database; sending approximately 1.8 million messages per month — order-confirmation transactional, shipping-notification transactional, abandoned-cart recovery, post-purchase nurture sequences, weekly newsletter campaigns, seasonal promotional campaigns (Black Friday, Christmas, Mother's Day), and customer re-engagement. On Mailjet Premium 100K with custom volume add-ons negotiated through Sinch enterprise sales: ~€640/month effective.

Trigger. Three converging factors. First, the Mailgun late-2025 price doubling raised concerns about parallel pricing pressure on Mailjet — the Sinch portfolio's quarterly reporting pressure made future Mailjet price increases probable. Second, Black Friday 2025 produced documented Outlook deliverability degradation during peak send periods (placement dropping from 89% to 71% during the 4-day Black Friday-to-Cyber-Monday window) — the SPF alignment quirk meant DMARC enforcement relied on DKIM alone, and Microsoft's stricter DMARC enforcement during peak commerce concentration produced filtering. Third, expansion into the German market introduced data residency considerations where the existing French/Swedish jurisdictional position was acceptable but the German enterprise B2B contracts in the customer base began requesting documented dedicated infrastructure for their compliance frameworks.

Migration approach. Hybrid stack — keep Mailjet Premium for the collaborative template editing, MJML-based responsive design system, and weekly marketing campaign workflows where the integrated capability was operationally invaluable for the design + marketing team's productivity; offload high-volume Black Friday + seasonal promotional campaigns, transactional order/shipping flows, and German B2B enterprise communications to a self-hosted MailWizz instance running on CSE Bulk Professional infrastructure with two dedicated EU IPs (Frankfurt and Paris for proximity to French and German subscriber bases).

Implementation. 14-week structured migration completed during the post-holiday low-volume period. Phase 1: subscriber and event export from Mailjet via REST API v3.1 (paginated, ~2,200 lines of Python migration script preserving 7 years of customer metadata, purchase history tags, French/German language preferences, and engagement scoring). Phase 2: SPF/DKIM/DMARC publication with strict dual alignment (closing the SPF alignment gap from Mailjet) on three sending sub-domains (transactional, newsletter, promotional). Phase 3: 8-week phased IP-reputation warm-up on two dedicated EU IPs. Phase 4: MailWizz instance configured with MJML templates ported from Mailjet (MJML import preserved 95% of design without rework); webhook integration with the ecommerce platform's order events so transactional triggers flow into both platforms in real-time during transition; reduced Mailjet contract negotiated for the preserved newsletter editorial + collaborative template workflows. Phase 5: parallel operation during the calm February-March period before the spring promotional cycle.

Results at month 9 post-migration:

• Inbox placement (high-volume promotional campaigns): 88.4% on Mailjet shared/dedicated mix → 95.7% on CSE dedicated EU IPs (200-seed inbox panel testing across Mailtrap and Glock Apps)
• Black Friday 2026 Outlook placement: 71% (degraded 2025 baseline) → 95.1% (largest delta — strict SPF + DKIM dual alignment closed the DMARC enforcement gap that Mailjet's default Return-Path configuration had created)
• Effective monthly cost: €640 (Mailjet Premium full at 1.8M volume) → €1,170 (€990 CSE + €180 Mailjet reduced-tier for newsletter editorial only) — net cost increase of €530/month
• Black Friday 2026 revenue impact: 31% higher conversion on the high-volume promotional campaigns moved to dedicated infrastructure compared with the deliverability-degraded 2025 cycle, attributed primarily to Outlook/Hotmail placement recovery during peak commerce — net new Black Friday revenue of approximately €112K, paying back the cost increase within 2 months
• Compliance posture: EU data residency satisfied for both physical and jurisdictional levels — Frankfurt + Paris infrastructure within EU member states; strict SPF + DKIM alignment now satisfies German enterprise customer DMARC requirements that the prior Mailjet configuration could not
• Forensic visibility: from "Mailjet aggregate dashboards + webhooks" to "full PowerMTA acct.csv stream with 90-day retention queryable via SQL" — enabling per-recipient deliverability investigations during peak commerce events when individual customer order-confirmation reliability directly drives revenue
• Collaborative template editing preserved: the design + marketing team's MJML-based responsive design system and real-time collaborative template editing continued running through Mailjet where the integrated capability is unmatched in the dedicated-infrastructure ecosystem
• Sinch portfolio risk distributed: the post-Mailgun-doubling pricing concerns now apply to a smaller portion of the brand's operational stack rather than the entire email layer
• German B2B enterprise expansion enabled: the dedicated infrastructure satisfied German corporate buyer compliance review on dual SPF + DKIM alignment, unblocking three German enterprise B2B contracts that had been blocked by Mailjet's SPF alignment configuration

The strategic outcome: the migration was driven by Black Friday 2025 deliverability impact on revenue, the Sinch portfolio pricing pressure signalled by Mailgun's late-2025 doubling, and German B2B enterprise compliance requirements that Mailjet's SPF alignment configuration could not satisfy. The hybrid approach preserved the collaborative template editing capability that produced ongoing operational value while moving the high-volume revenue-critical email to dedicated infrastructure with the deliverability consistency, strict DMARC alignment, EU jurisdictional independence at scale, and pricing transparency that the platform-bundled email could not provide for the volume-driven seasonal commerce workloads.

The Mailjet strategic position in 2026

Mailjet's 2026 strategic position is clear and increasingly defined by the Sinch corporate context. As a sixteen-year-old French-founded platform now operating under Sinch's Stockholm-listed publicly-listed parent in shared portfolio with Mailgun and Email on Acid, the platform serves a defensible niche: EU-based marketing teams needing real-time collaborative template editing, marketing-and-transactional unified API, and competitive volume-based pricing. The 100,000+ customer base across 150 countries reflects genuine product-market fit, and the MJML open-source heritage produces credible developer engagement.

The structural constraints are equally clear. Automation depth lags ActiveCampaign and Brevo. The template library (~65-70 designs) is thin compared to Mailchimp. There is no native landing page builder. AI content generation is absent in 2026. The Essential-Premium gating forces upgrades for any meaningful marketing capability. The Premium 100K dedicated-IP gating excludes SMB senders below the 100K threshold. The SPF alignment quirk creates DMARC compliance friction. The Mailgun late-2025 price doubling raises questions about parallel Mailjet pricing trajectory. The Sinch portfolio cannibalization with Mailgun creates strategic positioning ambiguity that some procurement teams find concerning.

For procurement teams evaluating Mailjet in 2026, the question is whether the real-time collaborative template editing differentiator, the MJML responsive email framework, the marketing-and-transactional unified API, the EU jurisdictional positioning, and the publicly-listed Sinch parent corporate transparency justify the platform's specific procurement structure and post-Pathwire strategic context. For EU-based marketing teams within the platform's target profile and where the collaboration capability is operationally critical, the answer often remains positive. For accounts where automation depth, AI content generation, dedicated IP below 100K, strict DMARC alignment, or send capacity past 1 million messages monthly enter the equation, the cost-to-capability inversion increasingly favours hybrid architectures or alternatives.

The bottom line

Mailjet is a defensible choice for EU-based marketing teams where real-time collaborative template editing produces measurable operational value, marketing and transactional email through a unified API matches the operational requirement, the MJML responsive email framework aligns with engineering practices, and the French + Swedish (Sinch) EU/EEA jurisdictional positioning matches the buyer's compliance posture. The Paris founding heritage as Julien Romanetto, Wilfried Durand, and Alexis Renard's collaboration-first email platform combined with the MJML open-source contribution has produced a platform genuinely differentiated by team-collaboration workflows rather than retrofitted from generic email tooling.

For senders whose primary need is reliable high-volume email at scale — particularly when peak commerce period deliverability, strict SPF + DKIM dual alignment for DMARC enforcement, dedicated IP control without 100K monthly volume gating, multi-million message send capacity, AI content generation, post-Pathwire strategic certainty, or per-message forensic logging enter the equation — the cost-to-capability ratio inverts. The right answer is rarely "abandon Mailjet entirely" if the collaborative template editing has real operational value. It is "use Mailjet where its team-collaboration strengths fit and offload high-volume marketing email to dedicated infrastructure with the cost predictability, dedicated IP control, deliverability consistency, strict DMARC alignment, and per-message forensic logging that platform-bundled email under Sinch portfolio management cannot match."

Infrastructure expertise is not a workaround for poor practice — it is an amplifier of good practice. Mailjet has built a French-founded hybrid email platform with real-time collaborative template editing and MJML open-source contribution as defining strengths under post-Pathwire Sinch parentage; dedicated infrastructure provides the email layer at a deliverability consistency, dedicated IP availability, strict DMARC alignment, and visibility level that platform-bundled email under shared-pool architecture cannot match. The choice between them depends on whether the email programme treats team-collaboration workflow value as the dominant priority or as a capability that can be preserved through hybrid architecture while volume-driven revenue-critical email moves to dedicated infrastructure.