Contents
MailWizz and SendGrid are often compared as competitors but they belong to fundamentally different product categories that complement rather than compete. MailWizz is a self-hosted PHP email marketing platform handling campaign management, subscriber lists, automation, segmentation, and analytics; it delegates actual email delivery to external SMTP services. SendGrid is a managed SMTP and API delivery service handling email infrastructure, IP pools, deliverability tooling, and ISP relationships; it provides both transactional email (its core product) and Marketing Campaigns feature for marketing automation. The 2026 comparison typically reduces to three deployment configurations: MailWizz alone with self-hosted SMTP, SendGrid alone (with or without Marketing Campaigns), or MailWizz with SendGrid as the SMTP backend in BYOSP pattern.
This comparison covers the practical decision between MailWizz and SendGrid in 2026: the categorical difference between marketing platform and SMTP service, MailWizz's role as marketing platform delegating delivery, SendGrid's role as SMTP service plus optional Marketing Campaigns, the three common deployment configurations (MailWizz alone, SendGrid alone, MailWizz with SendGrid), MailWizz and SendGrid integration setup specifics, cost economics across the configurations at typical volume tiers, feature comparison covering what each platform provides natively, deliverability implications of each configuration, and the decision framework for operators choosing between these options.
Different product categories
One manages campaigns. The other sends emails. They are not the same thing.
The MailWizz vs SendGrid comparison is frequently framed as competing email marketing solutions. The framing produces confusion because the products serve different layers of the email stack despite both being involved in marketing email.
MailWizz is positioned in the email marketing platform category. The platform handles: subscriber lists and segmentation; campaign creation and template management; automation workflows and sequences; A/B testing and analytics; subscription forms and landing pages; suppression list and bounce processing; multi-user accounts and customer management. The platform does not handle: actual email sending infrastructure. MailWizz delegates SMTP delivery to external services through the BYOSP (Bring Your Own Service Provider) model.
SendGrid is positioned in the email SMTP service category alongside Mailgun, Amazon SES, Postmark, SparkPost. The service handles: actual email delivery infrastructure including MTAs and IPs; sender reputation management; ISP feedback loop integration; bounce and complaint processing; deliverability monitoring; authentication helpers (DKIM signing, SPF guidance, DMARC compliance). SendGrid additionally provides Marketing Campaigns feature adding marketing platform capabilities (campaign builder, automation, segmentation) on top of the core SMTP service; the Marketing Campaigns is comparable to MailWizz functionality.
The practical implications of the categorical difference:
An operator choosing MailWizz needs additional SMTP infrastructure to actually send emails. The choices: self-hosted Postfix/Exim/PowerMTA on the same server; external managed SMTP service like SendGrid, Mailgun, or Amazon SES; combination of multiple delivery servers with rotation.
An operator choosing SendGrid for transactional email gets complete SMTP infrastructure but no marketing platform features (until adding Marketing Campaigns subscription). The choice handles delivery only; campaigns and automation require additional platform.
An operator choosing SendGrid Marketing Campaigns gets both layers from a single vendor: marketing platform features plus SMTP delivery infrastructure. The integrated approach trades flexibility for simplicity.
The decision space therefore includes three primary configurations rather than binary choice between MailWizz and SendGrid.
MailWizz as marketing platform
MailWizz's role as marketing platform has specific characteristics.
Campaign management. Drag-and-drop email builder; HTML editor; plain text editor; template library; subject line A/B testing; campaign scheduling; throttling controls; recipient targeting through lists and segments.
Subscriber management. Unlimited subscribers (limited only by hosting capacity); list management; segmentation by custom fields and behaviour; subscription forms; double opt-in support; import/export operations; suppression list management.
Automation workflows. Autoresponder sequences; triggered campaigns based on subscriber actions; multi-step automation; conditional logic; date-based triggers; behaviour-based triggers.
Analytics and reporting. Campaign reports (opens, clicks, bounces, complaints); subscriber engagement tracking; geographic analytics; device analytics; click maps; conversion tracking.
Delivery server abstraction. MailWizz's distinguishing architectural feature: the platform separates campaign management from SMTP delivery. Operators configure one or more delivery servers in MailWizz; campaigns use these servers for sending. The delivery server can be SMTP credentials for any provider (SendGrid, Mailgun, SES, generic SMTP) or PHP-based Mail/Sendmail integration; multiple servers can be configured and rotated.
BYOSP model. Bring Your Own Service Provider pattern means MailWizz integrates with any SMTP service. Officially documented integrations include Amazon SES (SMTP and Web API), SendGrid (SMTP and Web API), Mailgun (SMTP and Web API), SparkPost (SMTP and Web API), Sendinblue/Brevo, generic SMTP servers. The pattern provides delivery flexibility unmatched by single-vendor solutions.
Multi-tenant capability. MailWizz natively supports customer accounts for agencies and resellers. Each customer has isolated lists, campaigns, statistics; the platform operator (account holder) administers the overall installation.
Code-level customisation. Source code included with license; operators can modify code for custom requirements. Plugin architecture for extending functionality. Theme customisation for visual changes.
What MailWizz does not provide. No SMTP infrastructure (delegated to external services); no built-in IP pool management; no native deliverability monitoring beyond bounce/complaint tracking; no managed sender reputation services; no compliance certifications (SOC 2, HIPAA, etc.) for the application itself.
SendGrid as SMTP service
SendGrid's role as SMTP service has different characteristics.
SMTP and API delivery. SMTP server (smtp.sendgrid.net port 587) accepting authenticated submission; Web API (v3) for programmatic sending; SMTP relay for application integration; mature SDKs across major programming languages (PHP, Python, Node.js, Ruby, Java, Go, .NET).
Managed IP pools. Shared pools segmented by sender quality; dedicated IP options on Pro and higher tiers ($80-89/month per IP); IP warmup support for dedicated IPs.
Deliverability infrastructure. Established ISP relationships across major mailbox providers; feedback loop integration with major ISPs; managed sender reputation; abuse complaint handling; bounce categorisation; reputation monitoring tools.
Authentication helpers. DKIM signing through SendGrid or custom domain; documented SPF setup; DMARC compliance support; subuser domain management for multi-tenant.
Marketing Campaigns add-on. SendGrid Marketing Campaigns adds marketing platform features on top of SMTP infrastructure: campaign builder; automation workflows; segmentation; contact management; subscription forms; A/B testing. Pricing separate from transactional email pricing.
Email Activity Feed. Detailed per-message tracking showing submission, delivery, opens, clicks, bounces, complaints. Searchable feed for debugging delivery issues; webhook integration for event handling.
Compliance and security. SOC 2 Type II certified; HIPAA-eligible plans available; comprehensive compliance documentation; enterprise-grade security infrastructure.
SendGrid pricing structure (2026):
| Plan | Email volume | Cost/month | Notes |
|---|---|---|---|
| Free | 100/day forever | $0 | Testing and very low volume |
| Essentials | 40K/month | $14.95 | Basic transactional capability |
| Essentials | 100K/month | $34.95 | Mid-tier transactional |
| Pro | 100K/month | $89.95 | Adds dedicated IP option |
| Pro | 300K/month | $249 | Higher Pro tier |
| Premier | Custom | $1,000+/month | Enterprise with dedicated support |
| Marketing Campaigns Basic | 5K contacts | $20/month additional | Basic marketing features |
| Marketing Campaigns Advanced | 10K contacts | $80/month additional | Full marketing features |
| Dedicated IP add-on | Per IP | $80-89/IP/month | Pro plan or higher |
What SendGrid does not provide (without Marketing Campaigns). No native subscriber list management beyond basic API contact storage; no native campaign UI; no automation workflows (in base SMTP plans); no segmentation tools (basic only); limited subscription form capabilities.
Three deployment configurations
Operators typically choose among three deployment configurations rather than binary MailWizz vs SendGrid.
Configuration 1: MailWizz alone with self-hosted SMTP. MailWizz handles marketing platform; self-hosted Postfix, Exim, or PowerMTA handles delivery. Configuration: install MailWizz on Linux server; install MTA on same or separate server; configure MailWizz to use local MTA via PHP Mail or local SMTP submission; configure IP reputation, authentication, monitoring at MTA level. Best for: technically sophisticated operators wanting full control and lowest ongoing cost; high-volume operations where infrastructure scale justifies operational investment.
Configuration 2: SendGrid alone (with or without Marketing Campaigns). SendGrid handles both SMTP delivery and (optionally) marketing platform features. Configuration: SendGrid account with Essentials or higher plan; optional Marketing Campaigns subscription for marketing features; configure authentication for sending domains; use SendGrid UI or API for all email operations. Best for: operators preferring single-vendor simplicity; teams without infrastructure operational capacity; transactional-focused use cases where Marketing Campaigns is optional.
Configuration 3: MailWizz with SendGrid as SMTP backend. MailWizz handles marketing platform; SendGrid handles SMTP delivery. Configuration: install MailWizz on Linux server; create SendGrid account at appropriate tier; configure MailWizz delivery server with SendGrid SMTP credentials or Web API plugin; verify authentication; test sending. Best for: operators wanting MailWizz's marketing flexibility plus managed SMTP simplicity; mid-volume operations balancing cost and operational simplicity; agencies wanting MailWizz's multi-tenant capability with SendGrid's deliverability.
The configurations have different trade-offs:
| Aspect | MailWizz alone | SendGrid alone | MailWizz + SendGrid |
|---|---|---|---|
| Operational complexity | High (MTA + platform) | Low (managed) | Medium (platform only) |
| Cost at low volume | Higher (server costs) | Low | Medium |
| Cost at high volume | Lowest | Highest | Medium |
| Marketing features depth | High (MailWizz) | Medium (Marketing Campaigns) | High (MailWizz) |
| Deliverability baseline | Operator-dependent | SendGrid managed | SendGrid managed |
| Vendor lock-in | Low (BYOSP flexibility) | Medium (SendGrid dependent) | Low (can swap SMTP) |
| Compliance posture | Operator-managed | SendGrid certifications | Mixed |
| Multi-tenant capability | Native MailWizz | SendGrid subuser model | Native MailWizz |
MailWizz + SendGrid integration setup
The MailWizz + SendGrid combination requires specific setup steps.
Step 1: SendGrid account configuration. Create SendGrid account at appropriate tier (Essentials at $14.95/month for moderate volume; Pro at $89.95 for higher volume or dedicated IPs). Configure sender authentication (SPF, DKIM) through SendGrid's domain authentication wizard. Verify domains and IPs are correctly authenticated.
Step 2: SendGrid API credentials. Generate API key with mail sending permissions. The API key serves as authentication credential when MailWizz submits emails. Store credentials securely in MailWizz configuration.
Step 3: MailWizz delivery server creation. Navigate to MailWizz admin panel → Backend → Servers → Delivery Servers → Create New. Two options for SendGrid integration:
- SMTP method: Server type SMTP; Hostname smtp.sendgrid.net; Port 587 (or 25, 2525); Protocol TLS; Username "apikey" (literal string); Password [SendGrid API key]; From email and from name configured per requirements.
- Web API method: Install SendGrid Web API plugin for MailWizz (available in marketplace); server type SendGrid Web API; configure with API key; faster than SMTP at high volumes due to API efficiency.
Step 4: Bounce and feedback handling. Configure bounce processing through MailWizz's bounce server option (if SMTP) or webhook integration (if Web API). SendGrid sends bounce notifications; MailWizz processes them to suppress recipients automatically. Set up complaint feedback loop similarly.
Step 5: Testing and validation. Send test campaign to verify integration works correctly. Check email headers to confirm SendGrid is the actual sender; verify authentication (SPF, DKIM); confirm tracking pixels and click tracking function correctly. Run small validation campaign before full production launch.
Step 6: Production cutover. Once validated, configure MailWizz to route all campaign traffic through SendGrid delivery server. Monitor delivery rates, bounce rates, complaint rates during initial production days.
Configuration code example for MailWizz config.php with SendGrid SMTP:
# MailWizz delivery server settings for SendGrid SMTP hostname = smtp.sendgrid.net port = 587 protocol = tls username = apikey password = SG.your-actual-api-key-here # Or via API plugin: api_endpoint = https://api.sendgrid.com/v3 api_key = SG.your-actual-api-key-here
A common MailWizz + SendGrid setup error involves SPF alignment. SendGrid sends emails from sendgrid.net domain envelope by default; the SPF record validates against sendgrid.net, not the sender's brand domain. The mismatch means SPF technically passes but does not align with the From domain, weakening DMARC enforcement. The fix: configure SendGrid Domain Authentication (or Authenticated Domains in newer terminology) so SendGrid sends with the sender's brand domain in envelope. This requires adding CNAME records pointing to SendGrid's authentication infrastructure. With proper Domain Authentication, SPF and DKIM both align with the From domain; DMARC enforcement works correctly. Skipping Domain Authentication produces silently broken alignment that affects deliverability subtly over time. Always configure Domain Authentication when using SendGrid as backend.
Cost comparison across configurations
Cost comparison across the three configurations at typical volume tiers:
| Volume / Contacts | MailWizz alone (self-hosted SMTP) | SendGrid alone | MailWizz + SendGrid |
|---|---|---|---|
| 10K emails/month, 1K contacts | $25/month (VPS + amortised license) | $15/month (Essentials 40K) | $40/month (VPS + Essentials) |
| 50K/month, 10K contacts | $40/month | $50/month plus $20 Marketing | $65/month |
| 100K/month, 25K contacts | $80/month | $90/month plus $50 Marketing | $110/month |
| 250K/month, 50K contacts | $200/month (PowerMTA license) | $249/month plus $130 Marketing | $300/month |
| 500K/month, 100K contacts | $400/month (multi-server) | $700/month plus $250 Marketing | $550/month |
| 1M/month, 250K contacts | $700/month | $1,200/month plus enterprise Marketing | $1,000/month |
| 2M/month, 500K contacts | $1,200/month | $2,000+/month | $1,800/month |
Cost pattern summary:
Under 50K monthly emails. SendGrid alone often cheapest due to low-tier pricing; MailWizz options higher due to infrastructure cost floor.
50K-250K monthly. All three configurations competitive; choice driven more by operational preference than cost.
250K-500K monthly. MailWizz alone becomes clearly cheapest; MailWizz + SendGrid intermediate; pure SendGrid most expensive.
500K-2M monthly. MailWizz alone produces 40-50% cost savings versus pure SendGrid; MailWizz + SendGrid combination produces 20-30% savings.
Above 2M monthly. MailWizz alone with proper self-hosted infrastructure produces substantial savings; the differential grows with volume.
The cost calculations should include operational time investment. MailWizz alone has highest operational time (15-30 hours/month); MailWizz + SendGrid intermediate (10-15 hours); pure SendGrid lowest (3-5 hours). At market rates ($75-150/hour), the operational time cost can equal or exceed infrastructure savings at lower volumes.
Feature comparison
Feature comparison between MailWizz and SendGrid (with Marketing Campaigns where relevant):
| Feature | MailWizz | SendGrid |
|---|---|---|
| Subscriber/contact management | Unlimited (server-bounded) | Contact-limited by plan tier |
| Campaign creation UI | Drag-and-drop plus HTML editor | Marketing Campaigns drag-and-drop |
| Automation workflows | Yes (autoresponders, sequences) | Marketing Campaigns automation |
| Segmentation | Custom field rule-based | Marketing Campaigns rule-based |
| A/B testing | Subject line and content | Subject line in Marketing Campaigns |
| Templates | Templates included; custom HTML | Template library |
| Subscription forms | Built-in forms | Forms in Marketing Campaigns |
| API | Full REST API | Comprehensive REST API + SDKs |
| Multi-tenant accounts | Native multi-customer | Subuser model |
| White-label | Yes (Extended License) | Custom branding on enterprise |
| SMTP infrastructure | External required | Built-in |
| IP pool management | External (SMTP provider) | Built-in shared pools; dedicated optional |
| Deliverability tooling | External | Email Activity, deliverability insights |
| ISP feedback loops | External | Integrated |
| Compliance certifications | None (operator-managed) | SOC 2 Type II, HIPAA-eligible plans |
| Transactional email | Indirect through delivery server | Native transactional focus |
| Webhook events | Configurable | Comprehensive webhooks |
The feature comparison shows complementary strengths:
MailWizz strengths: marketing platform features (campaign management, automation, segmentation); unlimited subscribers; multi-tenant architecture; code-level customisation; one-time cost structure.
SendGrid strengths: managed SMTP infrastructure; established sender reputation; deliverability tooling; comprehensive compliance certifications; transactional email focus; ISP relationship management.
The MailWizz + SendGrid combination captures both strength sets. Pure MailWizz (with self-hosted SMTP) captures MailWizz strengths at the cost of operator-managed SMTP responsibility. Pure SendGrid (with Marketing Campaigns) captures SendGrid strengths but lacks MailWizz's multi-tenant architecture and customisation flexibility.
Deliverability implications
Each configuration produces different deliverability profiles.
MailWizz alone with self-hosted SMTP. Deliverability depends entirely on operator capability. Well-managed dedicated infrastructure (PowerMTA on Hetzner, proper warmup, disciplined sending, ongoing monitoring) can produce 90-95% inbox placement. Poorly-managed self-hosted SMTP (misconfigured authentication, neglected warmup, shared budget hosting) produces worse outcomes than any managed alternative. The variance is wide; operator capability is the determining factor.
SendGrid alone (with or without Marketing Campaigns). Deliverability inherits SendGrid's managed infrastructure. Typical inbox placement 85-92% for senders following basic practices on shared IPs; dedicated IP options with proper warmup achieve 90-95%. SendGrid's quality controls remove problematic senders, protecting baseline pool reputation. Operators without deliverability expertise produce solid outcomes through SendGrid's managed approach.
MailWizz + SendGrid combination. Deliverability inherits SendGrid's managed infrastructure (because SendGrid handles actual delivery). MailWizz's role does not affect deliverability directly; the platform manages campaigns but delivery happens through SendGrid. Typical inbox placement matches SendGrid alone: 85-92% shared IPs, 90-95% dedicated. The combination provides MailWizz's marketing flexibility without the deliverability risk of operator-managed SMTP.
The deliverability comparison comes down to:
For operators with strong deliverability expertise wanting maximum control: MailWizz alone with dedicated self-hosted SMTP can produce best deliverability outcomes. The work is substantial but the ceiling is higher than managed alternatives.
For operators wanting solid baseline deliverability without managing SMTP infrastructure: MailWizz + SendGrid or pure SendGrid produce comparable deliverability through SendGrid's managed approach. The choice between them is about marketing platform features rather than deliverability.
For operators without deliverability expertise running MailWizz with poorly-configured self-hosted SMTP: typical outcomes are worse than any managed alternative. The configuration is operationally risky for operators without the expertise to manage it.
Decision framework
The decision framework for MailWizz vs SendGrid configurations in 2026:
Use MailWizz alone with self-hosted SMTP when: volume exceeds 500K monthly emails (cost savings substantial); technical team has email deliverability expertise; operational time investment is justified by cost savings; multi-tenant architecture (agency operations) benefits from MailWizz's native support; data sovereignty or compliance requires self-hosted control; long-term operational cost is meaningful constraint.
Use SendGrid alone (with or without Marketing Campaigns) when: operational simplicity is the primary priority; team lacks infrastructure operational capacity; transactional email is the primary use case; SendGrid's compliance certifications (SOC 2, HIPAA) are operationally required; single-vendor relationship simplifies operations; budget supports the SaaS pricing model.
Use MailWizz with SendGrid as SMTP backend when: MailWizz's marketing platform features are operationally valuable; SendGrid's managed SMTP eliminates deliverability burden; cost balance favours combination over pure SendGrid; team has DevOps capacity for MailWizz operations but lacks SMTP expertise; mid-volume operations (50K-500K monthly typical) where combination cost balance works well.
Choose SendGrid Marketing Campaigns over MailWizz when: already using SendGrid for transactional and want unified vendor relationship; the marketing features needed are covered by SendGrid Marketing Campaigns; operational simplicity outweighs MailWizz's customisation potential; budget supports SendGrid's pricing.
Consider alternatives to both when: e-commerce focus suggests Klaviyo or Omnisend; B2B marketing automation suggests HubSpot or ActiveCampaign; mid-market simplicity suggests MailerLite or Brevo; transactional-only needs suggest Postmark or Mailgun; specific specialised platforms produce better outcomes for the use case.
The 2026 default progression for typical operators:
- Start with SendGrid free tier or low-cost plan during early operations (operational simplicity, low cost at small volume)
- Continue on SendGrid as growth progresses through moderate volume (SendGrid pricing remains reasonable)
- Evaluate MailWizz + SendGrid combination at 100K+ monthly when marketing platform features become operational priority or costs become material
- Consider full MailWizz with self-hosted SMTP at 500K+ monthly when cost savings justify operational investment
- Stay on MailWizz + SendGrid combination indefinitely if balance between control and simplicity fits operations
A B2C SaaS client we worked with through 2024-2025 illustrates the MailWizz + SendGrid combination pattern. They started on SendGrid Pro alone in 2023 at approximately 200K monthly emails for marketing and transactional. Through 2024 their marketing volume grew to 800K monthly while transactional remained 200K. SendGrid Pro plus Marketing Campaigns combined cost approximately $1,200/month. We migrated their marketing operations to MailWizz hosted on Hetzner CX42 (€18/month) using SendGrid Pro as the SMTP backend for marketing (kept same SendGrid subscription downgraded to volume-appropriate tier). Transactional continued on SendGrid directly. Total post-migration cost: approximately $700/month (Hetzner $20 + SendGrid Pro $400 + smaller Marketing Campaigns $50 for legacy contacts + operational time amortised). Annual savings: approximately $6,000. Migration project cost: approximately $5,000 (consulting, MailWizz setup, list migration, integration testing). Payback period: under 1 year. The combination provided MailWizz's marketing flexibility (multi-tenant capability they did not need initially but useful later for white-label features) plus SendGrid's deliverability without operator-managed SMTP. The lesson: MailWizz + SendGrid combinations produce strong outcomes for moderate-volume operations valuing both marketing platform features and managed SMTP simplicity. The configuration is operationally more complex than pure SendGrid but produces meaningful savings at sufficient scale.