Mailforge Review

Mailforge sells the cheapest path to bulk cold email mailboxes: automated DNS, shared-IP infrastructure, and a calculator-style pricing model that undercuts official Google Workspace and Microsoft 365 by a wide margin. This review covers what that low price actually includes, where it doesn't, and how Mailforge's own user reviews describe living with it.

Verdict at a glance

What is Mailforge?

Mailforge is cold email infrastructure software from the Salesforge family — the same company behind Salesforge (sequencing), Leadsforge (prospect data), Infraforge and Primeforge (dedicated Google/Microsoft mailbox infrastructure), Warmforge (deliverability/warmup), and Agent Frank (AI SDR). Mailforge's specific job in that stack is bulk, low-cost domain and mailbox provisioning on shared IP infrastructure — the opposite end of the spectrum from Primeforge's official-account approach under the same corporate umbrella.

Instead of dedicated Google Workspace or Microsoft 365 tenants, Mailforge creates mailboxes on infrastructure shared across its customer base, with DNS (SPF, DKIM, DMARC) configured automatically. The pitch is volume and price: the vendor's own comparison claims 200 mailboxes run about $484/month on Mailforge versus roughly $1,200–$1,680/month for the equivalent in Google Workspace or Microsoft 365 seats. That math holds up arithmetically — it's a genuine discount — but it's comparing against retail productivity-suite pricing, not against other cold email infrastructure vendors, several of which (InboxKit, Zapmail) also sell official mailboxes at a smaller markup than full retail.

How it works

Setup is built for speed: connect or buy .com domains (Mailforge sells them at $14/year), and DNS records populate automatically without any manual editing. The vendor advertises domains ready in about five minutes. Mailboxes are created in bulk against those domains, and because Mailforge is software-agnostic, credentials export to whatever sequencer you're already running — the vendor specifically calls out compatibility with its sibling Salesforge, plus general SMTP/API access for anything else, and even MCP connectivity for AI-assistant workflows.

Multiple workspaces let agencies keep client setups separate, bulk DNS updates mean a record change propagates across every connected domain at once, and domain masking lets a secondary sending domain redirect visitors to your real site rather than a bare parking page. None of this is unusual for the category — InboxKit, Zapmail, and Mailscale all offer versions of the same automation — but Mailforge's version is well executed and, per G2 reviewers, notably fast to get running.

Mailforge pricing (2026)

