Fillo Review (2026): Pricing, Features & Honest Verdict

Fillo is headless form infrastructure for product teams: you build the form inside your own React app, and Fillo runs the validation, uploads, responses and delivery behind it. Best for developers who keep shipping one-off forms. Price: from $0, then $39 a month. Free plan: yes. Rating: 7.5/10.

What is Fillo?

Fillo is a form backend that renders inside your product instead of beside it. Its React and DOM SDKs draw native HTML controls in your own components, so a form inherits your route, your CSS and your account context. No iframe, no borrowed font, no flow that leaves the app halfway through. Behind that rendering layer sits one schema covering validation, conditional logic, file uploads, response storage, version history, CSV export and delivery into webhooks, Google Sheets, Notion, Slack, HubSpot and Zapier.

It is operated by Jafu ApS in Denmark and was founded by Jacob Funch, who also maintains the open-source SDK. The npm package @usefillo/react is MIT licensed, first published on 15 June 2026, and now sits at version 0.19.0 across 24 releases. Both the app and your responses are hosted in the EU. Uploaded files barely touch Fillo at all: they go browser-direct to Google Drive, Box, Amazon S3 or Cloudflare R2, up to 5 GB per file, and Fillo keeps only the durable reference next to the response.

We found it on Product Hunt on 3 September 2026, launched under the line “build forms into your product with your coding agent.” That framing undersells it. The agent bootstrap is a nice touch, but the reason to care is the rendering model.

What Are Fillo’s Key Features?

Forms that render as your own components

You write <Fillo.Form id="support"> with Fillo.Email, Fillo.Phone and Fillo.Rating children, and Fillo renders real inputs into your DOM. Start with the default renderer and restyle it, swap individual fields for your own components, or drop to headless hooks with FilloProvider and createFormController and own the entire layout. It works with React, Vue, Svelte, Astro and plain browser apps. Crucially, every one of those embed methods is on the free plan. Nothing about the rendering path is gated behind payment, which is unusual for this category.

Files go to storage you already own

Connect Google Drive, Box, S3 or R2 and file bytes upload browser-direct to your bucket, resumable, up to 5 GB per file. Fillo stores the response and the file reference together but never becomes the custodian of your uploads. That has a pleasant side effect the vendor points out itself: if you cancel, the files were never on a Fillo plan in the first place, so there is nothing to migrate.

Responses carry context and keep their schema

Attach the account, user, plan, page or product state to a submission without asking the respondent another question. The account email, company, plan tier and route travel with the answer, invisible to the person filling it in. Version history is handled properly too: you can edit a published form while it keeps collecting, and old responses keep the schema context they were captured under. Anyone who has renamed a field in a form tool and watched a year of exports turn to mush will understand why that matters.

Setup from the coding agent you already run

Paste one prompt into Claude Code, Cursor, Copilot, Windsurf or any MCP client, or run npx @usefillo/cli@latest agent bootstrap. The agent asks what the form should collect, builds it into your app matching the existing route and UI, and hands back a live preview. Fillo is honest about the limit here: its own FAQ says the agent can do this “mostly,” and that you still claim the workspace yourself and connect OAuth accounts by hand.

How Much Does Fillo Cost?

Fillo starts at $0 with no time limit and no card. The Free plan includes 200 completed responses a month, unlimited visual-builder forms and up to 200 code-defined forms per workspace. The paid plan, called Everything, is free for 30 days and then EUR 35 or $39 a month for 5,000 responses, with extra responses at EUR 0.007 or $0.008 each.

Run the arithmetic and something interesting falls out. EUR 35 divided by 5,000 responses is EUR 0.007 exactly, which is the published overage rate to the last decimal. In euros, the subscription buys no volume discount at all: the 5,000th included response and the 5,001st cost the same. What the EUR 35 actually buys is the option to turn off the “Powered by Fillo” badge and priority email support. That is a clean, honest ladder, but you should know that is what you are paying for.

The dollar side does not reconcile as neatly. $39 divided by 5,000 is $0.0078, while the dollar overage is $0.008, so a response above the cap costs 2.6% more than a response inside it. The two prices also imply two different exchange rates: EUR 35 to $39 is 1.114, while EUR 0.007 to $0.008 is 1.143. Rounding, almost certainly. Still, EUR buyers get the flat rate and USD buyers get a small step up.

Credit where it is due: Fillo works its own examples on the pricing page and they are correct. At 5,001 responses your total is EUR 35.01 or $39.01. At 6,000 it is EUR 42 or $47. We recompute vendor charts constantly and most of them fail. This one holds.

