Amazon SES vs Loops for Solo Developers

Comparing Amazon SES and Loops for solo developers. Features, pricing, pros and cons, and which one to pick for your next project.

Quick Comparison

Feature	Amazon SES	Loops
Type	Low-level email infrastructure	SaaS email platform for product companies
Pricing model	$0.10 per 1,000 emails, billed per recipient	Priced by stored contacts, unlimited sends
Entry price	Pay-as-you-go (no minimum)	Free under 1,000 contacts, then $49/mo at 5,000
Free tier	3,000 message charges/mo, first 12 months only	1,000 contacts and 4,000 sends/mo, permanent
Official SDK	@aws-sdk/client-sesv2 v3.1056.0	loops v6.3.0 (MIT)
Built-in automation	None	Visual Workflows builder
Contact management	None (bring your own database)	Built-in with properties and segments
Learning Curve	Steep	Easy
Best For	High-volume email at rock-bottom cost	SaaS email with automation and lifecycle management
Solo Dev Rating	6/10	8/10

Amazon SES Overview

Amazon SES is email infrastructure stripped down to the essentials. It sends emails for $0.10 per 1,000 messages. That is its pitch, and that pitch works when volume is high and budget is tight.

You get an API for sending, SNS integration for delivery notifications, CloudWatch for metrics, and basic templating. Everything beyond that, automation sequences, contact management, analytics dashboards, suppression list maintenance, is something you build or configure yourself using other AWS services or custom code.

Setting up SES means creating an AWS account, configuring IAM policies, verifying your domain, requesting production access out of the sandbox (which can take a day), and wiring up SNS topics for bounce and complaint handling. If you skip the bounce handling part, AWS can suspend your sending privileges when your bounce rate exceeds their threshold.

Loops Overview

Loops is purpose-built for SaaS companies that want to manage their entire email strategy in one platform. It handles transactional email, product announcements, onboarding sequences, and re-engagement campaigns through a visual interface designed for speed.

The automation builder is the standout feature. You create flows triggered by user events: signup, trial start, feature activation, plan upgrade, inactivity. Each flow has steps with delays, conditions, and branching logic. You build a complete onboarding email sequence in an afternoon without touching your backend code.

Contact management tracks user properties and lets you create segments. You can target emails based on plan type, last login date, feature usage, or any custom property you send through the API. The dashboard shows open rates, click rates, and flow performance in clean, readable charts.

Loops starts free for up to 1,000 contacts. The paid tier at $49/month supports 5,000 contacts with unlimited sends.

Key Differences

These are fundamentally different categories of tool. SES is a pipe that carries email from your server to an inbox. Loops is a platform that decides which emails to send, when to send them, and tracks how recipients engage. Comparing them is like comparing a delivery truck to a logistics company.

Time to value. With Loops, you sign up, connect your domain, build an onboarding flow in the visual editor, and start sending automated emails within a few hours. With SES, you spend those same hours just getting out of the sandbox and configuring bounce handling. The actual email logic, the part that drives user engagement and conversion, still needs to be built in your application code.

Automation is the defining gap. Loops has a visual flow builder for multi-step email sequences with conditions and delays. SES has nothing. To replicate Loops' automation with SES, you need a task queue (like Celery or BullMQ), a database to track user states and email history, scheduling logic for delays, and conditional branching code. That is days of development work for what Loops offers out of the box.

Contact management. Loops tracks every user with properties, events, and engagement history. You can segment your audience and send targeted emails. SES does not store contacts. It sends individual emails to addresses you provide. Any user tracking or segmentation requires your own database and application logic.

Cost structure. SES charges per email. At moderate SaaS volumes (10,000 emails/month), SES costs about $1. Loops at 3,000 contacts costs $49/month. The price gap is real. But the development time to build Loops-equivalent features on top of SES, automation, contact tracking, analytics, segmentation, easily costs hundreds of hours. The $49/month pays for itself in the first week.

Analytics and insights. Loops shows you which flows convert, which emails get opened, and which users are engaged. SES gives you delivery metrics through CloudWatch, open and click tracking requires additional configuration with configuration sets and event destinations. Understanding user engagement with raw SES data requires significant custom analytics work.

By the Numbers (2026)

Here is where the two products actually sit today, with the receipts.

Amazon SES. Outbound sending is $0.10 per 1,000 emails, billed per recipient rather than per message, so one email to 100 people counts as 100 charges. Attachments add $0.12 per GB of data. The free tier gives new AWS accounts up to 3,000 message charges per month, but only for the first 12 months after first use, after which you pay from the first email. There is no public version number for the service itself, so adoption shows up in the SDK instead. The official AWS SDK for JavaScript SESv2 client sits at v3.1056.0 and pulls 2,135,218 weekly downloads on npm, which tells you how much code in the wild talks to SES directly. Optional add-ons stack on top of the base rate: a standard dedicated IP is $24.95 per month, and Virtual Deliverability Manager adds $0.07 per 1,000 emails.

