Signup backend for static sites: why Simple Signups exists

A signup backend for static sites gives a marketing page one reliable HTTPS endpoint: accept an email, reject junk, and store the row somewhere you can export later. That sounds small until you repeat it across projects and re-learn the same lessons about domain allow-lists, rate limits, double opt-in, and where the data should live.

Simple Signups is that backend. It gives you a campaign-scoped HTTPS endpoint for waitlists, newsletters, and contact forms, then handles domain gating, spam checks, storage, and export without asking you to run your own API.

The goal is to keep signup capture boring: plain HTML or light client-side fetch on the front, anti-abuse and storage on the back, and a clean handoff into your email or CRM stack later.

What problem this replaces

• Old PHP habits. Static hosts do not run mail.php next to your HTML anymore.
• One-off serverless handlers. They work, but you own the abuse controls, exports, and long-term maintenance forever.
• Heavy form or ESP embeds. Useful for bigger workflows, heavier than necessary when you only need a thin intake layer.

What a signup backend for static sites should do

• HTML-first embed. A plain form POST is enough. No SDK required.
• Abuse resistance. Domain gating, rate limits, and optional Turnstile before a row is written.
• Your data, exportable. Subscribers stay in your campaigns; pull them when you need a list.

Who is Simple Signups for?

Indie hackers and small teams shipping static or lightly dynamic sites who do not want to stand up another database and mail pipeline for a waitlist or newsletter form. If you already run a full marketing automation suite, this is not a replacement — it is the thin intake layer in front of whatever you use next.

When does it fit best?

• Waitlists and launch pages. Collect email on a static site and export when invites or onboarding go live.
• Newsletter forms. Capture addresses on any site, then forward or export into your sending tool later.
• Contact and enquiry forms. Accept light metadata without building a custom intake API.

How this differs from a form builder or ESP

Simple Signups is not a drag-and-drop form builder and not a replacement email-sending platform. It is the thin intake layer in front of the rest of your stack: your HTML on the page, campaign-scoped endpoint behind it, export or webhooks when you are ready to hand off.

For deeper implementation detail, start with the developer docs or jump to the worked guides for newsletter signups and waitlists.

Common questions

Do I need a backend on my own domain? No. The normal setup is a plain HTML form or browser fetch that posts to the Simple Signups endpoint with your public campaign id.

Is Simple Signups a replacement for Mailchimp, ConvertKit, or HubSpot? No. It is the intake layer that captures and protects the address first, then hands off to the tools you already use for sending or CRM.

What makes it safer than a one-off form script? Domain allow-lists, rate limits, honeypot checks, and optional double opt-in are built into the signup path instead of being left as future TODOs.

This blog will cover product changes, integration patterns, and the anti-abuse choices behind the API as the product matures.