Loops

What Loops actually is

Loops is an email platform for SaaS companies — marketing, transactional, and lifecycle email in one product — and the database description of it as an "SMTP service built for transactional email at scale" is wrong enough that we have filed corrections below. The product is API-first: sending goes through the Loops API and SDKs (the /email-api surface covers both transactional and marketing sends), with templates, contact management, and audience segmentation included rather than bolted on. Transactional email to recipients who are not part of your marketing audience is included on every paid plan at no extra charge, which is the design point that makes it interesting for software companies: your receipt emails and your onboarding drip share one tool and one contact graph.

The company came out of Y Combinator's Winter 2022 batch, founded by Chris Frantz and Adam Kaczmarek, and it is small — around a dozen people. In our view that is both the appeal and the risk. The product is opinionated and unusually clean, the pricing page is refreshingly candid (it literally tells you to evaluate all your options before choosing), and there is no enterprise-sales gauntlet. There is also no decade-long track record, no large integration marketplace, and less operational mass behind the sending infrastructure than at the incumbents. We prioritize honesty over vendor comfort on this site, so we say that plainly up front.

Pricing: what you really pay

Loops prices by subscribed contacts, not by sends — and the company is explicit about both halves of that. All paid plans include unlimited marketing and transactional sends and full feature access; no per-seat charges, no per-email charges. The published ladder starts at $49/month for 1,001–5,000 subscribed contacts, $99 for 5,001–10,000, $149 for 10,001–15,000, $199 for 15,001–25,000, $249 for 25,001–50,000, $399 for 50,001–100,000, then $599, $799, $1,199, $1,599, $1,999 and onward in the same style up to $4,799/month for 1,250,001–1,500,000 contacts. Above 1,500,000 contacts it is Enterprise — custom contract, with an SLA and dedicated support available.

The free plan is genuinely free and genuinely limited in a specific way: you can store unlimited contacts, but you can only send to your first 1,000 contacts — up to 4,000 sends in any rolling 30-day window, marketing and transactional combined, roughly a weekly email each. All platform features are included on free, and a small "Powered by Loops" footer is appended. No credit card required to start.

The economics deserve a close look, because the model cuts both ways. If you send a lot to a small list — transactional-heavy SaaS products often do — unlimited sends at a fixed contact price is excellent value compared with metered providers. If your list is large but quiet — 40,000 dormant contacts you email twice a year — you pay $249/month for the privilege of having them stored as subscribed contacts. Pruning unengaged contacts is effectively part of operating this product profitably. Also note the first paid step is steep relative to the free plan: crossing from 1,000 to 1,001 subscribed contacts moves you from $0 to $49/month. There is no small paid tier in between, which we regard as the clearest pricing gap in the lineup.

Performance & infrastructure

Loops does not publish a detailed infrastructure page the way hosting vendors do, and we will not invent one. What is verifiable: sending is handled by the vendor (both API and platform-managed delivery), bounce and complaint handling is automatic as part of contact status management, and transactional sends to non-audience recipients are supported alongside marketing sends. The company states its differentiation as developer experience — clean API, clear pricing, fast setup — rather than raw throughput numbers. We found no published throughput benchmarks, no per-region data-residency options, and no public SLA except the Enterprise-tier "SLA available" line; those fields are left unset in our specs rather than guessed. For a small vendor this is the kind of transparency gap that matters when email is load-bearing for your product: ask support directly about sending limits, dedicated IPs, and warm-up policy before you commit, and treat any answer as a commitment to get in writing.

Company health is the other half of infrastructure here. Loops is venture-backed via Y Combinator (W22) with a small team in the United States — company profiles place it variously in Beaverton, Oregon and Washington, DC, so we record only the country and flag the conflict. Small vendors get acquired, pivot, or wind down; your mitigation is standard for this category. Keep templates and contact data exportable, and make sure your transactional path has an exit plan. On the other hand, small vendors also ship fast and answer support tickets like their revenue depends on it — because it does.

The developer surface is the part we would evaluate first. Loops ships an Email API covering both transactional and marketing sends, with SDKs, transactional templates, and a contacts API that keeps your audience model in sync with your product database. Transactional email to recipients outside your marketing audience is explicitly included on paid plans, which matters for SaaS products where receipts and password resets must not be treated as marketing volume. Contact properties and events give you the raw material for lifecycle email — onboarding sequences, trial-expiry nudges, win-back campaigns — without a separate marketing tool. The pricing FAQ is the most candid we have read in this category: it states plainly that sends are not metered, that a subscriber is any address marked subscribed, that team seats are free, and that you should compare all your options before choosing. That tone extends to the free plan's limits, which are specified exactly rather than buried in a footnote. In our view, vendors who describe their own limitations this clearly deserve credit on the transparency criterion — it is cheap to be vague, and Loops chose not to be. The open question is depth: the API and templates handle the common SaaS email shapes well, but teams migrating complex automation trees from larger platforms should prototype their five most important flows during evaluation before switching.

Where it falls short

Segmentation and automation depth are the first limitation. If you are coming from a mature marketing platform, expect fewer branching options, fewer pre-built flows, and less sophistication in behavioral triggers; Loops covers the SaaS-email essentials (transactional sends, lifecycle drips, marketing campaigns, contact properties) rather than the full marketing-cloud surface. Second, the ecosystem is thin: far fewer native integrations and third-party plugins than larger competitors, though the API is the intended escape hatch. Third, the contact-based pricing cliff between free and $49, plus the fact that dormant subscribed contacts cost real money every month, punishes list hygiene laziness. Fourth, the track record is short and the team is small — a fair reliability question, not a disqualification. Fifth, we could not find published deliverability infrastructure details (dedicated IP availability, shared IP pool management, regional sending), which is exactly the homework we would do before trusting any email vendor with receipts and password resets.

Who should pick this

Our pick for SaaS teams who want marketing and transactional email in one product, priced predictably, without a marketing-cloud implementation project. It fits best when you send frequently to a modest list — the unlimited-sends model rewards that shape. It is a weaker fit for large-but-inactive lists, for teams that need advanced marketing automation depth, and for organizations that require a published SLA or data-residency guarantees outside Enterprise. If your transactional email is absolutely mission-critical and you cannot tolerate a small-vendor risk, a dedicated transactional provider with published infrastructure detail is the safer pairing — and you can still run Loops for lifecycle and marketing alongside it.

Key takeaways

• Loops is a full email platform for SaaS (marketing + transactional + lifecycle), not an SMTP relay service — the old database description was wrong.
• Pricing is per subscribed contact with unlimited sends on paid plans: $49/month at 1,001–5,000 contacts, scaling to $4,799/month at 1.5M; no seat or send charges.
• Free plan: unlimited stored contacts, 4,000 sends per rolling 30 days to the first 1,000 contacts, all features, branded footer.
• The jump from free (1,000 contacts) to the first paid plan ($49) is steep — there is no small paid tier.
• Y Combinator W22, founded 2022, small US team; capable vendor, but no published SLA outside Enterprise and thin integration ecosystem.
• Best economics for send-heavy, contact-light SaaS workloads; expensive for large dormant lists.

Sources

• https://loops.so/
• https://loops.so/pricing
• https://loops.so/.well-known/pricing.txt
• https://loops.so/about
• https://loops.so/email-api
• https://smtpedia.com/platforms/loops-so
• https://smtpedia.com/platforms/loops-so/review