Here's the real math the headline "$3/mailbox" doesn't show. A realistic starter setup — 10 mailboxes across 4 domains, annual billing — runs: $30/month for the mailbox slots, plus $56/year in domains (about $4.67/month amortized), for a base of roughly $35/month. Add SSL and domain masking on those 4 domains ($8/month) and you're at about $43/month before any warmup. Since Mailforge doesn't include warmup, adding it — through Warmforge or another provider — typically adds $30–$50/month on top for a small mailbox count. All-in, a genuinely functional 10-mailbox setup lands closer to $65–$90/month, not the $30 the base slot price implies. That gap narrows at scale (the vendor's own 200-mailbox figure of $484/month already assumes volume pricing), but it's real at the entry tier where most new customers start.

The other cost trap: month-to-month billing. Mailforge's calculator shows a meaningfully higher rate for customers who don't commit to annual billing — one pricing snapshot showed $75/month for the same slot count that runs $30–$60/month annually. If you're not ready to commit for a year, budget for that premium.

What users say

Mailforge holds 4.7/5 on G2 across 81 reviews, and a lower score on Trustpilot — roughly 3.5/5 across about 15 reviews, which Trustpilot's own classification bands as "Average." That gap between platforms, and the small sample size on both, is worth taking at face value rather than averaging away.

The G2 themes are consistently positive: 25+ reviewer mentions single out setup speed as the standout, and 15+ separately praise responsive support — unusual specifics for a budget infrastructure tool, where support is often the first thing to get cut. Reviewers describe getting from signup to sending mailboxes in a fraction of the time manual DNS configuration would take, which tracks with the automated-setup pitch.

The Trustpilot picture is rougher, and the negative themes deserve the longer treatment the positive ones don't need. The single biggest complaint pattern is cancellation and billing friction: multiple reviewers describe subscriptions that kept charging after they believed they'd cancelled, with resolution requiring a direct message to support rather than a self-serve toggle — one reviewer said support handled it "the next day" once contacted, but the friction of needing to contact anyone at all is the complaint, not the eventual outcome. This bites hardest for smaller customers who don't have a billing contact or account manager relationship to escalate through. The workaround is mundane but effective: cancel through support proactively and confirm in writing rather than assuming a subscription toggle stopped billing.

A second theme is functional reliability at the edges — a smaller number of reviewers reported the send function failing outright across mobile and web, which one reviewer framed as the product failing at its most basic purpose. This is a more serious complaint than typical UX gripes because it affects the core send action, not a peripheral feature; it's also the kind of intermittent bug that's hard to verify as ongoing versus resolved from outside the platform, so treat it as a known but unquantified risk rather than a constant.

The third and most structural theme is shared-IP deliverability variability, which isn't really a bug — it's the tradeoff inherent to the product. Because Mailforge mailboxes sit on infrastructure shared across many customers, your inbox placement is partly a function of how well-behaved everyone else on that shared pool is, not just your own sending practices. A competing infrastructure vendor's own comparison page claims Mailforge averages around 63% inbox placement with roughly 23% landing in spam, against a claimed 82%/8% for dedicated Google accounts — that figure comes from a competitor with an obvious incentive to make its own dedicated-account product look better, so treat it as directional rather than verified, but it's consistent with the general shared-IP tradeoff and with independent reviewer comments about inconsistent placement. Pairing Mailforge with proper warmup (Warmforge or otherwise) is the standard mitigation, which is also why the missing warmup at the base price matters more than it would for a smaller feature gap.

Pros and cons

Pros

• Lowest per-mailbox price in the infrastructure category, especially past 50–100 mailboxes
• Genuinely fast automated DNS setup — domains ready in minutes
• Bulk DNS updates and multi-workspace support suit agency workflows
• G2 reviewers consistently praise setup speed and support responsiveness
• Integrates with any sequencer, plus API/CLI/MCP access
• Part of a broader stack (Salesforge, Warmforge, Leadsforge) if you want one vendor for the full outbound pipeline

Cons

• Shared IPs mean your deliverability is partly dependent on other customers' sending behavior
• Warmup isn't included — budget for a separate Warmforge or third-party subscription
• Monthly billing costs substantially more per mailbox than annual; the advertised rate assumes a yearly commitment
• No free trial
• Trustpilot reviewers report real cancellation and billing friction, including charges continuing post-cancellation
• Slot-based pricing means you pay for unused mailbox capacity once purchased

Mailforge alternatives

Mailforge sits in a crowded field, and it's worth knowing that several review pages you'll find in the SERPs for "Mailforge review" are written by direct competitors (InboxKit, Maildoso) or by Mailforge's own sibling products (Primeforge, Warmforge) reviewing each other — read all of them, including this one, knowing who benefits from the framing.

• Slicey — managed, done-for-you Google and Microsoft inboxes (Microsoft from $0.49 per inbox) with a self-serve dashboard, delivered pre-warmed with deliverability monitoring and automatic domain swaps. Slicey customers also get Outfalcon, a free bundled sequencer with unlimited sending.
• Primeforge — Mailforge's own sibling product, provisioning official Google Workspace and Microsoft 365 mailboxes instead of shared-IP infrastructure, at a higher price point.
• Infraforge — another Salesforge-family option, positioned around private (non-shared) infrastructure.
• InboxKit — official Google/Microsoft mailboxes with built-in monitoring (InfraGuard); pricier per mailbox but no shared-IP tradeoff.
• Zapmail — pre-warmed official Google and Microsoft mailboxes, competing mainly on speed to first send rather than lowest price.
• Maildoso — comparable shared-infrastructure pricing model to Mailforge; the two are frequently cross-compared in the category.

If lowest price per mailbox at real volume is the priority, Mailforge is hard to beat on the sticker number. If avoiding shared-IP variability matters more than price, Primeforge, InboxKit, or Zapmail's official-account approach is the more defensible choice.

Who should use Mailforge — and who shouldn't

Good fit: agencies and outbound teams provisioning mailboxes at real scale (50+) where the per-mailbox savings compound; teams already inside the Salesforge/Forge Stack ecosystem who want one vendor across sequencing, infrastructure, and warmup; senders who plan to pair Mailforge with a dedicated warmup product from day one rather than treating it as optional.

Poor fit: anyone who needs a self-serve, no-hassle cancellation experience — the Trustpilot billing complaints are a real signal worth weighing; teams sending at a volume too small to absorb the 10-mailbox/domain-plus-SSL-plus-warmup real cost, where a couple of manually configured official mailboxes would be simpler; and anyone deliverability-sensitive who isn't prepared to budget for warmup and monitor placement actively, since shared IPs put outcomes partly outside your own control.