A form builder that gets out of the way.
formeasy is an open-source alternative to Google Forms, built around one belief: the interesting part of a form is the question, and everything else should be quiet enough to forget.
Why it exists.
Asking people questions should be the easiest thing on the internet. Somewhere along the way it turned into a page-building exercise: pick a template, drag a grid, theme a wizard, and hope the questions survive the trip.
formeasy was written to be the small version. Build a form, get a link, collect answers, export a spreadsheet — and then read the source when you want to know exactly what it does with your data. Two tables, a handful of routes, and no vendor between you and the answers.
It is deliberately unambitious in scope and deliberately careful about the parts that matter: the public path stays public, the validation happens on the server, and failures reach the person as a sentence rather than a stack trace.
The rules we hold to.
- Minimalism, then fluidity.
- One accent colour, hairlines instead of shadows, and space as the default answer to almost every layout question. Motion is short, on one curve, and only ever explains what changed.
- A question is content.
- The serif is the voice — page titles, question labels, the form itself. The sans is the chrome around it. That split is why a formeasy form reads like a document rather than a settings screen.
- The public form is HTML first.
- A form renders, reads, and submits with JavaScript switched off, because a respondent should never need a script to answer a question. Animation there is CSS, and never a prerequisite.
- The server is the gate.
- A form's schema lives in the database and every answer is re-validated against it. The client is a convenience; editing the page in a browser changes nothing.
What is not here yet.
The first version does the core loop well and stops there. Each of these is its own project, and each is additive — none of them changes the shape of an answer already stored.
- Branching and conditional logic
- Multi-page forms
- File uploads
- Quizzes and scoring
- Payments
- Teams, roles, and sharing
- Themes and custom styling
Contributing.
Issues and pull requests are welcome. The design notes and the roadmap live in the repository, and the contributing guide says how the tests run — the hermetic suite first, the browser suite when the secrets are there.