What it is
You build a form in the builder. It gives you a line of HTML. You paste that into your site. That is the integration.
There is no npm package to install, no framework version to match, no plugin to keep patched, and no build step. The renderer ships compiled and is served from the form host, so changing a field or adding a language updates the live form without redeploying your site.
The editor runs on a phone
Section titled “The editor runs on a phone”Not a viewer: the editor. Add a field, change its settings, reorder the form, read submissions, publish. The palette and the settings panel slide over the canvas instead of squeezing it, and the whole thing is reachable with one thumb.
This is worth saying because it is unusual. Most form builders, including the good ones, put up a message asking you to come back on a bigger screen.
Five ways to put it on a page
Section titled “Five ways to put it on a page”| Mode | What you paste | Use it when |
|---|---|---|
| Custom element | A tag and a module script | Almost always |
| Script tag | A div and a script |
A CMS or page builder |
| Iframe | An iframe |
You want zero JavaScript |
| Popup or drawer | A script with a trigger | The form is secondary to the page |
| Hosted page | A link | You have no site to embed in |
All five render the same form from the same definition. Switching between them is changing what you paste, not rebuilding anything.
What it does not do
Section titled “What it does not do”It does not require JavaScript on your page for the iframe and hosted-page modes. It does not need a database of its own. And it does not stop collecting answers because of your billing. An unpaid account keeps its live forms working and its data exportable.