Loops Review 2026: Built for SaaS, Priced by Contact, Relay on a Leash

TL;DR: should you use Loops in 2026?

Loops sells one idea, and it is a good one: your marketing email, your lifecycle sequences and your password resets should be one product, one API and one contact record. Every other platform in this comparison makes you run two things and reconcile them. Loops does not, and for a software company with a product to ship that is worth more than any feature on a comparison grid.

The pricing follows from the idea. You pay for contacts, not for emails, and on paid plans the sends are unlimited with transactional included at no extra charge. Free is 1,000 subscribed contacts and 4,000 sends in any rolling 30 days, forever, with a Loops footer. That inverts the economics of this entire category, and whether it is cheap or expensive depends entirely on the shape of your list.

What you give up is the thing this site is named after, though not in the shape a feature grid records it. Loops does publish an SMTP relay at smtp.loops.so on port 587, and it still will not do what you want a relay to do: every message has to name a transactional template you already built inside Loops, and the body you hand it is a JSON payload rather than the email itself. So it is not a drop-in replacement for a relay, it will not accept a connection from your WordPress plugin or your printer or your legacy app, and there is no dedicated IP at any price either.

The context you need before evaluating Loops in 2026

Loops came out of Y Combinator’s Winter 2022 batch, founded by Chris Frantz and Adam Kaczmarek, who had just sold their previous company Snazzy to Unbounce. It raised $3.2M in early-stage funding led by Craft Ventures, and it is still independent, still around 10 people, and based in Washington DC. Four years in, that is a small company running email infrastructure for other people’s products, and the size is a fact you should price in rather than ignore.

The product thesis is worth stating properly because it explains every decision that follows. Frantz put it bluntly when the company raised: Email is still kind of awful. Your devs know it. Your product team knows it. Your marketers really know it. The awfulness he means is structural. A typical SaaS company sends marketing email from one vendor, lifecycle email from a second, and transactional email from a third, then spends engineering time keeping three contact records in sync and cannot answer the question what has this user actually received from us without joining three dashboards.

Loops collapses that into one. One audience, one contact record, one API key, three send types (campaigns, workflows, transactional) that all read the same contact properties. It is not a novel idea in the abstract. It is unusual in being the whole product rather than a feature bolted onto a marketing suite.

The price model is the second half of the thesis. Charging per contact with unlimited sends is how a CRM prices, not how postage prices, and it is the opposite of every relay on this site. Postmark, SocketLabs, Amazon SES and turboSMTP all meter the message. Loops meters the person. For a product company sending twenty lifecycle emails a month to each of 3,000 users, that is a very large difference in the right direction. For a newsletter with 80,000 subscribers and one send a month, it is a very large difference in the wrong one.

Snapshot

What Loops does well

Three kinds of email, one contact record, one API key

Loops sends campaigns (a one-off to an audience or segment), workflows (event-triggered sequences) and transactional messages (password resets, receipts), and all three read the same contact properties from the same audience. The compliance behaviour differs where it should: campaigns and workflows carry unsubscribe information and track opens and clicks, transactional messages do neither, and unsubscribed contacts still receive transactional mail, which is the correct and surprisingly often mishandled rule.

The value here is not a feature, it is a deletion. You stop running a marketing tool beside a relay, you stop writing the sync between them, and you stop being unable to answer what a given user has received. Customer.io does this too and costs considerably more. Brevo does it and is a much heavier product. For a ten-person software company, Loops is the version of this idea that fits in an afternoon.

Priced per contact, with the sends thrown in

On paid plans Loops does not charge for sends at all, and transactional email is included at no additional charge. You are buying a contact count and the messages are free inside it. Nothing else in this comparison prices that way.

Work an example. A SaaS product with 4,000 users sending each of them roughly twenty lifecycle and product emails a month is 80,000 sends. On a metered relay that is a real line item every month and it grows every time you add a sequence. On Loops it is the $49 bracket, and adding a twenty-first email costs nothing. That changes how a team behaves: nobody has to justify a new onboarding email to finance.

A free tier that does not expire, on a product that is not crippled

1,000 subscribed contacts and 4,000 sends in any rolling 30 day window, permanently, with all features available and a Powered by Loops footer as the only restriction. Unsubscribed contacts do not count against the limit, which is a small honesty that several larger platforms do not extend.

