Use cases
What teams build with Formward
Formward is a form endpoint: it accepts submissions, filters spam, emails you, and stores the data in Sweden. These are the setups teams use it for most, each with code you can copy and the plan limits that apply.
Form to email
Point any HTML form at an endpoint and get each submission by email, with spam filtered out and a searchable copy kept in Sweden.
Read more →Contact forms
Your own markup, a one-line popup button, or a hosted page. Spam layers and a consent checkbox come with every plan.
Read more →File upload forms
Take CVs, photos and documents on a plain HTML form. Files stay in Sweden and follow the form's retention period.
Read more →Online forms
Publish a form as its own public page and share the link. No website, no code, and the responses stay in the EU.
Read more →Lead generation
Keep the UTM source on every lead, filter out throwaway addresses, and score leads with EU-hosted AI on paid plans.
Read more →Static site forms
Working forms on Hugo, Jekyll, Astro or any static host. No functions to deploy and nothing tied to one host.
Read more →Agencies
A workspace per client, one bill, and on Business, notification email sent from each client's own domain.
Read more →Job application forms
Run applications from your careers page: CV uploads or links, routing to the hiring team, and retention that deletes CVs on time.
Read more →HTML form endpoint
The idea behind a form backend: one URL in the action attribute that receives the POST, checks it, stores it and sends the visitor on.
Read more →Contact form API
Post JSON from fetch() and read a JSON answer back: the response shape, the status codes to handle and how CORS is gated.
Read more →Form submission API
Pull submissions with the REST API or have each one pushed to you as a signed webhook, and pick the one that fits your system.
Read more →Serverless forms
An honest comparison of writing your own form function against pointing the form at a hosted endpoint, including when to keep the function.
Read more →Need the compliance side first? The GDPR form backend page covers where data is stored, the DPA and sub-processors.