Mailforge Pricing: The Complete Breakdown

Mailforge Plans

What's Not Included

Mailforge as the Salesforge ecosystem entry tier

Mailforge isn't a standalone product — it's the shared-IP entry tier of the Salesforge infrastructure stack. The pricing strategy assumes most cold email teams start cheap on shared IPs, grow into needing dedicated isolation, and eventually upgrade to Infraforge ($3-$4 per mailbox plus the $99 IP block fee) within the same vendor account. Mailforge claims 10,000-plus businesses, the largest customer count anywhere in the Salesforge ecosystem, which reflects its entry-tier positioning.

The structural advantage is that in-account upgrade path. Moving from Mailforge to Infraforge happens inside the existing Salesforge account — same login, same masterbox interface, same DNS automation state, same domain inventory. Mailboxes migrate to the dedicated-IP fabric without needing to re-provision anything.

For teams already inside the Salesforge ecosystem, running Salesforge sequences or other Salesforge products, Mailforge is the default starting point precisely because that upgrade path is friction-free. For teams outside the ecosystem, Mailforge's pricing is competitive on raw rate but doesn't get the benefit of that upgrade-path advantage. They're paying for an entry tier without the future-path value baked in.

The shared-IP economics that make Mailforge structurally cheap

Mailforge's $2-$3 per mailbox is achievable specifically because the IP infrastructure is shared across the whole customer base. One IP pool handles many senders, amortizing the underlying IP cost — each clean IP is genuinely expensive to acquire and maintain — across a large number of mailboxes. Dedicated-IP architectures invert that economics entirely: one IP per customer means one buyer bears the full IP cost, which is exactly why Infraforge charges $99/mo per IP block on top of its per-mailbox rate.

The shared-IP trade-off isn't theoretical, either. Customers on the same pool share sender reputation, so when one customer's sending hygiene slips, the whole pool's reputation degrades and every customer on it feels it. The 10,000-plus customer base suggests Salesforge actively manages pool composition, probably segmenting by sending pattern, but the approach isn't publicly documented and individual buyers can't inspect their own pool.

For low-to-mid-volume senders running well-warmed sequences with clean list hygiene, the shared-pool economics work fine, since pool-wide reputation problems are rare. For high-volume senders, where every percentage point of inbox placement means real revenue, that shared-pool variability becomes the argument for moving to dedicated IPs.

What Mailforge bundles versus what it does not

Mailforge bundles the infrastructure-layer features: automated DNS configuration (SPF, DKIM, DMARC, MX), bulk DNS updates across many domains at once, domain transferring, SSL certificate management, domain masking for tracking-link rewriting, and multi-workspace support for separating client books or campaign cohorts. Those are the operational features that matter at scale, and most providers offer them too. What it doesn't bundle: email warmup, placement testing, an email verifier, or a blacklist monitor.

Those deliverability-layer tools sit explicitly outside the product and have to come from the sending platform or a standalone service. That's a deliberate architectural choice — Salesforge treats deliverability tooling as the sending platform's job, since their own Salesforge sequencer covers it and they trust competitors' sequencers to handle it for everyone else. The pricing consequence: teams already using a sending platform with native deliverability tooling get cheap raw mailboxes and pay for nothing they don't use.

Teams running barebones sequencers without that coverage face $75-$200/mo in standalone tool costs that eat into the Mailforge cost advantage. Which side of that line your sending stack sits on determines the real total-cost comparison.

When Mailforge's pricing model structurally fits

Mailforge fits cleanly for three kinds of buyers. First, Salesforge-ecosystem buyers running Salesforge sequences who want the cheapest infrastructure tier and the option to upgrade to Infraforge later — the ecosystem alignment makes that in-account upgrade trivial whenever it's needed. Second, mid-volume cold email teams running a sending platform that already covers warmup and placement testing (Smartlead, Instantly, Sendbox), for whom the raw mailbox rate is the cheapest path to 100-500 SMTP mailboxes.

Third, cost-driven solo operators and small agencies who can live with shared IPs and want to keep infrastructure spend minimal. It fits less cleanly for teams that need bundled deliverability monitoring (InboxKit handles that better at a slightly higher rate), teams that want Google Workspace or Microsoft 365 mailboxes (Zapmail or InboxKit cover those), or teams that already know dedicated IPs are non-negotiable (Infraforge is the direct route). The structural fit here is "commodity SMTP at scale on shared IPs, for teams whose deliverability tooling lives somewhere else."