It is worth noting what that is not. It is not a trial that converts, like turboSMTP’s six month free plan, and it is not absent entirely, like SocketLabs. A real product on a real free tier is how a developer evaluates anything in 2026, and Loops understood that.

An API that behaves like someone has used an API before

Bearer tokens generated from settings, a documented rate limit of 10 requests per second per team with x-ratelimit-limit and x-ratelimit-remaining headers and a proper 429, a published OpenAPI specification you can import into Postman, and official SDKs for Go, JavaScript and TypeScript, PHP and Ruby plus a Nuxt module.

Two details raise this above competent. The send rate is 1,000 emails per second on paid plans and excess is queued rather than rejected, so a launch spike does not become an incident. And the rate limits are published as numbers rather than described as reasonable, which is the difference between an API you can design against and one you discover in production.

Authentication set up properly, including BIMI

Loops requires a custom sending domain and documents four DNS records: SPF placed at envelope.yourdomain so it cannot collide with the SPF on your root domain, DKIM, an MX record, and DMARC with a policy you choose. BIMI is supported. DKIM signing is active from the first send rather than after a verification step you forget to complete.

Putting the SPF record on a subdomain to avoid collision is the kind of decision that only comes from having watched customers break their root domain, and it is documented rather than left as an exercise. This is a better authentication story than most platforms twenty times the size.

Where Loops falls short

The SMTP relay will not accept an email you wrote yourself

This is the first thing to check and the reason many readers of this site can stop here. Loops does run a relay: smtp.loops.so, port 587 with STARTTLS, the literal username loops, an API key as the password, and official guides for Django, Laravel, Rails and Supabase. What it will not take is an email. The documentation is explicit that every email sent using Loops SMTP service requires a transactional email to be set up in your Loops account, and the Django guide states that the body needs to be an API-like payload: a stringified JSON object carrying transactionalId, email and dataVariables. Your subject line and your HTML are ignored, because the template in the dashboard supplies both.

For anyone who cannot change what their sender puts on the wire, the consequences are the same as if the relay did not exist. A WordPress plugin that expects SMTP settings sends a real message, not a payload, so it cannot use Loops. A legacy application that speaks SMTP and nothing else cannot use Loops. A device, a scanner, a monitoring appliance, an off-the-shelf tool with an outgoing mail server field: none of them can use Loops. The relay is a transport for code you control, carrying mail whose content already lives in Loops. Migrating from a relay is still not a settings change, it is an integration project.

No dedicated IP at any tier, and the documentation does not discuss IPs at all

The deliverability documentation covers SPF, DKIM, DMARC and BIMI thoroughly and contains no discussion of dedicated IPs, IP pools or sending infrastructure. There is no dedicated IP option on any published plan and no way to ask for one that we could find.

For most Loops customers that is the right trade. A shared pool managed by the vendor beats a badly warmed dedicated IP, and at 4,000 to 80,000 sends a month you should not want your own IP. But it is a hard ceiling. If you reach the volume where reputation isolation becomes the correct answer, or if a compliance review requires you to name your sending IPs, Loops has no answer and you are migrating. SocketLabs bundles one at $89.95 and Postmark sells one; this is the axis on which they beat Loops outright.

The pricing page does not publish a price

Loops’ pricing page renders its paid tiers through a JavaScript slider. The result is that the numbers are not in the page source, not in search results, not quotable, and not readable by anything that does not execute the page, which now includes a meaningful share of the software that answers questions about products.

What we can report is second-hand and we label it as such. Two independent pricing trackers read the live page and agree on the entry point at $49 a month, with a ladder of $99 at 10,000 contacts, $199 at 25,000, $249 at 50,000 and $399 at 100,000, checked in the first half of 2026. They differ slightly on where the first bracket ends. Move the slider yourself before you budget.

Contact pricing is brilliant or brutal depending on the shape of your list

The model that makes Loops cheap for a SaaS product makes it expensive for a publisher. A newsletter with 50,000 subscribers and four sends a month is 200,000 emails, which costs about $249 here. EmailOctopus and MailerLite exist precisely to be cheaper than that, and a metered relay would be cheaper still if you can build the sending yourself.

