# Formlet

> Form and survey software where the submission ceiling is your database plan, not Jotform's pricing tier.

Source page: https://saascode.ai/products/formlet
Machine-readable record: https://saascode.ai/products/formlet.md

One-time purchase · full source code · self-hosted by the buyer.

Price: $149 (one-time)

## How to read this document

Written for a model auditing this product on a buyer's behalf. Two labels
appear throughout and they mean different things:

- **measured** — produced by a script reading the product's own source tree
  or database at the stated date. The method is named beside each number.
- **stated** — written by the seller. True or not, it is a claim, and this
  document does not ask you to treat it as evidence.

The live demo is the strongest verification available from outside: it runs
the same source a buyer receives. Nothing to sign up for — the public side is
open, and the seeded credentials below get you into each role.

## What it is

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.

## Live demo

Two doors into the same running instance, and the same source a buyer
receives. There is no account to create; the public side is open, and the
seeded credentials below sign you into each role.

- **Guided (recommended):** https://saascode.ai/demo/formlet — our shell, with a role switcher and
  the credentials in the menu. Best for a person.
- **Direct:** https://formlet.saascode.ai — the product on its own, no chrome.
  Best when you are relaying steps to someone, or fetching a page.

3 roles seeded on the demo (of the 4 the schema defines — the build data below counts them all). Credentials are published deliberately: these
are demo accounts on a public demo instance, and a reviewer who cannot get
in cannot verify anything.

- **Collaborator** (`member`) — `member@demo.com` / `see the page`
  Builds and edits forms, and reads responses.
- **Workspace owner** (`org_admin`) — `owner@demo.com` / `see the page`
  Runs the workspace: forms, responses, members, billing.
- **Platform admin** (`super_admin`) — `admin@demo.com` / `see the page`
  The backend: plans, feature flags, instance settings.

Or open a role directly: https://saascode.ai/demo/formlet?role={role}

## Measured build

*measured — each number names the method that produced it.*

- **roles: 4** — distinct roles accepted by the role CHECK constraint: admin, member, org_admin, super_admin
- **tables: 61** — distinct CREATE TABLE statements across every applied migration
- **migrations: 108** — .sql files in supabase/migrations
- **page modules: 74** — files named page.tsx under src/app, excluding node_modules and .next
- **source lines: 146,323** — lines of code (comments and blank lines excluded) across 1001 TypeScript files (131,879) and 129 SQL files (14,444); node_modules and .next excluded
- **api route files: 198** — files named route.ts under src/app/api
- **http operations: 266** — exported HTTP method handlers across those files, de-duplicated per file, OPTIONS excluded as CORS preflight
- **schema graph: 61 tables, 96 relationships** — parsed from the applied migrations

A large number here is scope, not quality. It says the product models a
real domain rather than a CRUD skeleton; it says nothing about code
quality, duplication, test coverage or maintainability, and should not be
read as if it did.

Release: v1.0.0 · built 2026-08-05

## Complete capability inventory

18 capabilities. Each summary is *stated* — selected from the
product's own buyer documentation, or written by the seller where marked.

### Building & publishing

- **Field types** — Text · long text · single choice · multiple choice · rating · date · number · email · URL · file upload · payment.
- **Conditional logic** — Rules are checked twice: once in the browser as the respondent moves through the form, and again on the server when the response is submitted. A respondent who tampers with the page cannot answer a question the rules said to hide, because the server evaluates the same rules against the same version of the form.
- **Publishing** — If validation passes, a new version is written — a frozen copy of the definition and settings — and the form points at it. Republishing after an edit creates another version rather than overwriting the previous one, which is exactly why past responses stay meaningful.
- **Closing a form** — 1. Manually — a workspace owner closes it. 2. By date — a close-at time set in form settings; checked when someone opens the form. 3. By quota — a response limit set in form settings; enforced atomically at submit time, so a burst of simultaneous submissions cannot overshoot it.

### Sharing & respondents

