Loops vs Lighthouse: Which Fits an Indie Launch? (2026)
Honest comparison of Loops and Lighthouse for indie SaaS founders. Loops if you need transactional and marketing email for an already-launched SaaS. Lighthouse if you need the full launch arc (waitlist, survey, newsletter, feedback). Price, features, audience, and who should pick which.
Posted by
Related reading
Tally vs Lighthouse: Which Fits an Indie Launch? (2026)
Honest comparison of Tally and Lighthouse for indie founders. Tally if you need an unlimited free form builder. Lighthouse if you need a waitlist with survey questions, a newsletter, and a feedback page. Price, features, audience, and who should pick which.
Substack vs Lighthouse: Which Fits an Indie Launch? (2026)
Honest comparison of Substack and Lighthouse for indie founders. Substack if the publication IS the product. Lighthouse if the newsletter is one piece of a launch toolkit. Price, features, audience, and who should pick which.
Beehiiv vs Lighthouse: Which One Fits an Indie Launch? (2026)
Honest comparison of Beehiiv and Lighthouse for indie founders. Beehiiv if the newsletter IS the product. Lighthouse if the newsletter is one piece of a launch toolkit. Price, features, audience, and who should pick which.

Loops is an email platform built around the SaaS sending lifecycle: transactional, behavioural, and broadcast email from inside one tool, with a focus on developer experience. Lighthouse is a launch toolkit where the email piece is one of four. They look similar at first glance, and the fork is bigger than the marketing makes it sound. This is the honest comparison from someone who has used both for different jobs.
I have shipped 7 indie apps over 8 years and ended up building two tools for myself along the way: Spaceport, a SwiftUI starter that gets a paid iOS app live in days, and Lighthouse, the launch toolkit this post is mostly about. Different audiences, same indie-dev frustration: every new project rebuilt the same plumbing.
Table of contents
What each tool actually is
Loops is an email platform built for SaaS. It handles transactional email (password reset, receipts), behavioural email (drip campaigns triggered by user actions), and marketing broadcasts, all inside one dashboard with a developer-friendly API and SDK. The pricing is volume-based, free up to 1,000 contacts, then climbing with list size. The product is the email engine. That is the entire job.
Lighthouse is a launch toolkit for indie founders. A waitlist with survey questions on the same form, a newsletter for keeping the list warm before and after launch, a feedback page for once people are using your thing, and a REST API on Pro. Flat indie pricing, no per-contact tiers. Built for people whose product is in the pre-launch or just-launched window, where the email piece is one part of getting the first hundred real users.
Side-by-side comparison
Two tools shaped for two different stages. The matrix below is the honest version.
| Capability | Loops | Lighthouse |
|---|---|---|
| Transactional email (receipts, password reset) | Yes, headline feature | No, not the lane |
| Behavioural triggers (drip campaigns) | Yes, full builder | No |
| Waitlist landing page with goal counter | No | Yes, the main use case |
| Survey questions on the signup form | No | Yes, native pattern |
| One-off broadcast campaign | Yes | Yes, baked in |
| Feedback page after launch | No | Yes, baked in |
| Developer API and SDK | Yes, headline | Yes on Pro |
| Custom domain | Yes, sending domain | Yes on Pro |
| Pricing | Free up to 1,000 contacts, then scaling | $19 a month flat, $29 with API |
Where Loops wins
Be honest about this part. Loops is the right tool for a real list of jobs:
- The post-launch SaaS sending stack. Transactional, behavioural, and broadcast email in one place is exactly what an already-launched SaaS needs. Lighthouse does not try to be this.
- Behavioural triggers. If you want "send X email when a user signs up and then Y email three days later if they have not done Z", Loops is built for this. Lighthouse has one-off campaigns; the loop logic is not its lane.
- Developer experience for sending. Loops has a clean SDK and the dashboard feels like a product made by people who send email for a living. If your product fires transactional email by the thousand, this matters.
- Free up to 1,000 contacts. A small SaaS with fewer than 1,000 users can run Loops for nothing. Generous free tier for a sending tool of this depth.
Practical rule: if you have already shipped, have signups happening daily, and need transactional plus behavioural plus broadcast email in one tool, you already have the answer.
Where Lighthouse wins
Lighthouse is the better fit when the email is one piece of an indie launch arc, not the whole sending stack:
- The pre-launch phase. Loops starts when you have users to email. Lighthouse starts when you have an idea and no users yet. The waitlist with survey questions on the signup form is the part Loops does not have a shape for. See the pre-launch checklist for where this lives in the broader launch arc.
- Survey questions on the signup form, by default. Every signup teaches you something about what to build. Loops collects email addresses; Lighthouse collects email addresses with answers. See why answers beat emails.
- Feedback page after you launch. Loops sends your launch email; Lighthouse sends the launch email and gives you the feedback inbox for everything that comes back. Two pieces of the same arc.
- Flat indie pricing. $19 a month does not move as your list crosses 1,000, 5,000, or 10,000 contacts. Loops's tier-based pricing is competitive at small sizes and gets real at indie scale.
Who should pick which
The choice is mostly about the stage you are in, not which tool is "better". Five founder shapes:
The pre-launch indie founder
You are weeks from beta. You need a landing page, a signup form with survey questions, and a way to email the list when you launch. Lighthouse, every time. Loops will not have anywhere to put your signups, because the waitlist landing page is not its lane.
The post-launch SaaS founder, light volume
You shipped, you have a few hundred users, you mostly want to send a monthly update and the occasional broadcast. Lighthouse is simpler and the newsletter campaign tool is fine. Loops is overkill until you start needing behavioural triggers.
The post-launch SaaS founder, heavy sending
You ship transactional email from your product (password reset, invite emails, daily digests), you want behavioural drips, and you have or expect more than a few thousand users. Loops is what you actually need. Lighthouse will not match the sending depth.
The founder raising capital
You are raising and the bottleneck is the raise itself. Neither Loops nor Lighthouse is the headline tool. Dedicated platforms for investor outreach, like Funding Banker, a curated investor directory with pitch and outreach tracking, are built for that side. Pick Lighthouse for the public waitlist; pick Loops once the product ships and you have a sending volume to justify it.
The indie iOS developer
You want a beta waitlist with survey questions and an API the iOS app can call. Lighthouse on Pro. The REST API ships the data into your app for onboarding personalisation. Loops is a sending tool; it does not own the signup data. See how to add a TestFlight beta waitlist to your iOS app for the full setup.
Using both together
The cleanest split: Lighthouse for the pre-launch and launch window, Loops for the post-launch sending stack. The handoff happens on launch day, when the waitlist becomes a user list.
- Pre-launch and launch day: Lighthouse. The waitlist with survey questions, the launch email to the list, the feedback page once the product is live.
- Post-launch, week two onwards: Loops. Transactional sending from the product, behavioural drips for onboarding, and broadcasts to the user base as it grows.
Most indie founders do not need both on day one. Most need Lighthouse first and graduate to Loops six to twelve months in, when the sending complexity catches up with them. Buying both from the start is over-tooling.
Frequently asked questions
Can I use Loops for a waitlist?
You can capture emails through their API, but you do not get the landing page, the goal counter, or the survey questions on the signup form. For the pre-launch validation arc, Loops is the wrong shape. For sending email to the waitlist once you have one, Loops works.
Does Lighthouse send transactional email?
No, not in the sense Loops means. Lighthouse sends campaigns and launch emails. If your product needs to send "password reset" or "receipt" emails on a per-user trigger from inside the product code, that is not Lighthouse. That is Loops, Resend, or Postmark.
How does the pricing scale at indie sizes?
Loops is free up to 1,000 contacts, then tiers up with list size. For a 5,000-contact list with weekly sends it gets into the $30+ a month range. Lighthouse is $19 a month flat regardless of contact count, and $29 with the API. The crossover for indie founders typically happens around 2,000 contacts.
Which has better deliverability?
Both are good. Loops has more invested in transactional deliverability (which is harder than broadcast deliverability). For broadcast at indie volumes, both land in the inbox reliably. If you are running a transactional-heavy product, Loops is the safer bet.
Do I need both?
No, not at launch. Pick Lighthouse for the pre-launch and launch phase; revisit Loops when transactional and behavioural sending from inside the product becomes a real job. Most indie founders do not need both for at least the first six months.
Pick the tool that fits the stage you are in. If you are pre-launch, the waitlist with survey questions is the part that matters and Lighthouse covers it. If you are post-launch with sending volume, Loops is purpose-built for the email engine you need. Most of the disappointment with either tool comes from buying it for the stage it was not built for.
Lighthouse gives you the waitlist with survey questions, the newsletter for keeping the list warm, and the feedback page for after you launch, in one place. Free trial, indie pricing. From the same indie dev behind Spaceport, a SwiftUI starter kit for shipping paid iOS apps fast.