About
Built for the forms that carry weight
Formora exists for the awkward middle ground: work too structured for a simple form tool, but nowhere near big enough to justify a data system that takes six months and a consultant to configure.
The gap this fills
Most data collection ends up in one of two places. Either a general-purpose form tool, which handles the questions but nothing around them — no reference data, no way to compute a value from two answers, no memory of which version of the form a response belongs to — or a full data platform, which handles all of that and asks for a six-month implementation first.
Between the two sits an enormous amount of real work. A monitoring visit with a repeating section per school. An intake form where three questions only apply to some applicants and one of them is calculated. A district list of several hundred entries that four different forms need to agree on. None of that is exotic, and all of it is exactly where a simple form tool runs out and a spreadsheet takes over.
That is what this is for. The rules engine, the managed option lists, the immutable published versions and the record timeline are all answers to the same question: what does a form builder need before the data coming out of it can be trusted six months later?
What we commit to
Four things we hold ourselves to
Stated as commitments rather than values, because a commitment can be checked.
We describe what exists
Every capability on this site is built and documented. We do not list a feature as shipped because it is on a roadmap, and we do not claim a certification we do not hold — see security and compliance for exactly where we stand.
Your data stays yours
Export it to CSV whenever you want and delete it whenever you want, in whole or one response at a time. We do not sell it, mine it, or train anything on it.
Answers stay readable
A published version is frozen and every response records the version it belongs to, so editing a form next year cannot quietly change what last year’s data appears to say.
The interface is not the security
Permissions are enforced by the API on every request. Hiding a button is a courtesy to the user, never a control — and the two are never confused here.
Getting in touch
Questions, or something not working?
The documentation covers most of it. For anything else there is a person at the other end.
Build your first form
Create a workspace, build a form, and share a link. Nothing to install, and no card needed to start.