Open Source Typeform Alternative Your AI Agent Can Actually Use (2026)

Most people searching for a Typeform alternative want one of three things. Stop paying per response, own the data, or let software create forms for them. In 2026 there is a fourth reason, and it is quickly becoming the first. Teams now run AI agents, and those agents need to build, publish and read forms without a human clicking through a builder.

Typeform is a good product for a person designing a form by hand. It is less good when the "person" is Claude, ChatGPT or Cursor acting on your behalf. So this guide looks at what a Typeform alternative needs to do when an agent is the one using it. Then it shows how dForms covers that, for free and open source.

This is not a roundup of ten tools. It is one solution page: what to look for, what dForms does, where it is different, and what to check before you switch.

Why teams look for a Typeform alternative

Three complaints come up again and again, and they are easy to verify on Typeform's own pricing page.

Responses are the meter

Typeform's plans are sized by responses. According to the Typeform pricing page, the Basic plan includes 100 responses a month, Plus includes 1,000 and Business includes 10,000. The free plan includes a limited number. So a form that goes viral, or a hiring campaign with 2,000 applicants, moves you up a tier. Whether you wanted the extra features or not.

The data lives in someone else's account

Responses sit in Typeform's workspace. You can export and integrate, of course, but you cannot run the software yourself. For a team with a data policy, or a founder who wants the database in their own cloud, that is a hard limit.

The builder was designed for a human

Typeform's strength is its one question at a time design, built in a visual editor. That is pleasant for a person and awkward for an agent. Typeform does ship an MCP server, so an agent can create and edit forms there. However, the pricing and the data model are still the ones above.

What a Typeform alternative needs to do for an AI agent

If your agent will be the main user, add four criteria to your checklist. Price and design still matter, but these decide whether the agent can do the job alone.

1. An API or MCP server the agent can call with one key. Not a browser automation hack. The agent should create a form, add logic, publish and read responses through documented routes.
2. Scoring and routing inside the form. The agent should not have to export a CSV to find out which answer was good. Points per answer, buckets and a path to the calendar or CRM should live where the form lives.
3. Free with unlimited responses. An agent will make more forms than a person does, because forms stop being expensive to make. A per response meter punishes exactly that.
4. Open source and self-hostable. When an agent holds the keys, you want to be able to read the code, run it where you choose, and leave with your data.

The AI form generator guide goes deeper on the first two points and on what a form builder API needs so an agent cannot break things.

dForms: the open source Typeform alternative built for agents

dForms is the form builder for AI agents, the one your agent actually wants to use. You give your agent one API key. It builds the form, publishes it, scores every answer and sends the hot leads to your calendar or CRM. Second, and this matters for this search: it is free, open source under the MIT license, and you can self-host it.

Here is how the pieces you use in Typeform map to dForms.

Typeform features and their dForms equivalents

The difference is not a longer feature list. It is who holds the pen. In Typeform, a person opens the builder. In dForms, your agent does, through the API, and you review the result.

How the free plans compare

We checked each tool's own pricing page. Figures are the public ones on the day of the check, so confirm them before you decide.

Tally is a fair Typeform alternative for a person who wants a free builder. Where dForms differs is the scoring, the routing and the self-hosting, all in one place the agent already works in.

How your agent builds the form in dForms

This is the part that makes the switch worth it. Connect once, then ask in plain language.

1. Connect. Create an API key on the Developers page in dForms, or connect Claude through the dForms MCP server at mcp.dforms.ai. The key acts as you, in your workspace, with your role.
2. Ask. Describe the form the way you would describe it to a colleague. Fields, logic, scoring, where the hot answers should go.
3. Review and publish. The agent builds a draft. You can ask it to publish, or publish yourself from the dashboard.
4. Read the answers. Ask the agent for the scored responses, the top bucket, or a summary of the open answers.

Paste a prompt like this into your agent:

Create a form in dForms to replace our Typeform lead form.
Fields: full name, work email, company website, team size (1, 2 to 10, 11 to 50, 51 to 200, 200+),
what they want to solve (open), and when they want to start (this month, this quarter, later).
Score it: team size 11 to 200 = 10 pts, 2 to 10 = 5, others = 2; start this month = 10, this quarter = 6, later = 1;
open answer that names a concrete problem = 10, vague = 3, blank = 0.
Label 70% or more as Hot, 40% to 69% as Warm, under 40% as Cold.
Publish it and give me the public link.

The agent returns the link. From then on you can ask it for the Hot bucket or tell it to send Hot leads to your calendar. The same model powers the AI SDR qualification form and the 25 question lead qualification template, which you can hand to the agent as the starting spec.

Typeform alternative free or self-hosted: which setup fits you

Both are the same software. The choice is about who runs it.

Use the hosted free plan when

• You want to switch this week and have no infrastructure to maintain.
• Your agent needs the MCP server at mcp.dforms.ai in Claude without any setup.
• Response volume is unpredictable. Responses are not counted or billed, so a spike costs nothing.

Self-host when

• Your data policy says responses stay in your cloud.
• You want to read and audit the code your agent is calling. The repository is public and MIT licensed.
• You already run your own services and prefer one more container to one more vendor.

What to check before you switch from Typeform

A few honest notes so the move has no surprises.

• Response history. Export your Typeform responses before you close the account. dForms starts with an empty workspace; there is no automatic importer from Typeform.
• Keys act as people. A dForms API key has the same role as the member who created it, and there are no per key scopes. An agent with a key can publish. If you want a human to approve every publish, ask the agent to leave the form in draft and publish it yourself. Edits live in a draft until published, and a published form can be reverted.
• Rate limits. Each key gets 120 calls a minute. Enough for an agent building forms, worth knowing if you plan a bulk migration.
• Design. Typeform's one question at a time look is its signature. If that exact presentation is a requirement, test a dForms form with your audience before moving every form.

Because the responses are free and the code is open, the cost of trying it is one afternoon. Let your agent rebuild one form, send real traffic to it, and compare.

Frequently asked questions

Is dForms really a free Typeform alternative?

Yes. dForms is free for life, responses are not counted or billed, and the code is MIT licensed. There is no response tier to move up to.

Can my AI agent create forms in dForms without me?

Yes. An agent with an API key, or Claude connected through the dForms MCP server, can create, edit, publish and revert forms and read responses. If you want to approve forms before they go live, ask the agent to leave them in draft.

Does Typeform have an MCP server too?

Yes. Typeform, Tally and Jotform all ship MCP servers, so agent access on its own is not rare anymore. The differences are the response limits, the scoring and routing inside the form, and whether you can self-host.

Can I self-host this Typeform alternative?

Yes. The repository is public on GitHub under the MIT license, so you can run dForms on your own infrastructure and keep every response in your cloud.

Does dForms work with ChatGPT and Cursor, or only Claude?

Any agent that can call an HTTP API with a key can use dForms. Claude also connects through the MCP server at mcp.dforms.ai, with no extra setup.

Will my Typeform integrations still work?

dForms syncs with HubSpot and sends webhooks, so most downstream flows can be rebuilt. Check each integration you rely on before you move, and keep Typeform running until the new form has processed real responses.