Contact form for static sites: drop one URL into your HTML
If you've ever built a static site with HTML, CSS, and a git push deploy - Hugo, Eleventy, plain HTML, even hand-rolled - you've hit the contact form problem: there's no server to receive the POST. Most teams either forward to mailto: (lose every spam-filtered submission), spin up a serverless function (overkill for a contact form), or stand up a tiny backend (worse). Formspring exists to make this trivial: paste one URL into the form's action attribute, and you're done.
Working code
<form action="https://formspring.io/f/abc123" method="POST">
<input name="name" required>
<input type="email" name="email" required>
<textarea name="message" required></textarea>
<button>Send</button>
</form>How it works
You sign up at Formspring, create a form, and copy its endpoint URL (https://formspring.io/f/abc123). Drop that URL into your <form action> attribute - that's the entire integration. Submissions go through five spam-protection layers (honeypot → hCaptcha → custom rules → Akismet → AI moderation) and arrive in your dashboard within seconds. From there, fire signed webhooks to your stack (Slack, Notion, Airtable, custom endpoint), email yourself, or process via API.
Why this beats serverless functions
A serverless contact form means: writing a function, parsing form data, validating fields, handling spam, configuring SMTP, storing submissions, dealing with timeouts, debugging cold starts, paying for invocations, and maintaining all of that. Formspring replaces it with one URL. The math is one-sided unless you have a specific reason to control every layer.
Security and privacy
Submissions are encrypted in transit and at rest. Files (if uploaded) sit in private S3-compatible storage and are only accessible via signed URLs from the dashboard. EU-only hosting (Hetzner Falkenstein/Helsinki). DPA included on every paid plan. Per-form retention rules let you auto-delete after N days for GDPR.
When to NOT use a hosted form backend
Three cases where you should build it yourself: (1) you're already running a backend and form submission is one of dozens of endpoints, (2) you need extreme low-latency processing (<10ms p99), or (3) compliance requires absolute zero data egress. For everything else - and 95% of contact forms fall outside those - Formspring is the simpler answer.