Loops. The free plan covers under 1,000 stored contacts with up to 4,000 sends per month and a "Loops" footer, and unlike the SES free tier it does not expire. Paid pricing is keyed to stored contacts, not send volume, and every paid tier ships unlimited sends. The Starter plan is $49 per month for 5,000 contacts. From there it climbs to $99 (10,000 contacts), $149 (15,000), $199 (25,000), and $249 (50,000), with a Scale plan at $399 for 100,000 contacts and custom pricing above that. The official JavaScript SDK, published as loops on npm, is at v6.3.0 (released 2026-04-09, MIT licensed) and sees 165,159 weekly downloads. Its source repo loops-so/loops-js carries only 7 GitHub stars, which is normal for a single-vendor SaaS client where the npm download count, not stars, is the real adoption signal. Transactional email is included on every plan at no extra charge.

The headline gap is structural. SES meters the thing it does (delivery), so a quiet month costs almost nothing. Loops meters the asset it manages (your contact list), so the bill is steady whether you send daily or never. That difference is the whole decision, and the next section runs the actual math.

Real Cost at Solo-Dev Scale

Take a realistic early SaaS product. Say you have 3,000 subscribed users, and each one gets a 5-step onboarding sequence plus a roughly weekly product or marketing email. That works out to around 12,000 to 15,000 sends per month. No attachments, no dedicated IP, no Virtual Deliverability Manager.

On Amazon SES. Delivery is the only line item. At $0.10 per 1,000 emails, 15,000 sends is about $1.50 per month. SES is past its 12-month free window in this scenario, so you pay from the first send, but the bill is still rounding error. The catch is everything that bill does not cover. The 5-step onboarding sequence, the weekly scheduler, the contact properties, the open and click tracking, the segment that says "users who never finished onboarding", all of that is code you write and a database you run. The dollar cost is roughly $1.50. The real cost is the engineering days.

On Loops. 3,000 contacts lands inside the Starter band, so you are at $49 per month flat. Sends are unlimited, so going from 15,000 to 30,000 emails changes nothing on the invoice. The $49 includes the visual Workflows builder, contact properties, segments, and engagement analytics out of the box. There is no scheduler to write and no events table to maintain.

So the honest spread at this scale is about $1.50 versus $49 per month, a difference of roughly $570 per year. That is the number SES defenders point at, and it is real. But it only holds if you already have the automation, tracking, and segmentation built. Building Loops-equivalent flows on raw SES is comfortably tens of engineering hours, and then it is yours to maintain forever. For a solo developer whose scarcest resource is hours, the $570 a year buys back the part of the stack you would otherwise be hand-rolling.

Where the math flips is volume. SES stays near-flat as sends climb because it never charges for contacts, while Loops climbs with the list, not the volume. If you grow to 50,000 contacts you are at $249 per month on Loops regardless of send count, whereas blasting even 500,000 emails through SES is about $50 in delivery. At that point the contact-priced model is the expensive one, and splitting high-volume transactional traffic to SES while keeping Loops for lifecycle email is the move the Verdict describes.

When to Choose Amazon SES

You have specific infrastructure requirements that need raw email API access
You are already invested in AWS and want to keep everything in one ecosystem
You are building custom email tooling for very specific use cases
Volume is extremely high and every dollar of email cost matters
You have engineering time to build automation, analytics, and contact management

When to Choose Loops

You are building a SaaS product and want email automation without custom code
Onboarding sequences, trial conversion emails, and re-engagement campaigns are important
You want contact management with segmentation and user property tracking
Speed of implementation matters more than saving a few dollars on email delivery
You prefer a visual builder over writing backend email scheduling logic

The Verdict

If you are a solo developer building a SaaS product, Loops is the clear winner. The automation features alone save you weeks of development time compared to building equivalent functionality on SES. You will ship onboarding emails, conversion flows, and product updates in hours instead of days.

SES makes sense in narrow scenarios: you are already deep in AWS, you have very specific infrastructure requirements, or your email volumes are so high that the cost difference is material. For a solo SaaS developer sending thousands (not millions) of emails per month, the cost savings of SES do not come close to justifying the development time you would invest.

My advice: use Loops for everything user-facing, the onboarding flows, the product updates, the re-engagement campaigns. If you later hit a scale where SES pricing makes a meaningful difference, you can migrate the high-volume transactional sends to SES while keeping Loops for the automation and marketing side. But most solo developers never reach that threshold.