The real cliff is between the plans. Free stops at 200 responses and there is no middle tier, so response 201 costs you EUR 35. At exactly 201 responses a month you are paying EUR 0.174 each, roughly 25 times the marginal rate you would pay at scale. Fillo is cheap once you are past a few thousand responses and expensive in the gap just above the free cap.

Against rivals, that $39 looks strong. Basin, the closest form-backend comparison, prices its Pro tier at $40.83 a month billed yearly for 5,000 submissions. Formbricks charges $74 a month for 2,000 responses and $325 a month on its Scale tier for 5,000, which is more than eight times Fillo’s price for the same volume. Formbricks is a survey platform rather than embedded infrastructure, so it is not a like-for-like swap, but on cost per response Fillo wins clearly.

What Fillo Publishes, and Where It Falls Short

Most of Fillo’s documentation is excellent. Prices and allowances are dated (“last updated Aug 27, 2026”), the terms carry the same date, and the FAQ answers the awkward questions directly, including what happens to your data when you cancel.

Three things do not hold up. First, the homepage FAQ says “Temporary Fillo transit storage is capped and short-lived; the current limits are published on the pricing page.” They are not. We read the entire pricing page and it contains no transit-storage limit, no retention window and no cap in megabytes or gigabytes anywhere. A pointer to a number that does not exist is worse than no pointer.

Second, the About page invites you to “inspect the Fillo source repository” and links to github.com/jacobfunch/fillo. That URL returns a 404. The real repository is jacobfunch/usefillo, it is MIT licensed and last pushed on 26 August 2026, and it currently has zero stars. The npm package is real and public, so the open-source claim stands. The link on the page that proves it does not.

Third, and most important if you are putting a shipped product behind this: Fillo’s own terms describe the service as “currently in early access (beta),” state that it is provided “without a formal service-level commitment,” and cap total liability at the greater of EUR 100 or the fees you paid in the previous 12 months. For a $39 customer that ceiling is EUR 100. You are trusting a Danish one-person company with the intake path of your product, and the contract says exactly how much recourse you have if it breaks.

Who is Fillo Best For?

Use Fillo if you are a product developer who keeps rebuilding the same plumbing: another validation layer, another upload pipeline, another response table, another webhook retry. That is precisely the surface it replaces, and it replaces it without an iframe or a design-system fight. It suits onboarding flows, support intake, feedback widgets, approval steps and file requests that belong inside an app you already ship. EU hosting, a DPA and sub-processor docs on both plans make it an easy sell to a European buyer.

Skip Fillo if you want a standalone form you can send as a link, because a hosted builder does that better and cheaper. Skip it if you need a survey and analytics platform rather than form infrastructure. Skip it if your compliance team will not accept a beta with no SLA and a EUR 100 liability cap on a production intake path. And skip it if your volume lands between 200 and roughly 1,500 responses a month, where the per-response cost of the paid plan is at its worst.

Best Fillo Alternatives

Basin is the nearest match: a form backend you post your own markup to. Its rendered ladder runs Free at $0 for 1 endpoint and 50 submissions a month, Starter at $12.50, Growth at $24.17, Pro at $40.83 for 5,000 submissions and Agency at $108.33, all billed yearly. Basin gives you more granular tiers and a longer track record. Fillo gives you an SDK, versioned schemas and file uploads into storage you own.

Formbricks is open source and self-hostable, with a Hobby tier at $0 for 250 responses a month, Pro at $74 for 2,000 and Scale at $325 for 5,000, hosted in Frankfurt. Choose it if you want to run the whole thing yourself or if surveys and segmentation matter more than embedding. It is far more expensive per response on the cloud plans.

Tally is the free-forever hosted builder, and its own pricing page advertises unlimited forms and unlimited submissions on the free plan. It is a different product: you get a Tally-hosted page rather than a form inside your React tree. For a link you paste into an email, Tally wins on price and nothing else comes close. For a form that has to look like the rest of your app, it is not in the running.

Final Verdict: Is Fillo Worth It?

Fillo does the hard part well. Rendering native controls in your own components, sending files straight to your own bucket and versioning response schemas are all things that take a team a month to build badly. The pricing is transparent to the cent, the vendor’s own worked examples are correct, and every embed method including headless is free. At $39 for 5,000 responses it undercuts a survey platform charging $325 for the same number.

What holds it back is maturity, not design. This is a beta run by one person in Denmark, with a source link that 404s, a repository with no stars, no SLA and a EUR 100 liability ceiling. That combination is fine for an internal tool, a feedback widget or a side project. Think harder before it sits on the signup path of a product with real revenue. Start on the free tier, watch it for a month, and upgrade once you trust it. Recommended for developers, with your eyes open about the company behind it.