Mailforge vs Infraforge: When to Make the In-Account Upgrade

Moving from Mailforge to Infraforge isn't a migration in the usual vendor-switching sense. You keep the same Salesforge login, the same masterbox console, and the same DNS records for SPF, DKIM, and DMARC. Mailboxes you've already provisioned keep their identities and reputation history intact.

What actually changes is the IP fabric underneath: it flips from the shared pool to a dedicated allocation. Your sending IP itself changes, which resets IP-level reputation and requires a short re-warm through your existing sender tool, but nothing else shifts. The masterbox lists the new IP block as a resource in your account, with reputation metrics tracked separately from the mailbox metrics.

This matters for how you plan the move. There's no multi-day migration project to dread here, the upgrade is a billing change that rolls out across your infrastructure over roughly 24 hours, and it's reversible in either direction without disrupting operations.

Teams that upgrade reactively, after something's already gone wrong, almost always wish they'd moved sooner. A few signals on Mailforge worth watching for as the upgrade window approaches: First, your inbox placement rate slides 5 percentage points or more over a two-week stretch with no change in your own sending behavior. Almost always, that traces back to a neighbor on the shared pool sending aggressively.

Second, a blacklist hit shows up on your IP that you didn't cause. Mailforge's shared IPs occasionally land on Spamhaus or similar lists because of other tenants, and recovery takes longer than it would on a dedicated IP, since you're not the only stakeholder in getting it resolved. Third, a specific ISP starts deferring or rejecting your sends with no change to your own domain reputation.

Microsoft 365 and Yahoo show up most often here, since they score shared-pool reputation more aggressively. None of these are catastrophic on their own, but together they're leading indicators that shared-pool dynamics are starting to erode your reputation. Better to upgrade before the trend compounds.

Two rules of thumb for when to make the jump from Mailforge to Infraforge: The volume rule: past 50,000 to 75,000 sends a month, shared-pool noise starts showing up meaningfully in your reputation metrics. Below that, your sender tool's warmup engineering usually masks the shared-IP variability. The shift is gradual rather than sudden, so watch campaign-level reply rates over a six-week window.

The stakes rule: if a single week of degraded deliverability would cost your business more than $1,200, roughly what the $99/mo IP block fee runs annually, the dedicated IP is insurance worth buying ahead of time. For agencies running client campaigns, factor in contractual SLAs and the relationship cost of an incident, which usually justifies upgrading earlier than volume alone would suggest. These two rules often pull in different directions.

A small agency at 20,000 sends a month doing high-stakes client work crosses the stakes threshold long before the volume threshold. A 100,000-sends-a-month in-house team running low-stakes campaigns crosses the volume threshold well before the stakes one. Go with whichever applies more clearly to your situation.

Not every team needs to make the jump. Two patterns where staying on Mailforge is the right long-term call: The first: stable, low-volume sending (under 30,000 a month) holding consistent placement above 80 percent. At that size, the dedicated-IP fee's economics never really justify themselves, stay on Mailforge and put the $99/mo elsewhere.

The second: cost-sensitive teams whose deliverability stakes are genuinely low, announcements, transactional-style messages, internal notifications dressed up as cold email. Infraforge's reputation insurance doesn't do much work for these workloads, since a degraded campaign wouldn't cost much anyway. For everyone else, it's less a question of whether to upgrade than when.

Plan the move rather than reacting to a bad week.