Fillo
Start with a prompt

Forms inside your product, with your UI.

Tell your agent what you need. It builds a Fillo form that renders native in your app and sends files to your storage. You review and publish.

agentBUILDING 
Works with your agent
Claude CodeCursorCopilotWindsurfAny MCP client
Your agent does the work.
1
Copy the prompt.
One prompt, any coding agent. It installs the Build-with-Fillo skill and knows what to do.
Add a native Fillo form to my app. Start with: npx @usefillo/cli@latest agent bootstrap — it creates a workspace and installs the Fillo skill (ask me for an email if it needs one). Then build the form I describe and take it live. I'll get a link to claim it. If you get stuck, Fillo's agent docs are at https://fillo.so/agents.md.
The same prompt works in Claude Code, Cursor, Copilot, any coding agent.
2
It builds and goes live.
Schema, native render, and storage wiring — built and live on a preview in minutes.
3
You claim it.
Click the emailed link and it's yours. Your first response lands in your workspace.
Product forms need more than fields.
Files, context, exports, drop-off, and edits stay connected to the same form.
SupportForm.tsx
import { Fillo } from "@usefillo/react";

export function SupportForm() {
  return (
    <Fillo.Form id="support" title="Support request">
      <Fillo.Email id="email" label="Work email" required />
      <Fillo.Phone id="phone" label="Phone" />
      <Fillo.Rating id="urgency" label="How urgent?" max={5} />
    </Fillo.Form>
  );
}
Powered by Fillo
no <iframe>
Not an iframe with limited styling.
Use the default renderer, bring your own CSS, or replace a field when the flow needs something custom.
Choices, uploads, phone numbers, ratings, signatures, hidden values, and follow-ups.
Ask less. Still know enough.
Send app context with each response, without adding more fields.
jane@acme.coAcmePro planAdmin/settingsEU
Attached to the response, invisible to the user.
See where people stop.
Spot the step that needs fixing.
Large file uploads.
Browser-direct to storage you connect.
Google DriveBoxAmazon S3Cloudflare R2
up to 5 GB per file, resumable
Change the form without breaking old answers.
New versions can change fields; old responses stay readable with their original context.
Works with the tools your team already uses.
ZapierGoogle SheetsNotionSlackGoogle DriveBoxAmazon S3Cloudflare R2CSV exportWebhooksEmail
Built in Denmark. Hosted in the EU.
Frequently asked questions
When should we use Fillo?
Use Fillo when the form belongs inside your app rather than on a standalone link: onboarding, support, feedback, applications, file requests, and approvals.
Can my coding agent set Fillo up end to end?
Mostly, and the gap is closing. Your agent installs the Build-with-Fillo skill, builds the form, and takes it live. You claim it to keep it, and today you still verify your email and connect storage for file uploads yourself.
Do I have to use an agent?
No. The visual editor gives you drag and drop, and forms can be defined and synced from code. The agent path is simply the fastest way to a live form.
Does Fillo render in an iframe?
No. The React SDK renders native controls, so you can use the default renderer, your own CSS, custom fields, or headless hooks.
Where do uploaded files go?
Files can go to storage you connect, such as Google Drive, Box, Amazon S3, or Cloudflare R2. Fillo keeps the response itself and a reference to each file.
Where is Fillo hosted?
Fillo runs on EU servers, and your form responses are stored there too. Uploaded files go to the storage you connect.
What happens when a form changes later?
Published forms can keep collecting while you edit. New versions can change fields, and older responses remain readable with their original context.
What does the team get after someone submits?
A response workspace with answers, files, hidden context, exports, notifications, webhooks, and integrations connected to the same submission.
Your agent can ship it today.
Or open the editor.