Forms should feel like part of the product they serve.

Fillo keeps one form schema behind rendering, validation, conditional logic, responses, version history, exports, and delivery. Teams can work in a hosted editor or keep form structure in code. The React and DOM SDKs render native controls in the host application instead of putting the product flow inside an iframe.

The result is one place to review responses and files without asking the product team to build another validation service, upload pipeline, response table, and webhook retry system for every form.

Fillo was founded and is built by Jacob Funch in Denmark. He is the named maintainer of Fillo's open-source SDK, CLI, and MCP repository. Follow the work on GitHub, see his LinkedIn profile, or inspect the Fillo source repository.

Your app keeps its route, components, styling, account context, and after-submit behavior. Uploaded files can go browser-direct to storage you connect, while Fillo keeps the response, file metadata, and storage reference together. Fillo does not claim to replace your CRM, data warehouse, or design system.

Fillo is developed in Denmark and hosted in the European Union. Product claims are tied to behavior you can inspect in the documentation, SDK packages, public OpenAPI contract, and security pages. The service is in early access, so current limits and availability are stated directly in pricing and the legal pages.

Questions about the product or company? The contact page routes product, technical, privacy, security, and abuse questions to the right place. Official technical entry points are collected in the Fillo developer resource index.