Fillo

Fillo is built for product teams that want forms to look and behave like part of their application. A coding agent can generate the integration, while the product team keeps control of the route, components, CSS, and design system. The vendor says its renderer uses no iframe and supports React plus framework-agnostic browser applications, with Vue, Svelte, and Astro named on the homepage. Teams can start with default controls, replace individual fields, or use headless composition. That makes Fillo materially different from a hosted survey link: it handles validation, uploads, responses, versions, and delivery behind a form rendered inside the product.

Features and pricing

Both plans include editor-built and code-defined forms, all field types, conditional logic, answer piping, multi-page forms, URL prefill, hidden fields, signed webhooks, CSV export, response history, and integrations with Google Sheets, Notion, Slack, HubSpot, and Zapier. Files can go to connected Google Drive, Box, or S3/R2 storage. Identity features include signed-in respondent identification, optional server verification, and prefilling prior answers. Save-and-resume, response limits, drop-off recovery, funnel insights, and versioned response history address operational needs that usually require custom backend work. Product teams already using Notion, Slack, or HubSpot have direct delivery options.

Free is €0 with no card or time limit. It includes unlimited visual-builder forms, up to 200 code-defined forms per workspace, and 200 completed responses per month. Everything includes a 30-day trial and costs €35 per month, displayed as $39 per month in USD. It raises the allowance to 5,000 responses, then charges €0.007 or $0.008 per extra response. At 8,000 monthly responses, the published euro pricing works out to €56: €35 plus €21 for 3,000 overage responses. The vendor marked these allowances as updated August 27, 2026.

Honest assessment

Fillo's strongest advantage is the combination of native rendering and managed form operations. A team can build onboarding, cancellation, vendor-access, billing-change, waitlist, or in-product feedback flows without accepting an iframe's styling constraints. EU hosting, allowed browser origins, encrypted provider tokens, DPA information, and signed webhooks are useful controls. The free plan exposes the full product rather than withholding core field types. A coding workflow can pair Fillo with Cursor or GitHub Copilot Agents to accelerate implementation.

The trade-offs are concrete. Fillo is a newer specialist dependency in a critical data-collection path. Free permits only 200 completed responses monthly, and paid overages make cost sensitive to traffic. EU hosting may not satisfy every residency requirement. Teams still own accessible labels, validation copy, abuse prevention, webhook consumers, connected-storage permissions, and deletion workflows. The 200 code-defined-form workspace limit applies even though visual-builder forms are unlimited. No first-party MCP support was verified, so builders should treat ordinary coding-agent compatibility as distinct from an MCP server.

Practical evaluation

Pilot one real flow with at least 100 test submissions. Include file uploads, conditional branches, resumed drafts, duplicate respondents, webhook retries, a form-version change, CSV export, and a connected destination. Measure completion rate, p95 submission latency, webhook delivery success, accessibility defects, reviewer time, and styling effort. Verify data retention, subprocessor terms, origin restrictions, storage-token encryption, export completeness, and incident support. Fillo is a strong fit when native UI and managed submissions matter more than owning every backend component; a simple static contact form may not justify another vendor.