GetWaitlist vs Lighthouse: Which Fits an Indie Launch? (2026)

GetWaitlist wins on referral loops. Lighthouse wins on knowing why people joined (survey answers) and what to do after (newsletter, feedback).

GetWaitlist is a waitlist tool built around one strong idea: users move up the list by referring friends. Lighthouse is a launch toolkit where the waitlist is one of four pieces (waitlist landing page with survey on signup, newsletter, feedback page, REST API). Both capture email addresses on a landing page, but they solve different jobs. This is the honest comparison from someone who has used both for different things.

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 pre-launch plumbing.

Table of contents

• What each tool actually is
• Side-by-side comparison
• Where GetWaitlist wins
• Where Lighthouse wins
• Who should pick which
• Using both together
• Frequently asked questions

What each tool actually is

GetWaitlist is a waitlist tool with a referral engine at the center. Each signup gets a unique share link; referring friends moves the user up the list. The mechanic is well-executed and the reason GetWaitlist is on the shortlist for most viral-launch attempts. Bundled with a landing-page builder, embed widgets, and a free tier that covers small lists. Best when the launch narrative is “get to the front of the line by inviting friends”.

Lighthouse is a launch toolkit for indie SaaS founders. A waitlist landing page with survey questions on the same form, a newsletter for keeping the list warm after launch, a feedback page for once people are using the product, and a REST API on Pro. Flat $19/$29 pricing that does not change with list size. Built for people whose product is a SaaS or an app, where the waitlist is one piece of a validate-then-launch arc.

Side-by-side comparison

Two tools shaped for two different jobs. The matrix below is the honest version.

Where GetWaitlist wins

Be honest about this part. GetWaitlist is the right tool for a real list of jobs:

• Serious referral loops. If the launch plan is “let signups pull in more signups”, GetWaitlist is the shortest path to that mechanic working. Position rank, invite tracking, rewards for hitting referral thresholds. Lighthouse does not have a referral engine.
• Free tier for validation. If you are not yet sure the idea will get traction, the free tier lets you validate before paying anything. Lighthouse charges $19 from day 8 (after the 7-day trial), which is fine for founders committed to launching but a higher upfront ask.
• Position-based framing. “You are #128 of 4,213” is a specific shape of social proof that works for consumer-facing launches (courses, consumer apps, buzzy indie tools). Lighthouse leans goal-based (“47 of 100”), which suits smaller lists but reads different.
• Widgets and embeds. GetWaitlist embed widgets drop into an existing marketing site cleanly. Lighthouse gives you the whole landing page, which is faster if you do not have a site, and less flexible if you do.

Practical rule: if the launch narrative is a viral-share referral loop, GetWaitlist is the honest answer.

Where Lighthouse wins

Lighthouse is the better fit when the waitlist is the start of a validate-then-launch arc, not a viral push:

• Survey questions on the signup form, as the default. Lighthouse treats the survey-on-signup pattern as the main pattern. GetWaitlist has custom fields, but the survey UX, the answer segmentation, and the “email everyone who answered X” flow are not there. See why answers beat emails for the reasoning and how to segment your waitlist by survey answers for the payoff.
• Newsletter for the list after signup. The warmup emails, the launch email, and the 72-hour follow-up all live in the same dashboard as the waitlist. GetWaitlist has basic broadcast but not the campaign shape most indie launches need. See how to convert waitlist signups into paying customers for the full sequence.
• Feedback page after you launch. GetWaitlist stops at the launch email. Lighthouse keeps going with a feedback inbox that handles bugs, feature requests, and praise post-launch, on the same dashboard.
• Flat $19/$29 pricing. The price does not step up as the list grows. GetWaitlist paid tiers scale with signup volume, which gets awkward for a waitlist that pulses at launch (2,000 signups over a weekend).
• REST API shaped for SaaS onboarding. Lighthouse Pro exposes waitlist signups, survey answers, and feedback as REST endpoints your product can pull. See how to add a TestFlight beta waitlist to your iOS app for the pattern.

Who should pick which

The choice is rarely “which one is better”. It is “which job is this for”. Five founder shapes:

The viral-launch consumer founder

