One engine / Any workflow
Forms
that don’t
feel like
forms.
Page form or guided flow. Same engine, same data, one build.
Question 1 of 3. What are you collecting?
What are you collecting?
A–D TO PICK · ENTER TO CONFIRM
BUILD → COLLECT → SEE
Every submission lands here.
No account. No setup. This is the same table your submissions land in.
HOW IT WORKS
Four steps. One afternoon.
From blank canvas to a report you can send to your boss.
BUILT WITH FORMNEST
Forms people actually finish.
Six of the twelve templates that ship with FormNest, drawn from the same schemas the product renders. Real fields — not screenshots.
TWO MODES · ONE SCHEMA
Two ways to ask the same questions.
Every form ships as a classic page and as a guided, one-question flow. Same fields, same answers, same report — you pick the feel, not the plumbing.
WHAT SHIPS IN THE BOX
Not just a form builder.
The parts around the form are the product, not add-ons.
Conditional logic
Ask only what the last answer made relevant.
File uploads
Photos, PDFs, signatures — attached to the response.
Scheduling
Offer real slots, not a text box asking for a time.
Per-form sharing
Every form gets its own link and its own audience.
Exports
Your data leaves whenever you want it to.
Custom reports
Group and measure what came in, then send it on.
Reports
Submissions roll up into a report you can send on.
Gaming & esports
Sign-ups for squads, rosters and brackets.
5of the templates that ship with FormNest are built for people running games — tournaments, tryouts, check-ins, clans and creator collabs. They run on the same engine every other industry here runs on, and they have their own corner of the site.
- Streamer Collab IntakeIntake · 7 fields
- Team Roster & Tryout ApplicationRecruitment · 8 fields
- Bracket Check-In ConfirmationRegistration · 6 fields
- Clan / Guild Membership SignupRegistration · 7 fields
- Tournament / LAN RegistrationRegistration · 7 fields
Two modes, one schema
Every one of them renders as a classic page form or as a guided, one-question-at-a-time flow. It is a setting on the same schema, not a second build.
Logic that branches
Conditional show/hide means a solo entrant is never asked squad questions, and a console player never sees PC-only fields.
Editable to the field
Each one is a real schema, not a screenshot — open it, rename fields, drop the ones you do not need, and publish it under your own event.
Straight up: the forms are real and the questions in them — gamer tags, ranks, platforms — are captured today with standard text, dropdown and multi-select fields. Purpose-built gaming field types do not exist yet, and the neon treatment on this band is a look made for these web pages, not a theme you can pick in the product. Both are things we intend to build, not things you can use.
See the gaming templates →WHO IT’S FOR
Built for every industry.
12 industries ship with templates today — examples, not limits. The engine has no opinion about yours.
SECURITY & COMPLIANCE
Boring where it matters.
The parts of the product nobody screenshots — handled the way your IT team would want them handled.
GDPR erasure
Right-to-erasure is a workflow in the product, not a support ticket.
Audit log
Who did what, and when — every admin action is recorded.
Org roles & permissions
Access is scoped per member and per form, not all-or-nothing.
Encryption at rest
Submissions are encrypted at rest and in transit.
MongoDB Atlas + Cloudflare R2
Managed, replicated storage for responses and uploads.
Data residency available
Choose the region your submissions live in.
NO ACCOUNT NEEDED YET
Describe the form you actually need.
We'll build it. Keep it if you like it.