Create a list
Give it a name, choose a URL slug, and decide which websites can submit to it.
Waitlist infrastructure, simplifiedOne endpoint.
One endpoint.
Every waitlist.
Create a list, point any form at its endpoint, and watch the signups arrive. No form builder, no campaign maze, no unnecessary contact fields.
Get early access
Join this product’s waitlist.
This form posts to waitinglists.dev—the very product you’re signing up for.
Built for tiny launches & serious productsAstroCloudflare WorkersD1Your HTML form
How it works
From idea to collecting emails in three steps.
waitinglists.dev stays deliberately small: a clean endpoint on the public side and a focused control room on the private side.
Connect your form
Post an email plus explicit consent. Plain HTML, HTMX, or JavaScript all work.
Confirm and export
Only confirmed addresses enter your export. Pending requests expire and are removed automatically.
Just a form
Your frontend stays yours.
No embedded widget to restyle. Keep the form you already designed and change only where it sends the email.
index.html
<form method="post"
action="https://waitinglists.dev/api/subscribe/your-list">
<input
type="email"
name="email"
required
/>
<label>
<input type="checkbox"
name="consent" value="yes" required />
I agree to join this waitlist.
</label>
<button>Join the waitlist</button>
</form>No bloat
The useful parts, and nothing pretending to be a CRM.
Email-only by design
The only subscriber-supplied personal data is an email. Consent status and timestamps provide the minimum audit trail.
Works across your sites
Create a separate endpoint for every launch and restrict browser submissions to the origins you trust.
Confirmed-only exports
Download consent metadata with confirmed addresses. Unverified requests never enter the usable list.
One quiet dashboard
See list counts at a glance, inspect signups, and keep many launches organized in one place.
Private means private
Locked down where it matters.
01
Server-enforced accessEvery dashboard page, write action, and export checks an active admin session on the server.
02
Hardened sessionsShort-lived, random session tokens are protected by secure, HTTP-only cookies and CSRF checks.
03
Edge rate limitingLogin and collection endpoints are throttled before abusive requests can become a problem.
04
Privacy by defaultDouble opt-in, self-service deletion, finite retention, and email-only collection are built in.