Formlet
Form and survey software where the submission ceiling is your database plan, not Jotform's pricing tier.
Formlet is a form and survey builder for teams. People build a form by dragging fields onto a canvas, wire conditional logic so later questions react to earlier answers, publish it, share the link, and then read and export what comes back.
Every answer you collect was given against the same set of questions.
Forms get edited while they are live. Somebody rewords a question, adds an option, removes one that was confusing — and the responses collected before and after are now answers to different questions sitting in the same spreadsheet. Nobody notices at collection time. It surfaces at analysis, when a column has values that no longer correspond to any choice on the form, and there is no way to tell which responses came from which version. The dataset does not fail loudly; it just quietly stops meaning anything.
- Publishing
- Conditional logic
A respondent's payment settles in your customer's own account, directly.
The moment a forms platform collects money on behalf of its users, it becomes a payments business with all the obligations that implies. Refunds and chargebacks arrive against the wrong entity, funds sit somewhere in between, and a dispute between a workspace and its own respondent turns into a support ticket for the operator. Most platforms only discover the shape of this after the first refund request, when the question of whose money it was turns out to have no clean answer.
- Payment field
The same definition runs as one question per screen or a single page.
Presentation is not cosmetic on a form: a long survey answered one question at a time gets finished, and a short intake broken across nine screens gets abandoned. Teams that guess wrong usually cannot fix it, because switching presentation means rebuilding the form and losing continuity with everything collected so far. So the wrong format stays, the completion rate stays where it is, and everyone assumes that is simply what response rates look like.
- Two presentation modes
- Embed snippet
Each field has its own configuration — maximum length, choice options, rating scale, accepted file types and count, minimum and maximum for numbers, amount and currency for a payment field.
Question and option text is workspace content, not interface text. It is stored with the form and displayed exactly as written. It is not part of the English/Spanish interface translation set, which covers buttons, labels and system messages only. A form's own display language is a per-form setting.
Two kinds of rule, both driven by an answer the respondent already gave:
Logic is deliberately limited to adaptive data collection. There is no score, no accumulator and no branching outcome — see the overview section for why.
Publishing runs a validation pass before it will accept the form:
A draft form has no version and no public link. It is invisible outside the workspace.
Three ways a form stops accepting answers:
A closed form still serves its link, showing a closed-state screen rather than an error.
You receive this. It ships behind a feature flag and sits on the Pro, Team tier as configured, so it is revenue you can reserve for your own paying customers.
You receive this. It ships behind a feature flag and sits on the Pro, Team tier as configured, so it is revenue you can reserve for your own paying customers.
Every form is published in one of two modes, chosen in form settings and changeable at any time:
Per form:
The captcha fails closed once configured — a submission arriving without a valid token is rejected. Until a captcha is configured in the integrations settings, that endpoint is open to automated traffic. If someone reports a flood of junk responses, configuring captcha is the first thing to check.
You receive this. It ships behind a feature flag and sits on the Pro, Team tier as configured, so it is revenue you can reserve for your own paying customers.
Deleting a response does not decrement that counter. It is a ledger of how many submissions a form has accepted, not a live row count. A form with a quota of 100 that received 100 and had 10 deleted is still closed. If someone needs the counter reset, that is a deliberate administrative act, not a side effect of deleting rows.
No plan caps, meters or displays a response limit. Response quotas are a per-form tool a workspace chooses to use, never a billing constraint.
How it works in practice:
1. The workspace connects its own account from its payment settings screen. 2. The payment field only becomes usable once that account reports it can accept charges. 3. On submit, the response is stored before the payment is attempted, so an abandoned checkout leaves a recoverable record instead of a lost submission. 4. Confirmations arrive by webhook, on a separate endpoint with separate credentials from Plane 1, and are deduplicated so a replayed webhook cannot double-count.
Platform revenue from Plane 2 is a commission on Free-tier workspaces only — 5%, taken as an application fee at charge time, and 0% on paid tiers.
Three honest limits on Plane 2 in this release:
Say "zero platform commission" on paid plans — never "zero fees". The workspace still pays its processor's standard rates.
You receive this. It ships behind a feature flag and sits on the operator-set per plan tier as configured, so it is revenue you can reserve for your own paying customers.
The failure mode to recognise: if a screen shows something like "Thanks Body Generic" where a sentence should be, that is a missing translation row being humanized on the fly, not a broken page. Form question text is unaffected — that belongs to the workspace, not to the interface.
In this release the workflow API ships switched off and the agent-tool bridge is not enabled on any plan. Both are enabled per plan or per workspace on demand. Note also that the per-key rate limit depends on Redis being configured; without it that limit is not applied at all.
The platform underneath the product — counted in this product's own source, not claimed from a template. Where a row carries a list, open it to read the names behind the number.
Coinbase
dLocal
Flutterwave
Komoju
Mollie
NOWPayments
Opn
Paystack
ActiveCampaign
Customer.io
Segment
Canny
Amplitude
Custom Head Scripts
Pushover
Twilio SMS
Crisp
Tawk.to
Monday.com
fal.ai
Axiom
hCaptcha
Freshsales
Pipedrive
Pabbly Connect
AWS S3
MuxHover a table to isolate what it touches; click one to read its relationships. The big nodes are what everything else hangs off. organizations is referenced by 48 tables because every single record in this product belongs to an organization, and that is what makes tenant isolation a property of the database rather than something the application has to remember on every query.
all 61 tables, as text
active_boosts · admin_notifications · analytics_daily · analytics_events · analytics_funnels · announcement_dismissals · announcements · api_key_logs · api_keys · assistant_actions · assistant_conversations · assistant_messages · assistant_usage · audit_logs · automation_log · automation_templates · credit_balances · credit_transactions · currencies · data_exports · data_imports · faq_categories · faq_items · feature_flags · form_response_rollups · form_versions · forms · inbound_webhook_events · inbound_webhooks · languages · marketing_audience_members · marketing_audiences · notification_log · notification_rules · notifications · org_payment_connections · organization_limit_overrides · organizations · payment_attempts · plans · platform_secrets · platform_settings · processed_events · product_purchases · products · provider_prices · push_devices · report_templates · responses · roles · scheduled_tasks · seo_meta · subscriptions · theme_page_sections · theme_section_library · theme_sections · translations · user_sessions · users · webhook_logs · webhooks
The chassis, and anything particular to this product. 1 required, 1 optional.
The chassis. Next 16 on any Node host, with Postgres, auth and file-upload storage coming from Supabase.
The embed snippet loads a widget file produced by its own build, not by the normal application build. Skip it and hosted forms keep working while every embedded one silently stops — the one part of shipping this a buyer could not guess.
Already built — plug and play
Every provider integration in this list ships wired into the product. You bring your own keys, connect them in the admin, and go live — there is no integration code to write. Nothing is resold through us: the ongoing cost is whatever these providers charge you. Capabilities marked plan-gated elsewhere on this page unlock by plan, not by extra code.
What exactly do I receive after purchase?
The complete source repository behind the live demo — 146,323 lines across the application and its database, 61 tables defined by 108 migrations that the shipped scripts apply for you, plus the seed data, the demo accounts and the setup documentation. Not a subset and not a scaffold: the same code that runs the demo you just used.
Is the live demo the same product whose source I receive?
Yes. The Formlet demo runs the delivered release (v1.0.0), and the build figures on this page are measured from that same source — not from a showcase build kept separately.
Can I test every account role before buying?
Yes — all 3 of them: Collaborator, Workspace owner, Platform admin. Each one is seeded in the live demo and reachable from the role board above, so you can inspect the product from the customer's side, the agent's side and the administrator's side before you decide.
Is this a complete product or a starter template?
Complete. 74 page modules and 266 HTTP operations, with authentication, roles, billing, an administration panel, background jobs and seeded demo data all wired and running. A template gives you the shape of an application; this is one you can deploy and start operating.
Can I rebrand and modify it?
Yes, without asking. The name, identity, copy, styling and code are yours to change. Rebranding and operating it as your own service is exactly what the licence is for.
What does the licence allow?
A perpetual, worldwide, non-exclusive, non-transferable licence to the product you bought and to every update released for it. The Standard licence covers one business — yours. If you deploy for clients, the Client licence covers up to five. You can modify it, rebrand it, deploy it and charge your own customers.
Can I resell the source code?
No. Reselling, redistributing, sublicensing or giving away the source itself is not permitted under either licence. You build and deliver products with it — the code stays with you.
What services and ongoing costs are required?
You bring your own accounts, so we never mark anything up and there is no ongoing cost to us beyond the purchase. Required: A Node host and a Supabase project, A separate build step for the embed widget. Optional: none. The table above says exactly what stops working without each one; most have usable free tiers at low volume.
How difficult is deployment?
Two ways, and most buyers use the first. The installer in your saascode dashboard walks it: you create free accounts at Vercel and Supabase, connect them, and it provisions the database, applies 108 migrations, seeds the data, deploys and verifies the result — you watch the steps go green. Or take the source and do it yourself with the shipped scripts and docs, which is the same sequence run by hand.
What updates and support are included?
Updates to that product for as long as we maintain it — no renewal fee and no expiry date on your access. Support covers download problems, defects in the code as shipped, questions about what the product does and how it is structured, and licence questions. It does not cover debugging your own modifications, building features for you, or setting up your hosting and third-party accounts.
Why does a complete codebase cost $149?
Because it was built once and is distributed many times. SaaSCode builds each product and ships the same finished release through the catalog, so the price reflects repeatable distribution — not a reduced codebase, an unfinished template, or what the same work would cost commissioned.
Do I need to be a developer?
No, for the normal path. You create free accounts at Vercel and Supabase, connect them to the installer in your saascode dashboard, and it does the deployment for you — provision, migrate, seed, deploy, verify. What it asks of you is creating two accounts and copying a token, not writing code. If you would rather deploy it yourself, or host it somewhere else, the full source and the scripts are yours to do that with. Running the product day to day needs no technical skill at all: that happens through its own interface, which is what the demo shows.