The rule is simple enough to apply in your head. Divide your monthly sends by your contact count. Above roughly fifteen or twenty emails per contact per month, Loops wins on price and keeps winning. Below about five, you are paying for people you rarely email, and the model is working against you.

There is almost no independent review evidence, four years in

This is unusual enough to be worth its own section. Loops has no Trustpilot listing. It has no Capterra listing (the Capterra results for the name are other companies). Its G2 product page carries 2 reviews from June 2024, one of them incentivised, and the review text describes task organisation and surveys rather than anything to do with email, so we do not publish a G2 score for this product.

The only real corpus is Product Hunt: 4.9 / 5 on 134 reviews, plus a runner-up Golden Kitty in 2023. That is a genuine signal of enthusiasm and a poor signal of reliability, because Product Hunt collects people at the moment of discovery and almost nobody returns to downgrade a rating eighteen months later. A 4.9 average is evidence of a good launch, not of a good year.

About ten people are running your sending infrastructure

Loops is four years old, took $3.2M, and employs roughly 10 people. Nothing here suggests it is fragile, and independence has real benefits documented elsewhere in this corpus. But your password reset emails are a dependency, and this dependency is small, venture funded, and has not yet had the moment where it either raises a large round or gets acquired.

Price that honestly rather than emotionally. The mitigation is cheap and specific: keep your contact data exportable, keep your transactional sending behind an interface you control rather than calling the Loops SDK from forty places, and know what your fallback is. That advice applies to every small vendor, and it applies here.

The agent story is better than this section implies: Loops ships its own MCP server

This entry stood here as a weakness and it was wrong. Loops publishes an MCP server at https://mcp.loops.so, documented on two of its own pages, authenticated by signing in to a Loops account and reachable from any client that supports remote Streamable HTTP MCP servers, Claude Desktop, Claude Code and ChatGPT among them. The third-party wrappers are still there, Gumloop, Composio, Zapier and viasocket, and they still route your contact data through another vendor and depend on that vendor’s uptime and pricing, but they are no longer the only way in. Postmark ships one too. What survives of this entry is the argument made just above it: the server is one more surface owned by a small vendor, and an agent workflow built on it inherits that dependency.

What real users actually say

The mixed cluster is simplicity itself, and it is the cleanest example of it in this corpus. The same property is the top reason people adopt Loops and the top reason they hit a wall: a Notion-style editor is a joy until you need a layout it will not make, and a product that does three things well is a relief until you need the fourth. Both groups are describing the product accurately.

What is missing from the record is more telling than what is in it. There is no population of people who have run Loops for three years at scale and written about it, because the review sites where such people go have no listing to write on. The product launched at number one on Product Hunt in September 2023 and has shipped since (Bounce Doctor in 2024, Goals in July 2026), so it is clearly alive. It is simply unaudited in public, and a buyer should weigh that rather than read the 4.9 as reassurance.

Ratings breakdown

Six categories, scored 1 to 10, arithmetic mean for overall. The right-hand column names the platform we would recommend instead if that criterion is the one that matters to you.

Who should use Loops, and who should not

Ban policy and account risk

Read the words regardless of permission status carefully, because they close the loophole every other platform leaves open. Elsewhere, a list vendor’s claim that the addresses opted in is at least arguable. Here the origin of the list disqualifies it whatever the paperwork says. Cold outreach is therefore out by construction, not by a separate rule.

Six sectors require prior written approval before you send: financial services including investment, brokerage, lending, crowdfunding and debt collection; pharmaceuticals and telemedicine; tobacco and e-cigarettes; crypto and NFTs; astrology services; and loans and debt relief. Prohibited outright: adult content and escort services, illegal drugs and contraband, pirated software, weapons instructions, hateful or violent material, and anything fraudulent, deceptive or misleading.

The termination clause is as broad as they come: Loops may terminate or suspend your Account immediately, without prior notice or liability, under our sole discretion, for any reason whatsoever. Specific triggers named include violating the acceptable use policy and posting infringing material.

Third-party validation

Sources checked on 14 September 2026.

Top 3 alternatives

Continue reading

Verdict

Frequently asked questions