Create an account

Fillo has two front doors. People continue with an emailed sign-in link at fillo.so/login; if the address is new, clicking that link creates its verified account. The dedicated signup page additionally lets them provide a display name. Coding agents provision a live, capped preview workspace from the terminal — no browser, no form — and hand their developer a claim link that saves it to an account. Neither path asks for a card.

Sign up with an email link

1. Open /signup and enter your work email.
2. Fillo emails you a sign-in link. There is no password at signup.
3. Click the link. That one click verifies the address, signs you in, and lands you in the dashboard.

The same flow signs in a returning address — one account per email, whether it was created here, through Google or GitHub, or by claiming an agent-provisioned workspace. Continue with Google and Continue with GitHub are available on the same page.

You can also build first and sign up later: the form editor keeps a guest draft in your browser until you sign in and claim it.

Agents: provision a workspace from the terminal

An agent (or any script) can create a working Fillo workspace without rendering the signup form. Ask the human for their work email if it is not already in the task. Ask once, and never invent an address, infer or scrape it, or use a documentation placeholder. Then run this from the project the agent is editing:

npx @usefillo/cli@latest agent bootstrap --email <work-email>

One command provisions a preview workspace, signs the CLI into it, installs the Build with Fillo skill, and prints the workspace's pk_ publishable key. The workspace is live immediately — published forms accept real responses — with preview caps until it is claimed: up to 3 forms, 10 responses in total, and a 14-day hold. The email receives a private workspace link.

After building and verifying the form, finish account setup before handing it over:

npx @usefillo/cli@latest claim

Open the newest workspace link in the inbox used at setup. Save the workspace using that same email, then approve the terminal only if the page's code matches the CLI. Once the CLI confirms it is connected, the workspace belongs to your account and has the free plan's limits. If you are signed into a different account, use Switch account on the claim page.

If you cannot finish now, keep the remaining inbox step visible: the form is still in a capped preview that expires. An agent must not open your inbox or approve the claim for you.

If the developer already has a Fillo account, skip provisioning and connect it instead:

npx @usefillo/cli@latest login

The same loop is available as MCP tools (fillo_provision_workspace, fillo_push_form, fillo_claim_status) via npx -y @usefillo/mcp — see MCP setup. Machine-readable starting points for everything else are indexed at /llms.txt.

What you get without paying

The free plan needs no card: unlimited visual-builder forms, up to 200 code-defined forms per workspace, and 200 completed responses a month, with Fillo branding visible on rendered forms. Current allowances and paid limits are published at /pricing and, as Markdown, at /pricing.md.

Related

• Build in the dashboard: Create, publish, and share a form — no code required.
• Quickstart: Install a native renderer in React or another browser framework.
• Agent setup: Install the skill and wire an agent to your workspace.
• Workspaces and projects: Share billing and teammates while isolating forms and keys by project.