Make a form. Share a link. Read every answer.
An open-source alternative to Google Forms. Sign in to build a form, publish a link, and anyone can respond. The people you ask never need an account.
What should we build next?
Your answer shapes the roadmap.
Forms got heavy. They used to be a page and a pencil.
Most form builders are page builders. You drag a grid, theme a wizard, wire up a workflow — and the questions end up buried under the tool that was meant to hold them.
formeasy goes the other way. You write the questions, share a single link, and read what came back. The interface stays out of the way of the only two things that matter: the question and the answer.
Three steps, and the middle one is a URL.
- 01
Write the questions.
Seven field types — short text, long text, multiple choice, checkboxes, dropdown, number, date. Add, reorder, delete. It autosaves as you go, so there is no Save button to forget.
- 02
Share one link.
The people you ask need no account, no app, and nothing to install. The form opens in a browser and answers with JavaScript turned off.
- 03
Read every answer.
Responses arrive newest first, formatted the way the question was asked. Export the whole set as a spreadsheet whenever you want it.
Everything a form needs, and nothing it does not.
- Seven field types
- A question is a question, not a widget to configure. Pick a type, write the label, done.
- Autosave
- The builder writes as you type. Close the tab and the form is exactly where you left it.
- Validated on the server
- Every response is re-checked against the form's own schema. Editing the page in a browser changes nothing.
- One-click CSV
- Quoted the way spreadsheets expect, a column per question, and renamed labels following along.
- Closed, not taken down
- Stop accepting responses and the link keeps working. The questions stay readable; the form just stops taking answers.
- Quiet spam handling
- A hidden honeypot, a per-address rate limit, and size caps. No captcha, so nobody has to prove they are human.
- Agents can use it
- With an AgentOnboard token, an assistant can create a form and read its responses on your behalf.
- Your data, your Postgres
- Forms and answers live in a database you control. There is no vendor in the middle to lose them.
Open source, and yours to run.
Every line is public. Deploy it to Vercel in a few minutes, or run the container against a Postgres you already have. Nothing about the product is behind a plan.
- MIT licensed
- The permissive one. Fork it, rename it, ship it inside something else.
- Vercel or a container
- Two external services — Postgres and Clerk. The rest is a standard Next.js server.
- No lock-in
- The whole data model is two tables. Export it, move it, or leave with it.
Questions people ask first.
Do the people I ask need an account?
No. A published form is a public link. Anyone who has it can answer without signing in, installing anything, or turning on JavaScript.
Is it free?
Yes. It is MIT licensed and you host it yourself, so there is no plan to outgrow and nobody to ask permission from.
Where do the responses live?
In your Postgres, in a single responses table. Export them as a CSV whenever you like. The data is yours to move, back up, or delete.
Can I stop taking responses?
Close the form. Its link keeps working so people can still read the questions, but submissions stop — and reopening is the same switch.
What if a question changes after people answered?
Renaming is free: answers are stored against the question's id, so they follow the new label. Delete a question and its answers stay in the export rather than disappearing.
Do you support branching, uploads, or scoring?
Not yet. Branching logic, file uploads, quizzes, and teams are on the roadmap, and the design notes say how each one lands without breaking stored answers.