Compare
How we compare, without the pantomime.
NumoForms is a survey builder with 16 question types, conditional
logic, scoring bands, save-and-continue resume links and per-survey partner
branding, with survey content and responses stored in London
(eu-west-2). Typeform, Jotform, SurveyMonkey and Google Forms
are all mature products with genuine strengths, and for a good number of
jobs one of them is the right answer. These pages set out where the
difference actually lies.
Every statement about another vendor on this site is taken from that vendor’s own public pages, linked and dated. Where we are not certain, we say so and point you at their documentation rather than guessing.
The four comparisons
vs Typeform
Their strength: Best-known respondent experience: one question at a time, video questions, adaptive flows.
Our angle: We ship a conversational layout too, plus classic and paged, and keep the data in London.
vs Jotform
Their strength: A very large public integrations directory, spanning payments, storage, CRM and automation.
Our angle: Signed webhooks rather than a directory, plus deeper survey logic, scoring and UK residency.
vs SurveyMonkey
Their strength: SurveyMonkey Audience — a paid respondent panel with demographic and behavioural targeting.
Our angle: We do not sell respondents. We are the instrument, not the sample.
vs Google Forms
Their strength: Costs nothing beyond the Google account most people already have.
Our angle: Matrix, ranking, scoring bands, save-and-continue, per-survey co-branding, UK storage.
Statements about other vendors on this page summarise those vendors’ own public pages, checked July 2026. Each comparison links the source it was taken from and dates it.
What we are actually different at
Four things are genuinely unusual about NumoForms, and they are the only four we would ask anyone to switch for.
UK data residency as the default, not an enterprise upsell
Survey content and responses sit in Supabase’s London region
(eu-west-2), encrypted in transit with TLS and at rest with
AES-256, on every account. Several of the platforms below do offer
regional hosting, but typically as an enterprise-tier arrangement — check
their current pricing pages. Our sub-processor
list is published, and our security page
describes the actual controls rather than badges we have not earned.
Partner logos per survey, not per account
Collaborator branding is attached to the individual survey, so one workspace can badge a different local authority, funder or partner on each piece of work without maintaining a separate account for each. This is deliberately kept apart from the organisation brand kit — see per-survey co-branding.
Save and continue on long surveys
A resume link keyed on a 24-character token lets a respondent leave and
come back. Partial answers are stored in a table with no row-level
security policies at all, reachable only through
SECURITY DEFINER functions. If your survey runs to eighty
questions, save and continue
is the difference between a response and an abandonment.
Close dates and caps enforced by the database
Responses insert straight from the browser, so a close date or response cap policed only by the interface is not a control. Ours is a database trigger: past the date or over the cap, the insert is refused and the respondent sees your custom closed message.
What we do not do
If any row here is a requirement, one of the four platforms in these comparisons is a better fit than we are, and you should buy it.
| Not available | Detail |
|---|---|
| Zapier app or Google Sheets connector | Not built. Signed webhooks are, so anything that accepts a webhook works. |
| Payment collection in forms | Not built. |
| Qualified electronic signatures (QES) | Not built. Simple electronic signatures are — typed or drawn, stored with the agreement text and a hash of it. |
| SSO / SAML | Not built. Accounts are email-based, with owner / admin / member roles. |
| Multi-step approval chains | Not built. Single-step approval is. |
| CAPTCHA | Not built. Spam protection is: a honeypot, a dwell-time floor and a rate limit, all enforced by a database trigger. |
| Offline or kiosk mode | Not built. |
| Mobile apps | None. The builder and the respondent view are web only. |
| Tables or spreadsheet view of responses | Not built. CSV export is. |
| AI analysis of responses | Not built. The AI drafts surveys; it does not read the answers that come back. |
Common questions
How does NumoForms compare to Typeform, Jotform, SurveyMonkey and Google Forms?
NumoForms stores survey content and responses in London
(eu-west-2), attaches partner logos per survey rather than
per account, enforces close dates and response caps with a database
trigger, and offers save-and-continue resume links on every survey. The
four incumbents are mature products with real strengths — Typeform for
respondent experience, Jotform for integration breadth, SurveyMonkey for
its research panel, Google Forms for costing nothing extra. Check each
vendor’s current documentation for their own feature set.
What does NumoForms not do?
NumoForms has no Zapier app or Google Sheets connector, no SSO or SAML, no payment collection in forms, no qualified electronic signatures, no multi-step approval chains, no offline or kiosk mode and no mobile apps. If any of those are required, one of the larger platforms is the better answer.
Related reading
The product overview covers the builder end to end. All 16 question types lists what you can actually ask, conditional logic explains how questions are hidden, and local government is the sector page where UK residency and per-survey partner branding matter most. Pricing is not yet set — the pricing page says so plainly.
Judge it on your own survey.
A comparison table only takes the decision so far. Rebuild the survey you already run, turn on the logic and the scoring, and see whether the difference is one that matters to your work.
- Sixteen question types, conditional logic and scoring bands
- Survey content and responses stored in London
- Save-and-continue resume links on every survey
