Compare
How Dornick compares.
Honest side-by-sides. When to pick Dornick. When to pick them. When the comparison is unfair because you're solving different problems.
vs CopilotKit
CopilotKit gives you React components for AI copilots; Dornick gives you a browser agent that reads your live DOM. Same neighborhood, different bets. Here's when each wins.
Read →vs MCP-B
MCP-B is the WebMCP plumbing — polyfill, transports, relay, extension — that connects your page to agents elsewhere. Dornick is the agent, in the page. Both speak the standard.
Read →vs PageAgent
PageAgent and Dornick both put an agent on the page. The difference is abstractions: Dornick exposes a VFS, hooks, skills, and multi-agent; PageAgent is leaner but less primitive-rich.
Read →vs Stagehand
Stagehand automates a browser from the server with act/extract/observe primitives. Dornick is the same primitives, on the user's browser, with their consent. Different problems.
Read →vs Typeform
Typeform is a hosted form-builder SaaS. Dornick is an in-page agent SDK that drops into your own pages. Comparing them is comparing a SaaS to a runtime — but they solve the same problem.
Read →vs Vercel AI SDK
Vercel AI SDK is plumbing for streaming LLM responses in Next.js. Dornick is an agent runtime for your page. They're complementary — many Dornick apps use the Vercel AI SDK underneath for the proxy.
Read →Ship an agent-driven flow this afternoon.
Install Dornick, paste a config, and your form turns into an agent that fills its own inputs.