Choose Brew if you want a fully agentic setup, where your AI agent drives lifecycle marketing to engage and retain customers. Brew designs every email from your brand and runs your automations agentically.
Choose Iterable if your journeys run across email, SMS, push, in-app, WhatsApp and RCS with warehouse sync, and your team has time to design each email.
THE BROWSERCOMPANY
Brew is fully agentic: your agent designs on-brand emails, sends them and runs your automations. In Iterable, Nova Agent writes the copy, not the design.
 Brew | Iterable | |
|---|---|---|
| Key differences | ||
| Fully agentic | Brew: Yes. Your agent designs, sends and runs automations end to end | Iterable: Partly. Partly: Nova Agent drafts copy, templates and journeys in the app |
| Designs finished, on-brand emails | Brew: Yes. Layout, copy and images from your brand, ready to send | Iterable: No. Nova Agent writes copy and Handlebars, not the design |
| Your agent takes it live | Brew: Yes. Sends, schedules and runs automations; OAuth and org-scoped MCP require confirmation, brand API keys do not | Iterable: Partly. Partly: Its MCP server sends only after you turn on writes |
| Remembers your brand for every email | Brew: Yes. Brand files your agent reads every time | Iterable: Partly. Partly: Creative Library stores images, PDFs and videos |
| MCP server for AI agents | Brew: Yes. Every Brew tool, in Claude, ChatGPT, Cursor and Grok | Iterable: Partly. Partly: Beta, for desktop apps; read-only by default |
| Prices listed publicly | Brew: Yes. Growth $99/month, Pro $249/month | Iterable: No. On request |
| Brew | Iterable | |
|---|---|---|
| Creating emails | ||
| Visual editor | Brew: Yes. Infinite canvas, edit by hand or in chat | Iterable: Yes. Drag-and-drop, WYSIWYG and side-by-side editors |
| Bring the emails you already have | Brew: Yes. HTML, MJML, React Email, Figma or a forwarded email | Iterable: Yes. Your own HTML, imported in one step |
| Automation and data | ||
| Event-triggered automations | Brew: Yes. Stripe, Shopify, Clerk, Supabase or your own events | Iterable: Yes. Journeys start on events, a schedule or the API |
| Builds an automation from a description | Brew: Yes. Emails, waits and branches together | Iterable: Yes. Journey Assist builds the tiles from a prompt |
| Data pipelines and warehouse sync | Brew: No. API, SDK and integrations | Iterable: Yes. Smart Ingest from your warehouse |
| Best send time per contact | Brew: Yes. Intelligent Send | Iterable: Yes. Send Time Decisioning |
| A/B testing | Brew: No. Not built in | Iterable: Yes. Experiments on any part of a campaign |
| Channels | ||
| Email from your own domain | Brew: Yes. Marketing and transactional | Iterable: Yes. Blast and triggered campaigns |
| SMS, push and in-app | Brew: No. Email only | Iterable: Yes. Plus web push and embedded messages |
| WhatsApp and RCS | Brew: No. Email only | Iterable: Yes. Both, next to SMS |
| Agents and developers | ||
| API | Brew: Yes. REST API, typed SDK and CLI | Iterable: Yes. API and mobile SDKs |
| Pricing | ||
| Billed on | Brew: Emails sent and AI credits | Iterable: A contract; usage covers messages, users and events |
| Getting started | Brew: Free trial with 500 AI credits and 1,000 sends | Iterable: A demo and pricing estimate from sales |
| First paid plan | Brew: Growth, $99/month: 10,000 AI credits and 50,000 sends | Iterable: Not listed; price on request |
| Next plan | Brew: Pro, $249/month: 25,000 AI credits and 200,000 sends | Iterable: Not listed; limits set in your contract |
| Security and compliance | ||
| SOC 2 and ISO 27001 | Brew: No. Not yet; security review and DPA on request | Iterable: Yes. Certified |
| HIPAA | Brew: No. Not supported | Iterable: Yes. Listed in its Trust Center |
Connect Claude, ChatGPT, Cursor or Grok over MCP and your agent gets every Brew tool. It designs emails from your brand, builds audiences, runs automations and schedules sends. OAuth and organization-scoped MCP connections ask you to confirm live sends and launches. Brand-scoped API keys can execute permitted calls without the MCP confirmation step.
Paste your website and Brew writes your brand into two files your agent reads for every email. Describe the email and it appears on the canvas, ready to edit by hand or in chat.
They had me at Lovable for email. 10/10 experience.
MiloRiff.aiHaving an AI assistant built into the platform has made creating emails so much faster, easier, and, honestly, a really enjoyable experience.
Alice MullinsMarketing Manager, RedSeedA great rethinking of everything about email. Love it so far.
Shan ZhongGrowth, NeticVery impressed with what y’all have built and can’t wait to use Brew.
Addie LevinskyOps & Strategy, The Browser CompanyI didn’t need to cold start it with context. I gave it a link and it gathered everything it needed to get me started. I liked its taste in design.
Nischal NaikCo-founder, ConstructKeep Iterable sending until Brew passes your tests. We’ll do the move with you on a call if you like.
In Iterable, open each list, choose Save As, then Export As CSV File, and pick the fields to include. Include users who unsubscribed and their subscription status. Before importing, prepare a Subscribed column: true for opted-in contacts, false for unsubscribed, cleaned or suppressed contacts. Invert any Unsubscribed true/false flag first. Map the column to Subscribed and review the opt-out preview; new contacts default to subscribed if this value is missing.
Most teams have Brew redesign their emails from their brand, which is faster and looks better. You can also choose Export html on an Iterable template and paste it in, or forward a sent email to hello@email.brew.new; imports are free.
Connect Stripe, Shopify, Clerk or Supabase, or send your own events over the API, then describe each journey. Brew builds the emails, waits and branches, usually simpler than the original.
Connect and verify your sending domain, then review its health and inbox placement. For a new domain, select Gradual send to ramp the campaign in configurable batches before a large send. Gradual send is off by default; connecting a domain does not automatically warm it up.
We're here to help! Feel free to schedule a call.
Can't find what you're looking for? Contact us at +1-(332)-203-2145 or support@brew.new.
Yes, if email is your main channel and you want an agent to run it. Brew designs finished, on-brand emails from your brand, sends them and runs your automations from your AI agent, with unlimited contacts on every plan. Brew is email only, so SMS, push and in-app stay in another tool.
Yes. Connect Iterable in Brew with a server-side API key and ship any email into Iterable as a template, ready for your campaigns and journeys. You keep your users, SMS, push and in-app messages in Iterable and design the emails in Brew.
In Brew, your agent designs the finished email from brand files it reads every time, builds audiences, runs automations and sends. Iterable’s Nova Agent works inside Iterable: it writes copy and Handlebars logic, helps create templates, campaigns and experiments, and asks you to confirm before it saves or sends. Iterable’s MCP server is in beta, runs in desktop apps such as Claude Desktop and Cursor, and is read-only until you turn on writes and sends.
OAuth and organization-scoped MCP connections ask you to confirm live sends and launches. Brand-scoped API keys can execute permitted calls without the MCP confirmation step.
Iterable’s AI does not design the email. Nova Agent writes copy and Handlebars logic and drafts templates and journeys, and your team builds the design in Iterable’s editors. Teams that move to Brew tell us these drafts rarely look like their brand, so someone still redesigns them. Brew designs the whole email, layout, copy and images, from brand files your agent reads every time, so it goes out on-brand.
It depends on your audience and how much you send. Iterable lists no prices: usage is set in your contract and you get an estimate from sales. Brew bills on sends and AI credits with unlimited contacts, and its prices are public. Start with the free trial and compare at your own numbers.
No. Brew is email only: marketing and transactional email from your own domain. Teams that need SMS, push, WhatsApp or in-app keep Iterable for those, and can design their emails in Brew and ship them into Iterable.
Not yet. We complete security reviews and sign a DPA on request, and our privacy policy, DPA, GDPR page and subprocessor list are public at docs.brew.new/legal.
Your first on-brand email is ready the day you start the trial. The rest depends on how many journeys you run: contacts and unsubscribes import from Iterable’s CSV export, most teams have Brew redesign their emails rather than import them, and each journey is rebuilt by describing it. Keep Iterable sending until Brew passes your tests.
Before importing, prepare a Subscribed column: true for opted-in contacts, false for unsubscribed, cleaned or suppressed contacts. Invert any Unsubscribed true/false flag first. Map the column to Subscribed and review the opt-out preview; new contacts default to subscribed if this value is missing.
Yes. We get on a call to import your contacts and unsubscribe list, bring over or redesign your emails, rebuild your flows and connect your sending domain.
Brew publishes this comparison. Brew Team reviewed the linked first-party documentation. This is a documentation review, not a claim of hands-on testing of every product. Pricing and plan limits can change.
Work at Iterable? If anything on this page is wrong or out of date, email support@brew.new and we will correct it. We want to compete on the product, not on a mistaken comparison.
Updated October 2026