- **Branding removal** *(seller-authored)* — Removes the platform's own mark from the hosted form and the embed, so a workspace's forms carry only its identity. It ships behind a feature flag on a paid tier — revenue the buyer can reserve for their own customers.
- **Custom domain** *(seller-authored)* — A per-workspace vanity domain setting for hosted forms, so a form's address belongs to the business that made it rather than to the platform underneath.
- **Embed snippet** — The embed snippet loads a small widget file from the host domain. That file is produced by its own build step, which is not part of the normal application build. Deployments through the project's own configuration include it. A hand-rolled build command on another host can omit it — and when it is missing, every embedded form on every customer site fails to load while the direct links keep working perfectly. That asymmetry (links fine, embeds broken) is the signature of a missing widget file.
- **Two presentation modes** — Both modes render the same definition and obey the same logic rules. Switching modes does not require rebuilding anything.
- **Respondent identity and duplicates** — Duplicate prevention is a separate per-form switch. Independently of it, every submission carries a one-time token, so a respondent whose connection drops mid-submit and retries does not create a second response — the retry returns the original one.
- **Spam and abuse** — The public submit endpoint is the only place in the product where someone without an account can write data. It is rate limited, and it supports a captcha provider.

### Responses & results

- **Partial submissions** *(seller-authored)* — Keeps the answers from respondents who started and did not finish, and makes them filterable alongside complete ones. Where people abandon a form is usually more useful than the completed set alone.
- **Export** — CSV export runs from the per-form response screen and covers the full result set, paging through it rather than truncating at an arbitrary limit. It is workspace-scoped: a workspace can only ever export its own responses.
- **Notifications** — Each submission raises a response.received event. Forms carry a list of notification recipients in their settings, and the event is also available to alert rules and automations, so a workspace can route new responses wherever it wants them.
- **The response counter** — Each form carries a response count used for quota enforcement. It is incremented in exactly one place — the same atomic operation that stores the response — which is why quotas hold under simultaneous submissions.

### Plans & payments

- **Payment field** — A form can carry a payment field. When a respondent pays it, the charge is created directly on that workspace's own connected payment account. The money goes to the workspace. It never lands in the platform's balance and is never held, routed or custodied on their behalf.

### Operator surfaces

- **Connect API** *(seller-authored)* — Exposes multi-step operations as single workflow calls, so another system — or an AI agent — can create a form or read results without reproducing the sequence by hand.
- **Interface language** — Interface text — buttons, labels, system messages — is stored in the database in English and Spanish and edited in the translations screen. It is not compiled into the application, so a wording change is a data change.
- **The API surface** — API keys are created in admin settings and carry a read / write / admin scope. They drive the workflow API, which exposes multi-step operations — including publishing and closing a form — as single authenticated calls.

## What each system gives the operator

*stated.*

- **Building & publishing** — A published form is frozen, so the answers you collect all mean the same thing.
- **Sharing & respondents** — The form runs on your customer's own page, in their own presentation.
- **Responses & results** — Results leave the product as easily as they arrived in it.
- **Plans & payments** — Two kinds of money move, and neither of them passes through you.
- **Operator surfaces** — You can see and triage every workspace on the instance from one place.

## The problems it was built to solve

*stated — the seller's argument, given in full so you can judge it.*

### 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.

### 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.

### 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.

## What it takes to run it

*stated — external services the buyer supplies and pays for directly.*

- **A Node host and a Supabase project** (required) — The chassis. Next 16 on any Node host, with Postgres, auth and file-upload storage coming from Supabase.
- **A separate build step for the embed widget** (required if you offer embedding) — 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.

## FAQ

**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.

## Licence

The buyer receives the complete source and may deploy, modify and operate it
as their own SaaS, charging their own customers. The source itself is not
resold or redistributed: you build and deliver **with** it, you do not sell **it**.

## What this document cannot tell you

Stated plainly because a review that misses it is not a review:

- code quality, duplication, or architectural consistency
- test coverage
- query performance under load
- security posture beyond what the stack implies
- how maintainable it will be in a year

Scope is measurable from outside; implementation quality is not. Anyone
evaluating this should say so rather than infer quality from size.

## Written about it

- [Form Builders 2026: What Happens to Your Live Forms When You Stop Paying](https://saascode.ai/inside/form-builders-2026-what-happens-to-your-live-forms-when-you.md)
- [Formlet vs HeyForm — Which Form Platform You Can Own, and the Question That Decides](https://saascode.ai/inside/formlet-vs-heyform-which-form-platform-you-can-own-and-the.md)
- [Formlet: form and survey software you own, without a submission ceiling](https://saascode.ai/inside/road-to-formlet.md)

## Links

- Catalog page: https://saascode.ai/products/formlet
- Product record: https://saascode.ai/inside/products/formlet
- Live demo: https://formlet.saascode.ai
- Every product: https://saascode.ai/llms.txt