Visual edits
Change labels, choices, publish status, close dates, storage, and webhooks without redeploying.
All features
Add the form without building the system around it
Use the editor, code, or both. Fillo keeps questions, validation, uploads, responses, and versions together so your app can stay focused on the product.
Editor, code, or both.
builder-and-code
const feedback = defineForm({
id: "failed-export",
title: "What went wrong?",
pages: [{ id: "p1", blocks }],
});
<FilloForm form={feedback} client={client} />Forms defined in code
Keep product-owned forms beside the feature code and sync the form setup to Fillo.
Fast first setup
Paste one prompt into your app builder and let it add Fillo instead of creating another one-off form flow.
What this solves
Most product teams do not need another form system hidden inside their app code. They need a way to add the form, let the right person edit it later, and keep submissions, uploads, and delivery settings in one place.
Fillo gives you a hosted editor for day-to-day changes and a typed SDK for forms that should live close to a product feature. You can start visually, define a form in code, or use both when that is the practical choice.
That works well for customer intake, onboarding, feedback, cancellation surveys, support forms, and internal requests. The form can change after launch without becoming a new admin project.
Good fit for
- Product forms that change after release.
- Teams that want non-developers to edit labels, choices, and publish settings.
- Developers who want product-owned forms to stay near the feature code.
- Apps that need native forms instead of embedded iframes.
Fillo handles
- Hosted form editing, publish status, and version history.
- Shared schema for editor-built and code-defined forms.
- Validation, conditional logic, answer piping, and URL prefill.
- Agent-readable install docs through /llms.txt.
No forced choice
Some forms belong in a dashboard. Some belong near the feature code. Fillo supports both without splitting the form setup.
App-builder friendly
/llms.txt gives coding agents the install steps and examples they need, so setup stays predictable.
Common questions
Yes. You can build and publish a form from the editor without defining it in code. The SDK is there when you want the form rendered inside your app.
Yes. Code-defined forms use the same core schema, so product-owned forms can live beside the feature that uses them.
Yes. Fillo renders native DOM in your product. You are not sending visitors into a separate iframe experience.