Build Formspree
YESreplaces $15/mosaves $180/yrback to the verdict
A form backend for static sites: point any plain HTML form at your endpoint and get the submission stored, emailed to you and optionally posted to a webhook, with a honeypot, rate limits and an origin allowlist so strangers cannot post to it. Static site stays static; you run one small server.
Before step 1
Everything below is assumed from the first step. Tick each one when you actually have it, not when you plan to.
- installfree
Why Everything in this build runs on it: the server, the scripts, the tests.
Get it Download the LTS installer from nodejs.org, or install with your package manager (brew install node, or nvm install 22). Restart the terminal afterwards. open ↗
Verify
node --version prints v22 or higher - installfree
Why Every step below is a command you type or a file you edit.
Get it VS Code (code.visualstudio.com), Cursor or Zed. Open a folder for the project and use the editor's built-in terminal. open ↗
Verify
You can open a folder and run a command in its terminal - installfree
Why History for your code, and the way most hosts deploy.
Get it Install from git-scm.com or with your package manager, then run git init in the project folder once it exists. open ↗
Verify
git --version prints a version - have readyfree
Why Phase 2 refuses any origin not in the allowlist.
Get it List each site's https origin exactly.
- API keyfree tiers exist
Why Phase 3 emails each submission.
Get it Fastmail, Postmark, Resend SMTP or your mail host: host, port, user, app password.
- have readyfree
Why The other notification path.
Get it webhook.site while testing. open ↗
- accountabout $5 a month
Why This needs one process running all the time with a public address.
Get it Hetzner Cloud (from about 4 EUR), DigitalOcean or Fly.io. Ubuntu 24.04, the smallest size. You need SSH access and a public IP. Only needed for the deploy phase; develop locally first. open ↗
- accountroughly $10 a year, or free on an existing domain
Why A public address you own, so links you share never break when a provider changes.
Get it Register at Cloudflare Registrar, Porkbun or Namecheap, or use a subdomain of one you already own. You add one DNS record in the deploy phase. open ↗
- installfree
Why Automatic HTTPS in front of the Node process. Without TLS the browser features this relies on (and your visitors' trust) do not work.
Get it On the VPS: follow the install steps at caddyserver.com/docs/install for Ubuntu. One Caddyfile with your domain and a reverse_proxy line is the whole config. open ↗
Verify
caddy version prints a version on the server
Data model
Create these before the first phase that stores anything. Changing a table later is the expensive kind of change.
- forms: id, slug (unique, short), name, redirect_url, notify_email, webhook_url, created_at - submissions: id, form_id, received_at, fields (JSON), ip_hash, user_agent_class, spam (bool) - One row per submission with the fields as JSON, because every form has different fields and you do not control the markup that posts to you.
Environment variables
These go in a .env file the app reads at startup. The pack's .env.example is this table as a file · copy it, never commit the filled-in version.
| Variable | Needed | Example | Where the value comes from |
|---|---|---|---|
PORT | required | 3000 | Any free port. |
DATABASE_PATH | required | ./data/forms.db | SQLite file. |
UPLOAD_DIR | required | ./data/uploads | Uploaded files per form. |
ALLOWED_ORIGINS | required | https://yoursite.com | Comma-separated origins permitted to post. |
SMTP_URLsecret | required | smtps://user:pass@smtp.fastmail.com:465 | From your SMTP provider. |
NOTIFY_TO | required | you@yourdomain.com | Where submissions are emailed. |
SITE_URL | required | https://forms.yourdomain.com | Public base URL. |
ADMIN_USER | required | admin | Any username for the basic-auth admin pages. |
ADMIN_PASSsecret | required | change-me-to-a-long-random-string | Generate one: openssl rand -base64 24. Never reuse a real password. |
The build, in order
Accept a post
A plain HTML form on another site submits and lands on a thank-you.
forms (id, slug, name, redirect_url, notify_email, webhook_url), submissions (id, form_id, received_at, fields JSON, ip_hash, user_agent_class, spam). Fields as JSON because you do not control the markup that posts to you.
terminalmkdir formback && cd formback && git init && npm init -y && npm pkg set type=module mkdir -p data/uploads && cp .env.example .env
done when · tick each as it passesSpam controls
Honeypot, rate limit, origin allowlist, bot filter, all flagging rather than deleting.
done when · tick each as it passesNotifications
Email and webhook that never make the visitor wait.
- terminal
npm install nodemailer@6
done when · tick each as it passesFile uploads
Safe uploads with a generated name and a streaming cap.
- terminal
npm install busboy@1 sharp@0.35.3
done when · tick each as it passesAdmin
Forms, the snippet, submissions with spam separate, CSV.
done when · tick each as it passesDeploy
HTTPS, backups covering uploads, README.
Files
deploy/formback.serviceCaddyfileFiles
README.md
done when · tick each as it passesOperate it like a productproduct builder
Only for the product-builder path: know when the endpoint is down, never lose the database, and keep the server patched.
Answer 200 with the build id and a quick database read. Point a free uptime monitor (or your own, from the Healthchecks entry on this site) at it so an outage is noticed before a user notices.
One JSON line per request: method, path, status, duration, no raw IPs. Rotate weekly with logrotate, keep eight.
SQLite's .backup command makes a consistent copy while the app runs. Copy it to object storage or a second machine; then, once, restore it into a fresh checkout and confirm the app reads it.
terminalsqlite3 data/app.db ".backup '/tmp/app-$(date +%F).db'" rclone copy /tmp/app-$(date +%F).db remote:backups/
Firewall allowing only 22, 80 and 443; unattended security updates on; the app running as an unprivileged user under systemd with Restart=on-failure.
done when · tick each as it passes
That is the whole plan for Formspree. What it deliberately does not cover is below · check the gaps before you call it a replacement.
- The integrations gallery and hosted file storage.
- Spam filtering tuned on someone else's traffic.
- Not running a server, which is what Formspree actually sells.
- spam filtering tuned on someone else's traffic
- the integrations (Slack, Zapier, Google Sheets)
- file uploads to their storage
- not running a server for a static site
- A Slack adapter
- Per-form autoresponder email to the submitter
Need the files? The project pack on the verdict page hands your agent the whole brief · more forms.