vsMailforge vs Infraforge: The Salesforge In-Account Upgrade Decision
These are not competing products. They are the entry tier and graduation tier of the same Salesforge infrastructure stack, with the same login, the same masterbox, and the same DNS setup. The question is when to graduate.
The Verdict
Mailforge and Infraforge live in the same Salesforge account. You do not switch between them; you upgrade within the stack by adding the dedicated-IP fabric to mailboxes that currently sit on the shared-IP fabric. That structural detail changes how the comparison should be read.
The choice between "Mailforge" and "Infraforge" is really a choice about timing: at what point in the team's growth curve does the shared-IP risk profile no longer match the team's deliverability stakes. Most fleets cross that threshold somewhere between 50 and 75 active mailboxes, or when the first significant deliverability incident traces back to a noisy-neighbor on the shared IP pool. Before that threshold, Mailforge is the right tier because shared IPs work fine and the bill is small.
After it, Infraforge is the right tier because the cost of one degraded campaign exceeds the dedicated-IP fee. The transition itself is invisible to your end users; the same mailboxes keep working, the same DNS records keep resolving, the only thing that changes is which fabric they sit on. The pricing math (the $99 IP block, the per-domain SSL fee, the mailbox rate bump) is in the dedicated teardown.
Mailforge vs Infraforge
| Feature | Mailforge | Infraforge |
|---|---|---|
| Pricing | ||
| Price per Mailbox | $2-$3/mo Shared IP SMTP | $3-$4/mo Dedicated IP SMTP |
| Cost for 100 Mailboxes | $200-$300/mo 100 x $2-$3, no extra fees | $350-$499/mo 100 x $3.50 avg + $99 dedicated IP |
| Infrastructure | ||
| IP Infrastructure | Shared IPs Shared IP pools | Dedicated IPs Your own dedicated IPs ($99/mo extra) |
| Multi IP Provisioning | No Not available on shared IPs | Yes Provision multiple dedicated IPs |
| DNS Automation | Auto + bulk Automated DNS and bulk DNS updates | Auto Automated DNS setup |
| Deliverability | ||
| Pre-warmed Domains | No Standard domain setup | Yes Domains come pre-warmed |
| Features | ||
| Masterbox | No Standard management | Yes Centralized masterbox for management |
| Domain Masking | SSL + masking Included in platform | $2/domain/mo SSL and domain masking at $2/domain/mo |
| Automation | ||
| API Access | Not specified Not published | Yes API access available |
What changes in-account when you upgrade
The Mailforge-to-Infraforge transition is not a migration in the usual vendor-switching sense. You stay in the same Salesforge login. You keep the same masterbox console.
You keep the same DNS records for SPF, DKIM, and DMARC. The mailboxes you already provisioned keep their identities and reputation history. What actually changes: the IP fabric beneath your mailboxes flips from the shared pool to a dedicated allocation.
Your sending IP changes (which triggers a short reset of IP reputation that re-warms through your existing sender tool), but everything else continues unchanged. The masterbox shows the IP block as a new resource in your account; you can see its reputation metrics separately from the mailbox reputation metrics. This matters for decision-making.
A team that imagines "upgrading" as a multi-day migration project does not exist here. The upgrade is a billing change that propagates through the infrastructure over about 24 hours. The decision is reversible in either direction without operational disruption.
Key takeaways
- Same login, same masterbox, same DNS setup
- Mailbox identities and existing reputation history preserved
- IP fabric beneath the mailboxes flips from shared to dedicated
- Upgrade propagates in roughly 24 hours, reversible without disruption
How to read the noisy-neighbor signals that say upgrade now
Teams who upgrade reactively (after an incident) usually wish they had upgraded preemptively. The signals to watch on Mailforge that suggest the upgrade window is approaching: First, your inbox placement rate drifts down by 5 percentage points or more over a two-week window without any change in your sending behavior. The cause is almost always a neighbor on the shared pool sending aggressively.
Second, a blacklist hit appears on your IP that you did not trigger. Mailforge's shared IPs occasionally land on Spamhaus or other lists due to other tenants, and the recovery process takes longer than dedicated-IP recovery because you are not the only stakeholder. Third, a specific ISP starts deferring or rejecting your sends despite no changes in your domain reputation.
Microsoft 365 and Yahoo are common sources because they are more aggressive about shared-pool reputation scoring. None of these signals are catastrophic individually, but they are leading indicators that the shared-pool dynamics are starting to affect your reputation. Upgrade before the trend compounds.
Key takeaways
- Inbox placement drift of 5+ points over two weeks without behavior change
- Blacklist hit on the shared IP that you did not trigger
- ISP-specific deferrals or rejections without domain reputation changes
- These are leading indicators, not failures; upgrade before they compound
The volume and stakes math for graduation timing
Two heuristics for when to graduate from Mailforge to Infraforge: Volume heuristic: above 50K to 75K sends per month, the shared-pool noise starts to register meaningfully in your reputation metrics. Below that, the warmup engineering of your sender tool usually masks the shared-IP variability. The transition is gradual, not sharp; pay attention to your campaign-level reply rates over a six-week window.
Stakes heuristic: if a one-week deliverability incident would cost your business more than $1,200 (the rough annual cost of the $99/mo IP block fee), the dedicated IP is insurance worth buying preemptively. For agencies running client campaigns, the stakes calculation includes contractual SLAs and the relationship cost of an incident, which usually justifies upgrading earlier than the volume heuristic alone would suggest. The two heuristics often conflict in practice.
A small agency at 20K sends per month with high-stakes client work crosses the stakes threshold long before the volume threshold. A 100K-sends-per-month in-house team with low-stakes campaigns crosses the volume threshold long before the stakes threshold. Use whichever applies more clearly to your context.
Key takeaways
- Volume heuristic: 50K-75K sends per month
- Stakes heuristic: incident cost above $1,200/year
- Agencies usually cross stakes threshold first
- In-house teams usually cross volume threshold first
When staying on Mailforge is the right answer indefinitely
Not every team should upgrade. Two patterns where staying on Mailforge is the right long-term answer: Pattern one: stable low-volume sending (under 30K per month) with consistent inbox placement above 80 percent. The economics of the dedicated IP fee never justify themselves for fleets this small.
Stay on Mailforge and reinvest the $99/mo savings elsewhere. Pattern two: cost-sensitive teams whose deliverability stakes are low (announcements, transactional-like communications, internal notifications dressed up as cold email). The reputation insurance of Infraforge is not load-bearing for these workloads because the downside of a degraded campaign is small.
For everyone else, the question is not whether to upgrade but when. Plan for the upgrade rather than reacting to it.
Key takeaways
- Stable low-volume sending under 30K/mo can stay on Mailforge
- Low-stakes campaigns rarely justify the dedicated IP fee
- Most other teams should plan the upgrade rather than react to it
- Reaction to an incident is the most expensive timing
Pros & Cons
Mailforge
Strengths
- Lower per-mailbox cost at $2-$3/mo
- SSL and domain masking included
- Bulk DNS updates and domain transferring
- Good starting point for the Salesforge ecosystem
- 10,000+ businesses using the platform
Limitations
- Shared IP infrastructure only
- Deliverability depends on shared IP pool quality
- No pre-warmed domains
- No API access mentioned
Infraforge
Strengths
- Dedicated IP infrastructure for sender isolation
- Pre-warmed domains for faster ramp-up
- Multi IP provisioning and masterbox
- API access for automation
- Natural upgrade from Mailforge
Limitations
- Per-mailbox cost 50-100% higher than Mailforge
- Dedicated IP adds $99/mo on top of mailbox costs
- Domain masking adds $2/domain/mo
- SMTP only, no Google Workspace or Microsoft 365
Got questions? We've got answers.
An in-account upgrade. You stay in the same Salesforge login, keep the same masterbox console, and retain your existing DNS setup. The IP fabric beneath your mailboxes flips from shared to dedicated, but mailbox identities and reputation history persist.
Ready to hit primary?
Set up SendKit's isolated infrastructure and start sending in under 15 minutes.
Dedicated IPs on every plan. Cancel anytime.