That's quite a question you have asked and important to separate the two. Let me break down the summarized things for your better understanding.
Infrastructure planning is different depending on whether you're using:
- Mumara Campaigns (Self-Hosted / Cloud deployment)
- MumaraONE (SaaS managed by Mumara)
The sending logic is similar but infrastructure responsibility changes.
For Mumara Campaigns (Self-Hosted or on Cloud Server)
Here,
you control the server, so infrastructure is your responsibility.
Server Capacity
Minimum recommendations for high volume:
- NVMe or SSD storage
- 8–16 GB RAM (depending on volume)
- Dedicated CPU cores
- Stable outbound network
Example: One sender running Mumara Campaigns self-hosted scaled to ~900K/day on:
- 16GB RAM dedicated server
- 3 warmed IPs
- Optimized sending node configuration
Mumara handled queueing fine but performance depended on server tuning.
Dedicated Sending IPs
For 500K+ daily:
- Avoid shared IPs
- Warm each IP properly
- Keep volume consistent
Jumping volume without warm-up is the #1 cause of throttling not the software.
Authentication Setup
Must-have:
- SPF passing
- DKIM aligned
- DMARC published
- Branded tracking domain
- Feedback loops
Without this, high volume will trigger Yahoo/Gmail filtering regardless of hardware.
Sending Behavior
Even on powerful servers, mailbox providers dislike:
- Sudden 5x spikes
- Sending to cold segments
- High complaint rates (>0.1%)
Infrastructure ≠ immunity from reputation rules.
For MumaraONE (SaaS)
Here’s the key difference:
- You don’t manage servers or system scaling.
MumaraONE infrastructure is managed by Mumara, including:
- Server resources
- Application scaling
- Background workers
- Core optimization
So your focus shifts from hardware → to
sending discipline.
Volume Planning
Even in SaaS, mailbox providers still monitor:
- Sudden volume increases
- Complaint rate
- Bounce rate
- Engagement quality
MumaraONE can handle technical scaling but reputation management is still your job.
IP & Pool Strategy
Depending on your setup:
- Dedicated IPs need warming
- Shared pools require careful segmentation
If you suddenly blast 1M cold contacts, even SaaS won’t protect your reputation.
Automation Load (Mumara)
If using Automation Add-on:
- Ensure triggers are optimized
- Avoid overlapping massive campaigns + heavy automation
- Monitor activity logs
System scaling is managed but sending strategy matters.