You are shipping a consumer app or course and the launch plan hinges on a referral loop (“invite friends, move up the line”). Your audience is broad and share-friendly. GetWaitlist, every time. Lighthouse is not built for this.

The pre-launch indie SaaS founder

You are weeks from beta and you need a public landing page with a signup form, survey questions on the form, and a way to email the list when you launch. Lighthouse, every time. GetWaitlist gets you the signups but leaves you assembling the survey UX and the campaign flow by hand. See what to put on your waitlist landing page for the layout Lighthouse ships.

The founder raising capital

You are raising and the bottleneck is the raise itself. Neither GetWaitlist nor Lighthouse is the headline tool here. Dedicated platforms like Funding Banker, a curated investor directory with pitch and outreach tracking, handle the investor side. Pick GetWaitlist if the raise story leans on a viral-share signup graph; pick Lighthouse if the raise story leans on survey answers and audience insight (more common for a B2B SaaS pitch).

The post-launch SaaS founder

You shipped, you have customers, you want to send updates and collect feature requests. Lighthouse for the bundled flow (newsletter and feedback inbox in one dashboard). GetWaitlist is not the right shape post- launch; the referral engine is a pre-launch mechanic.

The indie iOS developer

You want a beta waitlist with survey questions and the data flows into your iOS app for onboarding personalisation. Lighthouse on Pro. The waitlist-with-survey-answers REST API is the differentiator. GetWaitlist has an API but the shape of the data is position-and-referrer, not waitlist-with-survey-answers; you would build the semantics yourself.

Using both together

Rarely worth it, but two patterns exist:

• GetWaitlist as the top-of-funnel viral capture, Lighthouse as the qualified sub-list. Signups go into GetWaitlist for the referral push; once someone completes the referral bump or hits a milestone, they get invited to a Lighthouse waitlist with a survey to qualify. Two tools, two lists, one handoff. Only worth it if the referral loop is actually working; otherwise it is one tool too many.
• GetWaitlist for a specific viral campaign, Lighthouse for the main product waitlist. You run a one-off viral campaign on GetWaitlist (a contest, a beta lottery) and keep the main product waitlist on Lighthouse. Zero data sharing, two distinct jobs.

The fit-for-purpose rule: each tool does the job it was built for. Most indie founders should pick one.

Frequently asked questions

Does Lighthouse have referral mechanics?

Not today. Referral is on the roadmap. If a viral referral loop is the whole launch story, GetWaitlist is the honest pick for now. If the launch story is “survey answers, warm the list, ship the launch email, keep going with feedback”, Lighthouse covers the full arc that GetWaitlist stops halfway through.

How does GetWaitlist's free tier really hold up?

Solid for small lists. Once the referral engine works and signups compound past the free-tier cap, the paid tiers step up in bands that scale with signup volume. Fine if the referral loop is producing real engagement; awkward if the list grew mostly from a single X thread and you now pay per-signup for traffic that will not convert at launch.

Can Lighthouse send the launch email to my waitlist?

Yes. That is the second piece of the toolkit. Compose a campaign in the dashboard, pick the list (your waitlist signups, filtered by survey answer if you want), send. For the launch email shape, see how to write your first launch email. For the sequence around it, see how to convert waitlist signups into paying customers.

Can I migrate from GetWaitlist to Lighthouse?

Export signups from GetWaitlist as CSV, import into Lighthouse. Survey answers do not carry across (the data shape is different), so plan on sending a one-time segmentation email once the list is imported. Referral position rank is not preserved either; if the referral graph was the whole point, stay on GetWaitlist.

Do I need both?

No. Most indie founders pick one. Choose by the job: a viral referral loop picks GetWaitlist; a launch toolkit with the waitlist as one piece of a validate-then-launch arc picks Lighthouse. Use both only when you have clearly separate uses (viral campaign on GetWaitlist, product waitlist on Lighthouse).

Pick the tool that fits the actual job. If the launch narrative is a referral loop, GetWaitlist is the honest answer. If the launch narrative is “survey answers, warm the list, ship the launch email, keep going with feedback”, Lighthouse covers the arc that GetWaitlist stops halfway through. Most of the disappointment with either tool comes from buying it for the job 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. 7-day free trial, indie pricing. From the same indie dev behind Spaceport, a SwiftUI starter kit for shipping paid iOS apps fast.