VS
Loops sends marketing and transactional email for SaaS teams. SuprSend is agentic, multi-channel orchestration for every message your product sends, run by teams and agents together.
Trusted infrastructure layer behind hundreds of platforms
Loops and SuprSend both send product, lifecycle and transactional messages from one tool. Loops does it on email, with a clean editor and pricing on subscribed contacts. SuprSend is agentic, multi-channel orchestration: engineering, product, growth and their agents run every kind of message, on every channel, from one system.
Email, SMS, WhatsApp, mobile push, web push, Slack, Teams, in-app inbox and webhooks run on one user profile, and transactional, product and marketing messages share the same workflows, preferences and logs. Loops sends email only, with no second channel to fall back to.
Your team works from the tools it already uses: the dashboard, Slack, the repo, Claude or ChatGPT. Agents create workflows, write templates, trigger sends and read the delivery log. Loops has no agent in its dashboard, and its MCP server and CLI stop short of delivery logs.
Each tenant has its own sending domain and provider, its own template versions, its own channel defaults and a per-tenant feed, nested five levels deep. Each user sets preferences per category, channel and digest schedule. Loops runs one sending domain per team, with mailing lists as its preferences.
A failed send moves to the next provider, bursts collapse into one digest, every workflow and template keeps versions with rollback, and test mode blocks real delivery outside production. Loops sends on its own infrastructure, and a running workflow must be paused before its emails can change.
A product manager changes a workflow in the dashboard. A developer commits the same workflow as a file and ships it through a pull request. A marketer asks Claude to build a list and send a campaign. All three work on the same workflows, templates and logs, so nobody waits on a ticket.
The built-in agent builds, edits and debugs notifications from a description; product and growth ship without a ticket.
Connect the MCP to Claude, ChatGPT or any client and operate templates, workflows, tenants and preferences.
CLI and API keep workflows versioned, diffable and reviewed in pull requests; coding agents make bulk changes.
One SuprSend customer runs its marketing email end to end from Claude Code, with nobody in the dashboard.
Loops is built in its dashboard, and it gives agents plenty to work with: a hosted MCP server for Claude, ChatGPT, Codex and VS Code, a CLI, skills for coding agents, and LMX markup for email content. Agents manage contacts, lists, events, campaigns, workflows and email content; delivery results reach you by webhook. Each Loops team is one live account with no staging.
One SDK, one event stream and one user record cover all nine channels, and adding a channel is a step in a workflow. A marketing team working in the SuprSend dashboard also runs the event-driven transactional messages, from the same workflows, lists and logs as its campaigns, with no second tool and no engineering ticket.
| If this is you | Choose |
|---|---|
| A SaaS team sends onboarding sequences, newsletters and receipts, all by email, on one bill based on contacts | Loops |
| Founders want a writing-first email editor with delivery and sender reputation handled for them | Loops |
| A large list is emailed often, and unlimited sends on a contact-based plan keep the bill flat | Loops |
| One product event has to reach the user by inbox, push, email or SMS, stopping once they respond | SuprSend |
| Each customer account needs its own domain, content and notification defaults | SuprSend |
| Users should choose, per category, which messages they get and on which channel | SuprSend |
| Ten updates in an hour should reach the user as one digest | SuprSend |
| A send that fails at the provider has to reach the user through another one | SuprSend |
| You want agents to build, send and manage your notifications from Claude, ChatGPT, Claude Code, Cursor or Slack | SuprSend |
| Marketing keeps Loops for newsletters and lifecycle email, and the product needs notifications Loops cannot send | Both |
| SuprSend | Loops | |
|---|---|---|
| Best when | Engineering, product and growth all send to users, on every channel and for every customer account | A SaaS team sends marketing, lifecycle and transactional email from one tool |
| Who uses it | Engineers, product, growth, and agents over MCP; unlimited seats | Founders, marketers, engineers, and agents over MCP; unlimited seats |
| Messages covered | Transactional, product and customer engagement, on nine channels | Marketing, lifecycle and transactional email |
| Built and changed from | Dashboard agent, your own agent over MCP, CLI and API | Dashboard, hosted MCP, CLI, API and LMX markup |
| Channels | Email, SMS, WhatsApp, mobile push, web push, Slack, Teams, in-app, webhook | |
| Email delivery | Your providers, with fallback between them | Loops sends it; SMTP relay for your own app |
| Multi-tenancy | Nested tenants with own domain, provider, template version and defaults | One sending domain per team; a second domain is a second team |
| User data | Any number of properties, any JSON value | Typed properties: string, number, boolean, date |
| Preferences | Per category across channels: channels, digest schedule, conditions; tenant defaults | Mailing lists in a preference centre, for marketing email |
| Workflow steps | Multi-channel send, branch, digest, failover, webhook, allowed hours | Email, timer, audience filter, branch, experiment |
| Test and staging | Development, staging, production; test mode blocks delivery | One live team; test with @example.com addresses |
| In-app inbox | Web, React Native, Flutter, iOS, Android; headless | No in-app channel |
| Logs | Per message with content and block reason; 30 days Free, 90 paid | Per-email metrics and contact timeline; 30 days of webhook history |
| Agents | Agent in dashboard and Slack; MCP over the whole engine, logs included | Hosted MCP, CLI and skills; no agent in the dashboard |
| Hosting | SuprSend cloud on every plan; your VPC, on-prem or BYOC on Enterprise | Loops cloud |
| Pricing model | Per notification per channel; 10,000 free; Essentials $100 a month | Per subscribed contact, unlimited sends; 1,000 free; paid from $49 a month |
| Implementation | Days: SDK or API call, providers connected in the dashboard | Days: DNS records, SDK or API call, first send |
| Compliance | SOC 2 Type II, GDPR, HIPAA BAA on Enterprise | SOC 2, DPA, EU-US Data Privacy Framework |
| Reviews | G2 4.8, 129 reviews | Product Hunt 4.9, 132 reviews |
LoopsLoops is an email platform for software companies. Marketing campaigns, event-triggered workflows and transactional email share one editor, one audience and one sending domain, and Loops handles delivery and sender reputation itself.
It fits a SaaS team whose messages are all email. Pricing follows subscribed contacts with unlimited sends, every feature is on every plan, and agents work in it through a hosted MCP server and a CLI.
SuprSendSuprSend is agentic, multi-channel orchestration for every message a product sends. Engineering, product, growth and their agents build workflows, templates, lists and broadcasts on nine channels, with one user profile and one set of preferences.
It fits a product that talks to users in more than one place, or serves customer accounts that each need their own setup. Teams that keep Loops for newsletters use SuprSend for the inbox, push and SMS around them.
LoopsFounders and marketers write campaigns and workflows in the dashboard editor, and target them with segments on contact properties and mailing lists. Engineers send events and transactional email through the API, an SDK, the CLI or SMTP, and receive delivery events at one webhook endpoint.
Agents connect to the hosted MCP server or use the CLI and skills to manage contacts, lists, campaigns, workflows and email content, and send transactional email.
SuprSendEngineers integrate once through the API, a backend SDK in Python, Node, Java or Go, the CLI and MCP, and keep workflows and templates in the repo. Product and growth build workflows, lists, content and broadcasts in the dashboard, or have the built-in agent build them, with versions to roll back and a test mode.
Agents connect over MCP from Claude, ChatGPT, Claude Code or Cursor and create users, tenants and objects, set preferences, write templates, trigger a notification, run a broadcast and read the log.
From both dashboards, documentation sites, changelogs and pricing pages, September 2026. Plan names mark the lowest plan that includes a feature; “every plan” on Loops includes Free.
Both can now be run from outside the dashboard: Loops has a hosted MCP server, a CLI and LMX markup for email content. SuprSend adds environments, and workflows and templates kept as files that are pushed, pulled and promoted like code.
| Capability | SuprSend | Loops |
|---|---|---|
| Visual workflow builder | YES | YES |
| Workflows and templates by API | YES | YESWorkflows, nodes and email content |
| CLI | Pushes and pulls workflows, templates, schemas, events, categories and translations | Creates and edits contacts, campaigns, workflows, components, themes and transactional email |
| Assets kept as files in your repo | YESPulled and pushed by the CLI | PARTIALEmail content as LMX; workflows live in the account |
| Promote staging to production | YESFrom the CLI or CI | NOOne live team per account |
| Change many emails at once | YESOne CLI command or one prompt | YESA component or theme change reaches every email that uses it |
| Agent in the dashboard | YESBuilds workflows and drafts copy from a description; also in Slack | NO |
| Headless UI components | YESInbox, preference centre and template editor | NOHosted preference centre and form embeds |
Both put marketing, lifecycle and transactional messages in one product with free seats. SuprSend does it on nine channels with role-based access on Enterprise; Loops does it on email with Owner and member roles.
| Capability | SuprSend | Loops |
|---|---|---|
| Who builds workflows | Engineers, product and growth, in the dashboard or by CLI | Founders, marketers and engineers, in the dashboard, API or CLI |
| Seats | Unlimited on every plan | Unlimited on every plan |
| Transactional messages | YESOn every channel | YESEmail, by API or SMTP |
| Product and lifecycle messages | YESOn every channel | YESEmail workflows on events and property changes |
| Marketing campaigns | YESOn every channel | YESEmail |
| One preference model across all three | YES | PARTIALTransactional email ignores subscription and list status |
| Roles | Role-based access on Enterprise | Owner and member |
SuprSend models users with any JSON properties, objects and nested tenants. Loops models contacts with typed properties in one audience per team, and keeps transactional-only recipients out of it.
| Capability | SuprSend | Loops |
|---|---|---|
| User properties | Any number, any JSON value, nested objects and arrays | String, number, boolean or date, created one at a time |
| Change a property later | YESNo schema to change | NOCreate a new property instead |
| Non-user recipients | YESObjects with their own channels and subscribers; Business | NOContacts only |
| Tenants | YESNested five levels; Business add-on or Enterprise | NOA separate team per domain, with no shared data |
| Per-tenant sending domain and provider | YES | NOOne sending domain per team |
| Per-tenant template version | YES | NO |
| Tenant-admin preference defaults | YES | NO |
| Recipients outside the stored audience | YESAny user by ID; stored users are free | YESTransactional sends to any address, not billed |
Both run campaigns to a list or segment from the dashboard. Loops adds goals, experiments and hosted forms; SuprSend adds warehouse lists, CDP sync, timezone sends and every channel, with campaigns running through the same workflow engine as transactional messages.
| Capability | SuprSend | Loops |
|---|---|---|
| How a list is built | Rules on properties and events, scheduled warehouse SQL, CSV, API, Segment, Mixpanel, Amplitude | Filters and saved segments on contact properties, mailing lists, CSV, API, Segment, RudderStack, Fivetran |
| Lists that refresh themselves | YES, BUTEnterprise, or an add-on on Essentials and Business | YESSaved segments |
| Broadcast channels | Nine, several in one send | |
| Scheduling | One-time, scheduled or recurring, in the recipient’s timezone | Send now or at a scheduled time |
| Campaign runs through the workflow engine | YESBatches, routes, falls over and respects preferences | NOSends once to the chosen audience |
| Signup forms | NO | YESHosted and custom forms, double opt-in |
| Experiments and conversion goals | NO | YESSplit tests in workflows; goals per campaign |
| Campaign analytics | Delivered, seen, clicked, unsubscribed per broadcast, template, category and tenant | Opens, clicks, unsubscribes, bounces and spam reports per campaign |
SuprSend sends on nine channels through providers you bring, with failover between them. Loops is the email sender itself and has no second channel.
| Capability | SuprSend | Loops |
|---|---|---|
| YESThrough SendGrid, SES, Postmark, Mailgun, SMTP and more | YESLoops sends it | |
| SMS and WhatsApp | YES | NO |
| Mobile and web push | YES | NO |
| Slack and Microsoft Teams | YES | NO |
| In-app inbox | YES | NO |
| Webhook as a channel | YES | NO |
| Provider failover | YESOrdered list, timer, delivery-confirmation stop; Essentials | NOOne sender |
| SMTP relay for your own app | NO | YES |
Loops workflows are email sequences with timers, audience filters, branches and experiments. SuprSend adds cross-channel steps, digest, provider failover, cancellation, a webhook step and allowed hours.
| Capability | SuprSend | Loops |
|---|---|---|
| Triggers | Events and API calls; broadcasts to lists | Contact added, contact updated, added to a list, event received |
| Steps | Multi-channel send, delay, branch, batch, digest, wait for event, webhook, sub-workflow, data transform | Email, timer, audience filter, branch, experiment |
| Several channels in one step | YES | NOEmail only |
| Batch and digest | YESUser-chosen time, batch until due date, skip if too few; Business | PARTIALYour app collects the items and sends one transactional email |
| Delivery timing | Scheduled send; allowed hours in the user’s timezone; throttling | Fixed timers between steps |
| Payload validation | YESJSON schema per event | PARTIALRequired data variables on transactional sends |
| Edit a live workflow | YESVersions with rollback | PARTIALPause, edit, resume; new contacts queue for up to 24 hours |
| Cancel a run | YESOne run, a recipient or a whole workflow | PARTIALPause or stop the whole workflow |
| Test mode | YESBlocks real delivery outside production | PARTIALSends to @example.com and @test.com are dropped |
Loops has the stronger email editor, with writing mode, components and a pre-send check. SuprSend has editors for nine channels, variants by tenant and language, translation files and an editor you can embed.
| Capability | SuprSend | Loops |
|---|---|---|
| Email editor | Drag-and-drop and HTML with Handlebars | Block editor with writing mode, themes and components; MJML upload; no raw HTML |
| Other channels | Editors for SMS, WhatsApp, push, Slack, Teams and in-app | No other channels |
| Checks before sending | Preview and test send on every channel | Guardian errors and warnings, in the editor and by API |
| Translations | YESTranslation files per language, pushed with the templates; Business | YES, BUTOne-click translation copies a workflow branch per language |
| Variants | YESBy tenant, user, event data or language | NO |
| Version history and rollback | YES | PARTIALDraft and published versions of a transactional email |
| Embeddable template editor | YESReact SDK inside your product | NO |
SuprSend resolves preferences per category across channels and tenants. Loops runs a mailing-list preference centre for marketing email, and transactional email ignores it by design.
| Capability | SuprSend | Loops |
|---|---|---|
| Model | Per category: channels, digest schedule, condition rules | Subscribed status plus public and private mailing lists |
| Covers | Every channel and every kind of message | Campaigns and workflow emails |
| Tenant-admin defaults | YES | NO |
| Preference centre | YESDrop-in, headless or hosted page; Business | YESHosted, branded with your icon |
| User-chosen digest schedule | YES | NO |
| Resubscribe after an opt-out | YESBy the user from the preference centre | PARTIALAudience by API only; mailing lists never |
SuprSend has an inbox on every plan, driven by the same workflow as the email. Loops has no in-app channel.
| Capability | SuprSend | Loops |
|---|---|---|
| Drop-in web inbox | YESReact, Angular, Vue, JS | NO |
| Mobile SDKs | YESReact Native, Flutter, iOS, Android | NO |
| Headless | YES | NO |
| Toasts, tabs, pin, snooze, archive | YES | NO |
| Per-tenant feed | YES | NO |
| Authentication | Expiring JWT, refreshed by the SDK | No in-app channel |
Loops reports what happened to each email per campaign, workflow and contact. SuprSend logs why a message did not go, per step and per channel, and syncs it to your warehouse and monitoring tools.
| Capability | SuprSend | Loops |
|---|---|---|
| Per-message log | YESRendered content, provider error, block reason | PARTIALContact activity timeline and per-email metrics |
| Block reasons named | YESOpt-out, no channel, template error | NO |
| Opens and clicks on transactional email | YESWhere the provider reports them | NONot tracked on transactional email |
| Retention | 30 days Free, 90 days paid, custom on Enterprise | Webhook history 30 days |
| Webhook events | YESAll plans | YESOne endpoint; retries over about 28 hours |
| Log export | S3 Parquet every five minutes; CSV to 50M rows | Contact CSV export; delivery events by webhook |
| Monitoring tools | YESDatadog, New Relic, OpenTelemetry; Enterprise | NO |
Loops has more backend SDK languages and an SMTP relay. SuprSend has three environments, promotion, type generation and frontend SDKs for the inbox.
| Capability | SuprSend | Loops |
|---|---|---|
| Environments | Development, staging, production; all plans | One live team; a second team for testing |
| Backend SDKs | Python, Node, Java, Go | Go, JavaScript, PHP, Ruby, Nuxt; community Python, Java, .NET, Elixir |
| Frontend SDKs | JS, React, React Native, Flutter, iOS, Android | Form embeds only |
| OpenAPI spec | YES | YES |
| Typed payloads | YESTypeScript types from event schemas | PARTIALTypes in the JavaScript SDK |
| Rate limits published | NOFair-use limit, no number | YES1,000 emails a second on paid, 10 on Free |
| SMTP | NO | YESRelay for Rails, Django, Laravel and Supabase auth |
Both expose the product to agents over MCP, a CLI and skills. SuprSend adds an agent in the dashboard and Slack, and any agent can read the delivery log and diagnose a send.
| Capability | SuprSend | Loops |
|---|---|---|
| Agent in the dashboard or Slack | YESBuilds workflows, drafts copy, traces failed sends | NO |
| MCP server | YESLocal, through the CLI | YESHosted, with OAuth sign-in |
| What the MCP reaches | Users, tenants, objects, preferences, workflows, templates, broadcasts, logs | Contacts, lists, events, transactional email, campaigns, workflows, email content |
| Read the delivery log from an agent | YES | NODelivery events go to a webhook |
| Skills for coding agents | YESClaude Code, Cursor, Windsurf | YESClaude Code, Codex, Cursor |
| Agent SDK for your own agents | YESOpenAI, LangChain, Vercel AI | NOCall the API |
| Campaign created and scheduled by an agent | YES | YES |
Both hold SOC 2. SuprSend adds HIPAA, SSO, an audit trail and a choice of hosting on Enterprise; Loops publishes a DPA and takes part in the EU-US Data Privacy Framework.
| Capability | SuprSend | Loops |
|---|---|---|
| Certifications | SOC 2 Type II, GDPR, HIPAA; ISO 27001 and CPRA in progress | SOC 2; DPA; EU-US Data Privacy Framework |
| HIPAA BAA | YESEnterprise | NO |
| SAML SSO | YESEnterprise | NO |
| Audit trail | YESEnterprise | NO |
| Hosting | SuprSend cloud on every plan; your VPC, on-prem or BYOC on Enterprise, full product, supported | Loops cloud |
| Support | Slack community; email and chat on paid; phone and named CSM on Enterprise | Email and in-app support; onboarding call |
| Uptime | 99.9%; SLA on Enterprise | Status page; SLA not published |
Loops bills on subscribed contacts with unlimited sends on paid plans; transactional-only recipients and unsubscribed contacts are free. SuprSend bills per notification per channel, stores users free, counts a digest as one, and your email provider bills its own sends. 5,000 users who each get a weekly email and an in-app message make about 43,000 notifications a month, inside SuprSend Essentials at $100 plus the provider’s email bill; on Loops the same 5,000 contacts sit in the first paid tier, from $49 a month, with no in-app message. Compare on your own contact count, channels and event-to-notification ratio.
| Capability | SuprSend | Loops |
|---|---|---|
| Billing unit | Notification per user per channel; a digest counts as one; opt-out blocks not billed | Subscribed contact at renewal; transactional-only and unsubscribed contacts not counted |
| Free | 10,000 notifications a month; all channels; unlimited members | 1,000 subscribed contacts; 4,000 sends in any rolling 30 days; Loops footer |
| Entry paid | Essentials $100 a month; 50,000 notifications; $2 per extra 1,000 | From $49 a month; unlimited sends; 1,000 emails a second |
| Next tier | Business $250 a month; adds digest, preferences, objects | Price rises with the subscribed contact count on one plan |
| Feature gates | Fallback at Essentials; digest, preferences, objects at Business; tenants as a Business add-on or Enterprise; RBAC and SSO at Enterprise | None; every feature on every plan |
| Seats | Unlimited | Unlimited |
| Email delivery cost | Billed by your email provider | Included |
| Time to first send | Same day: free plan, SDK or API call | Same day: free plan, DNS records, SDK or API call |
Two shapes of move are common. Some teams move everything. More often, newsletters and lifecycle campaigns stay in Loops, and product notifications, transactional messages and every non-email channel move to SuprSend.
| Loops | SuprSend | Moves how |
|---|---|---|
| Contact | User | Users API, backend SDK, or Segment |
| Contact properties | User properties | Same keys; values can become any JSON |
| Mailing list | List and a preference category | Members to a list; the opt-in becomes a category |
| Segment or filter | List from rules | Rebuild the rules on properties and events |
| Event | Event | Point the same event calls at SuprSend |
| Workflow | Workflow | Rebuilt; no export maps across |
| Transactional email | Workflow with an email template | Recreate; data variables become payload fields |
| Campaign | Broadcast | Recreate; send to a list on any channel |
| Components and themes | Templates | Recreate in the email editor |
| Sending domain | Email provider | Connect a provider and verify the domain there |
| Webhook endpoint | Webhooks and log sync | Re-point your endpoint |
| Metrics and contact timeline | Logs | Export contacts first; history stays in Loops |
Inventory every Loops workflow, transactional email, campaign, mailing list and contact property, and decide which mailing lists become preference categories.
Stand up SuprSend development and staging. Connect your email provider with a fallback order, and the push, SMS and chat providers you need.
Import users and lists; carry each contact’s subscribed status and list opt-outs into preferences.
Rebuild the critical flows first: verification codes, password resets, receipts and billing alerts. Test them in test mode, then pull them into your repo.
Run both in parallel on those flows for a week, and ship the inbox behind a flag.
Move the remaining workflows, cut over, and keep a contact export from Loops for reference.
Enterprise customers get migration support and a scoped plan; on other plans the Slack community and docs are the path.
SuprSendSuprSend is better when a product sends on more than one channel, needs preferences that hold across channels, or serves customer accounts that each need their own setup. Engineering, product, growth and agents run transactional, product and marketing messages from one system.
LoopsLoops is better when email is the only channel and you want sending, deliverability and a writing-first editor in one tool, on one price based on subscribed contacts.
Yes. Many teams keep newsletters and lifecycle email in Loops and send the inbox, push, SMS and Slack messages from SuprSend, triggered by the same product events. The trade-off is two systems: two user records, two sets of preferences, and an opt-out in one that the other does not see.
SuprSendSuprSend tenants send through the customer’s own email domain and provider, carry their own template version, and set the defaults, mandatory channels and visible categories their users start from, nested five levels deep; on Enterprise or as a Business add-on.
LoopsLoops has one audience and one sending domain per team. A second domain means a second team, with its own settings and no shared data.
SuprSendSuprSend keeps a version history for every workflow and template with rollback, and its test mode in development and staging blocks real delivery.
LoopsLoops keeps a draft and a published version of each transactional email, and a running workflow is paused to edit. Tests go to @example.com and @test.com addresses, which Loops accepts and never delivers.
SuprSend runs as SuprSend cloud on every plan, and on Enterprise the full product runs in your VPC, on-prem or bring-your-own-cloud with support behind it. Loops runs in its own cloud.
The units differ. Loops bills per subscribed contact with unlimited sends on paid plans, so a large list emailed often favours Loops. SuprSend bills per notification per channel and counts a digest as one, so a small audience reached on several channels favours SuprSend.
Contacts move through the users API, a backend SDK or Segment, and mailing lists become lists and preference categories. Workflows and email content are rebuilt, then kept in your repo through the CLI. Most teams run both in parallel on the critical flows for a week before cutting over.
Join thousands of product & engineering teams using SuprSend to build and ship better notifications—faster.
