deban 出番 · Self-driving form
Write a plain note about what you want to know. Get back a form people can actually fill in. With a deletion date you set yourself.
No signup needed for people filling it in.
Drag-and-drop form builders are already free and everywhere, so deban doesn't repeat that. What's different is starting from what you already wrote, and what happens after the link goes out.
Drop in a note you wrote yourself, or have AI draft one first. Plain text is all it needs, one that says what you want to know from whom.
The single source of truth is one spec file. The web page, the answer intake, and the agent all read the same file, no question hides anywhere else.
Want to edit question wording, add options, or change the brand color after sending the link? Go ahead. The same key still works.
It also tells you what the edit affects, like how many people already answered a field you just removed.
Each person who clicks gets their own copy. Clicking again returns to that same copy, never a new one on top.
Answers save to their device while typing. Close it and reopen, and they pick up right where they left off.
Who holds the copy is decided at the database, not in application code. However many arrive at once, only one holder wins.
If a holder disappears mid-way, the copy releases itself when the lease expires. Nothing gets stuck.
deban ships with a built-in MCP server. Connect it straight to the tool you're already working in, no switching screens back and forth.
Connects over stateless Streamable HTTP. No hanging connections, no sessions to manage.
deban_spec_check · deban_spec_generate
deban_form_create · deban_form_update · deban_form_list
deban_envelope_open · deban_envelope_todo · deban_envelope_claim
deban_envelope_fill · deban_envelope_heartbeat
deban_envelope_release · deban_envelope_submit · deban_envelope_summaryThe token for filling in and the token for reading results are different tokens. If the fill-in one leaks, it still can't pull out every answer in the form.
If it ever leaks, revoke it and issue a new one. The old link dies instantly.
Every form must state, from the moment it's created, how many days data is kept, what it's used for, and who to contact. People filling it in see this on the first screen, not buried at the bottom.
Deletes the "answers," not the "copy." The record that this copy existed, and when and by whom it was deleted, stays intact.
A deletion request must name who's asking. A record that doesn't know who acted isn't a record.
Access expires and can be revoked anytime, and you can see for yourself which copy we opened, when, and why.
We'll build your first form for it, free. What we're asking isn't your opinion about our product, it's what you actually do. The more specific, the closer the form fits.
This form was built with deban itself, about 3 minutes.