Nitrosend vs Inframail.

TL;DR

Inframail is cold email infrastructure. It provisions Microsoft-backed mailboxes in bulk on domains you buy or bring inside the platform, sets up SPF, DKIM, DMARC, and the forwarders automatically, puts them behind dedicated US IPs, and exports the lot into a sequencer like Instantly or Smartlead. It composes nothing and sends nothing itself. Flat rate, no per-mailbox fee. If your job is running cold outbound at volume, it does that job cheaply.

These are two different purchases. Inframail is the layer your cold mail leaves from. Nitrosend is the platform your permissioned email runs on: campaigns, flows, segments, and transactional sending, with every capability an API endpoint and an MCP tool before it's a screen. Most companies buying one find they needed both, on separate domains. If what you want is more mailboxes, this page isn't going to argue you out of Inframail.

1. Leave the cold stack alone. The mailboxes, the throwaway domains, and the sequencer stay exactly where they are, and nothing in this migration touches them.
2. Authenticate your real domain in Nitrosend. DKIM and SPF go on the domain your company actually trades under, kept deliberately separate from the domains your cold mail is sent from.
3. Import the permissioned list, and only that list. nitro_import_contacts takes email, first and last name, and custom properties. Cold prospects don't belong in this import, and the separation is far easier to keep than to recover.
4. Move one message type first. Send a receipt or a password reset with nitro_send_message and watch it for a week before a campaign follows it. Then rebuild anything scheduled as a flow with nitro_compose_flow.
5. Decide what carries the permissioned reputation. BYO sending keys on Pro and above route mail through Amazon SES, Resend, Postmark, Mailgun, or SendGrid, on a domain and IP you already warmed. Inframail isn't one of them and isn't meant to be: its IPs are carrying cold traffic, which is the last reputation you'd want your receipts riding on.

• Unlimited contacts on every plan, including Free, so a list that grows without being mailed never moves the bill.
• Campaigns, flows, and segments in the same product as transactional sending, with the two streams kept deliverability-isolated.
• Permissioned email has somewhere to live, which is the half of the program a mailbox provider doesn't cover.
• MCP-first is an architecture, not an integration: every capability is an API endpoint and an MCP tool before it's a screen.
• The MCP covers campaigns, flows, contacts, templates, and segments, not a read-only slice of them.
• Deliverability, billing, tests, and approvals are MCP tools too, and they're the four that usually stop an automation dead.
• Transactional sends stay on the REST API, because a send that has to be fast shouldn't wait on a tool call.
• A clean REST API and a CLI alongside the MCP, so nobody is forced through an agent to get work done.
• BYO sending keys on Pro and above route mail through Amazon SES, Resend, Postmark, Mailgun, or SendGrid, on the domain and IP you already warmed.
• BYO keys make the platform decision reversible, where switching usually means changing sending reputation on the same day.
• A published price from 500,000 to over 4,000,000 emails a month, where most ladders go quote-only.

A cold email stack is three purchases, not one

A working outbound program is three separate things to buy, and only one of them is what most buyers think they're shopping for. There's the infrastructure layer, which is mailboxes, domains, and the IPs they leave from, and that's Inframail. There's the sequencer, which composes the messages, paces them out, and handles the replies. Then there's the platform the rest of your email runs on, the half that sends receipts, password resets, lifecycle mail, and campaigns somebody actually asked to receive.

Infrastructure, sequencer, and sending platform get sold as substitutes for each other. Transactional providers get pitched as Inframail alternatives without anyone mentioning they're a different category, and a reader who takes that at face value buys two layers out of three and finds the gap on the morning the first receipt has to go out.

The three-purchase framing tells you what to buy and nothing about who ends up operating it. Every layer in the stack was designed to be clicked through by a person, so the work settles wherever a human is the only thing that can drive the product. The question worth asking of each layer is what can operate it other than somebody logging in.

Keep the cold domains away from the rest of your email

The domains a cold program sends from are being spent. Complaints, bounces, and the occasional block are the running cost of outbound, and they land on the sending domain rather than on the tool that sent the message. The domain your receipts and password resets leave from can't absorb that, because a receipt in the spam folder is a support ticket and a reset in the spam folder is a locked-out customer.

Separating the domains doesn't separate the brand. A prospect who complains about your cold mail still associates it with your company, so the split protects deliverability rather than reputation, and it's worth being honest with yourself about which of the two you're solving for.

Inframail keeps the cold layer running, and Nitrosend runs the email that carries your company's name: campaigns, flows, segments, and transactional sending from the domain you actually trade under. Two layers normally means a second console and a second set of credentials, and the permissioned half asks for neither: you drive it from the agent session that's already open, so buying both doesn't mean running two dashboards. The free tier starts at 8,000 emails with unlimited contacts, so you can put one message type through it before anything else moves.

Does Nitrosend give me cold email inboxes like Inframail does?

No. Nitrosend is sender-side: it sends from a domain you authenticate, and it doesn't provision, host, or read mailboxes. If what you need is fifty Outlook inboxes on throwaway domains by Friday, Inframail is the answer for that job and we'd point you at it.

Can I run Inframail and Nitrosend at the same time?

Yes, and it's the arrangement we'd recommend. Cold outbound leaves the throwaway domains Inframail provisions, everything permissioned leaves the domain your company trades under, and the two sending reputations stay apart on purpose. Neither platform needs anything from the other for that to work.

Does Inframail work with Smartlead and Instantly?

Yes, and that's the clearest signal of which layer it sits at. Inframail provisions the mailboxes and exports them into a sequencer, and the sequencer does the composing, the pacing, and the reply handling. Instantly, Smartlead, Woodpecker, Saleshandy, ReachInbox, and Salesforge are all on its list.

What does Nitrosend do that Inframail has no equivalent for?

Campaigns, automation flows, segmentation, templates, and transactional sending, plus the agent surface over all of it: every capability is an API endpoint and an MCP tool before it's a screen. Inframail is infrastructure rather than a sending platform, so a team that needs any of that is buying a second product either way.