Skip to main content

Never build another form by hand.

See what Fillo handles

Let your coding agent build it into your product. Fillo handles the infrastructure behind it: validation, uploads, responses, versions, and delivery.

Report product feedback

Capture the page, user feeling, and a screenshot in one response.

Powered by Fillo

Support request

Ask for the evidence support needs before the ticket is routed.

Powered by Fillo

Approval vote

A simple decision form in the flow.

Powered by Fillo

Article feedback

A tiny feedback form inside docs or help.

Powered by Fillo

Release confidence

Ask a short readiness question before a rollout.

WaitShip
Powered by Fillo

Beta access

Collect the right context before enabling a new feature for a customer.

Powered by Fillo

Invite a workspace

Turn account setup into a structured product flow.

Powered by Fillo

Data export request

Collect identity, scope, and delivery details before support starts the export.

Powered by Fillo

Cancellation review

Capture reason, timing, and handoff details before the account is closed.

Powered by Fillo

Feature priority

Let an account rank what should happen next.

  1. 1Audit logs
  2. 2SSO
  3. 3CSV exports
  4. 4Custom roles
Powered by Fillo

Billing change

Let customers request a plan or invoice update from inside settings.

Powered by Fillo

Vendor access request

Collect the details security needs before approving a vendor.

Uploads are unavailable in this render-only preview
Powered by Fillo

Real forms, rendered by @usefillo/react.

Works from the coding agent you already use

Claude CodeCursorCopilotWindsurfAny MCP client

One form. Everything behind it stays connected.

Own the route, UI, and product context. Stop rebuilding rules, uploads, response tooling, and delivery every time the product needs another form.

SupportForm.tsx
import { Fillo } from "@usefillo/react";

export function SupportForm() {
  return (
    <Fillo.Form id="support">
      <Fillo.Email id="email"
        label="Work email" />
      <Fillo.Phone id="phone"
        label="Phone" />
      <Fillo.Rating id="urgency"
        label="How urgent?" />
    </Fillo.Form>
  );
}
Powered by Fillo
no <iframe>

Your interface stays yours.

Your route and components render the form directly—no iframe, foreign font, or detached flow. Start with the default controls, replace individual fields, or own the entire layout.

React, Vue, Svelte, Astro, or plain browser apps. Your CSS and design system stay in charge.

Every answer carries context.

Attach the account, user, plan, page, or product state without turning each one into another question.

jane@acme.coAcmePro planAdmin/settingsEU

Attached to the response, invisible to the user.

Files can go straight to storage you own.

Browser-direct to connected S3, Drive, Box, or R2—multiple large files included. Fillo keeps each durable file reference attached to its response.

Google DriveBoxAmazon S3Cloudflare R2

up to 5 GB per file, resumable

A response becomes useful work.

Review answers, files, context, and delivery state together—then export them or send them into the systems that act next.

  • Response #1042 · accepted
  • Account context · attached
  • Webhook + HubSpot · delivered

Change it without breaking old answers.

Keep the published form collecting while you edit. New versions can change fields; old responses keep their original schema context.

Build it from your coding agent.

Paste one prompt. Your agent asks what the form should collect, builds it into your app, and gives you the working preview.

Add a Fillo form directly to this app. Ask me what it should collect, match the existing UI and route context, and follow https://fillo.so/agents.
Prompt it. Preview it in your app. Publish when it looks right.

Tried the agent setup. Literally one prompt and it was live on all help pages on rotato.app

Morten JustFounder of Rotato

Frequently asked questions

When should we use Fillo?

Use Fillo when the form belongs inside your product: onboarding, support, feedback, intake, file requests, and approvals that need your route, components, account context, or ongoing maintenance.

Can my coding agent set Fillo up end to end?

Mostly. Your agent installs the Build-with-Fillo skill, provisions the form, adds it directly to your app, and gives you a live preview. You claim the workspace to keep it, and connect external accounts yourself when an OAuth or account-level decision is required.

Can I use my own design system?

Yes. Fillo renders accessible HTML controls directly inside your app, not an iframe. Start with the default renderer and restyle it, replace fields with your own components, or use the headless hooks.

Where do uploaded files go?

For durable storage, connect Google Drive, Box, Amazon S3, or Cloudflare R2. File bytes upload browser-direct while Fillo keeps the response and durable file reference together. Temporary Fillo transit storage is capped and short-lived; the current limits are published on the pricing page.

What does Fillo cost?

Free includes 200 completed responses a month with no time limit. Everything is free for 30 days, then €35 ($39) a month for 5,000 responses. Extra responses are €0.007 ($0.008) each. Every render method is included on both plans.

The next form does not need another backend project.