Use your components, not an iframe.
Keep the form on your route and let your design system own every visible control.
app.acme.co/onboarding/check-inOnboarding check-in
Tally alternative for in-product forms
Compare Tally with Fillo when a hosted form moves into your app: native controls in your own route and a schema shared across validation and responses.
When an embed stops being enough
Tally is quick for a link, popup, or iframe. Fillo is for the point where the form needs your components, signed-in context, and product behavior.
Edit once. Validate everywhere.
Stable field IDs carry from the rendered form through server checks, responses, and exports.
Know who answered inside your app.
Attach the account and route without making the person repeat details you already know.
Put uploads where your team works.
Connect your own storage and keep each file attached to the response that brought it in.
Tally is a hosted builder. You share its forms as a link, popup, or iframe. Fillo renders the form inside your app and handles validation, uploads, and responses behind it.
Which should you choose?
When Fillo fits
- The form has to render as native controls inside an existing product route.
- Your component system should own layout, focus behavior, and field rendering.
- The schema belongs in code, or needs to be shared across rendering, validation, responses, and exports.
- Signed-in account identity should travel with the response.
- Uploaded files must go directly to Google Drive, Box, or S3-compatible storage such as Amazon S3 or Cloudflare R2 that you connect.
When to stay on Tally
- The form never touches your product — a hosted link or popup does the job.
- It depends on Tally's payments, custom domains, or non-numeric calculations. Fillo doesn't have those today — its calculated fields handle numbers only.
- Nobody on the team is going to touch code for this form, and the current integrations already work.
Key differences
| Decision | Fillo | Tally |
|---|---|---|
| Rendered form | Native React or DOM controls, fully headless UI, or a hosted page | Tally-hosted form in standard, popup, or full-page embeds |
| Authoring | Dashboard or typed defineForm() schema | Document-style visual builder |
| Application identity | Optional server-verified respondent ID from your app | Hidden values and Tally's duplicate-submission controls |
| File destination | Browser-direct upload to storage connected by your workspace | Files collected and managed through Tally's service and plan rules |
| Calculations | Numeric calculated fields: totals and derived values, recomputed on the server | Calculations are a documented Tally feature |
| Payments | No payment field today | Payment collection is a documented Tally feature |
| Pricing shape | Fillo plans limit completed responses; renderer access is included on both plans | Tally advertises unlimited forms and submissions within its fair-use policy |
Check Fillo plans and limits and Tally's current pricing before comparing costs for a live form.
What you would need to change
| Existing Tally form | Expected work |
|---|---|
| Questions, required fields, and a single completion screen | Rebuild the fields, publish, and replace the link or embed |
| Pages, hidden values, logic, numeric calculations, uploads, and destinations | Map each rule and setting, rebuild calculations as calculated fields, connect storage, and test every path |
| Payments, custom code, non-numeric calculations, or automations built around Tally payloads | Redesign those parts and update downstream consumers before cutover |
Old Tally submissions don't become Fillo responses. Export them and keep the archive under its existing access and retention policy.
Next step
Open the editor and rebuild one real form first. If it works for your team, read Migrate from Tally for the full checklist.
Related
- Migrate from Tally: Plan the rebuild, archive, cutover, and rollback.
- Embed a Fillo form: Choose a native React, DOM, or hosted form.
- Author forms in code: Keep a typed Fillo schema in your repo.
- Compare form tools: Find the right starting point for the form you need.
- Headless form builder: See how a Fillo form works inside your app.
- Fillo plans and limits: Check response, branding, and upload limits.
Updated