Waitlist tools compared (2026): free plans, referrals, API

A waitlist is easy to start and easy to get wrong at the end. The start is a form. The end is the day you open: invites, an email, a hand-off, and the question of where the good signups came from. The tools below differ mostly in how much of the end they handle, and from where.

The tools, briefly

GetWaitlist does one thing: hosted or embedded waitlists with referral links, leaderboards and automated emails, plus no-code guides for Webflow, Framer, Carrd and the rest. Its free tier closed to new accounts in 2025; its first paid plan, Basic, adds API access, webhooks and export. Custom email templates and sending from your own domain are on the highest tier.

Waitlister is the most agent-forward of the group: an API on every plan, an OpenAPI spec, an npm SDK and an official MCP server, alongside a drag-and-drop landing-page builder, surveys, and a points-based referral programme with milestone rewards from its first paid plan, Launch. Subscriber-data API and webhooks are on Growth.

Prefinery is a referral-marketing platform that runs waitlists: referral links, points, rewards delivered automatically, a leaderboard and thousands of no-code integrations, run from a dashboard. Lite runs one campaign with no API; Essentials adds the API, webhooks and branding removal. Prices are in the table above.

Nordva Launch treats the waitlist as one primitive of seven. Signups come from a hosted page, a script-tag widget or POST /v1/waitlist/signups with a publishable key. Every signup carries a referral code, a position and its first-touch source (referrer and UTM values, no cookie). Indie adds the confirmation email, invites (the longest-waiting first, or one address at a time), a leaderboard, CSV export and a one-off announcement email. The MCP server has the same operations, so an agent can add, invite and export. There is no page builder, no surveys and no reward automation. The same key runs the changelog, feedback, notifications and, with Stripe connected read-only, the report of which signup source produced paying customers.

How to choose

Your situation	Pick
A no-code site, a referral programme with milestone rewards, and a page built in the tool	Waitlister
A marketing team running a rewards campaign with thousands of integrations	Prefinery
The cheapest single-purpose waitlist with an API, on a no-code site	GetWaitlist
The waitlist comes from code or an agent, and you want it to continue into changelog, feedback and revenue attribution on one bill	Nordva Launch

What a waitlist has to do on launch day

Whichever tool you pick, check these four before you need them. They are the difference between a list and a launch.

1. Invite in order, in batches. Position should mean something, so the people who have waited longest get in first. You will not invite everyone at once; a server that has never had users should get fifty, then five hundred. In Launch that is POST /v1/waitlist/invites with { "count": 50 } (the fifty who signed up first), or the invite_from_waitlist MCP tool, and each invited person gets the invite email with your welcome URL. Launch’s position is signup order; referrals show on the leaderboard, so to let your best referrers in early, invite them by address ({ "specific_email": "..." }).

2. Tell the people still waiting. One plain email: it is open, here is your link. Not a campaign; one send, previewed first, with an unsubscribe line. Launch’s announcement is under Waitlist → Announce, one per day at most, counted against the project’s email quota. If your tool cannot do this, export the list and send it from your email provider, and remove the unsubscribes by hand.

3. Hand off to your app. The invite has to land somewhere that recognises the person: a sign-up page with the email prefilled, or a token. Set the welcome URL before launch day, and test the link from the invite email on a phone.

4. Know where the good signups came from. By the evening you will want to know which post worked. That needs the source recorded on each signup, not reconstructed from analytics afterwards. Launch records the referrer hostname and UTM values on every signup on every plan; once Stripe is connected, the attribution report shows which sources turned into paying customers, which is the number that decides what you do next week.

Who should not use Launch for this

If your launch is a rewards campaign (tiers, prizes, automated delivery), Prefinery or Waitlister do that and Launch does not. If you need a landing page built inside the tool, Launch gives you a hosted page with your name, description and colours, not a page builder. And if you are on a no-code site and want Klaviyo or Mailchimp to receive every signup without a webhook step, Waitlister’s integrations on Growth are the shorter path.