Dock.us VS BriefGate.dev

Dock.us's answer

Lattice, Loom, Nooks, Rho, FundraiseUp, Intenseye

BriefGate.dev's answer:

BriefGate is built so an AI coding agent can run the intake itself. Through an MCP server, Claude Code, Cursor, Codex or any MCP client declares what a project needs from the client - files, copy, choices, structured data, logins - and later pulls the answers back as typed data it can act on. The client sees none of that: they open one link, with no account to create, and fill in what was asked. Most tools in this category are built for a person to operate a form. BriefGate is built for an agent to operate the whole loop, and it works straight from the dashboard when no agent is involved.

BriefGate.dev's answer:

Three things. First, the client has nothing to sign up for - one link and they are in, which is usually the difference between materials arriving this week or next month. Second, the follow-ups run on their own until every item is in, so nobody has to keep a mental list of who still owes what. Third, logins are handled properly: they go into an encrypted vault and are revealed once, instead of living in an inbox forever. On top of that BriefGate is a real API product - REST, webhooks and an MCP server - so collecting client input can be a step in an automated pipeline rather than a manual chore. Data is stored in the EU.

BriefGate.dev's answer:

Two groups. The first is developers and agencies who build with AI coding agents and want a project's missing inputs collected without leaving the agent - the agent asks, the client answers, the answers come back as typed data. The second is small agencies, freelancers and studios who simply want client materials to arrive on time; they create the request in the dashboard, send one link and never touch the API. Both share the same trait: the bottleneck is not the work, it is waiting on the client.

BriefGate.dev's answer:

It came out of building projects with AI coding agents. The agent could write the whole application, but it kept stopping in the same place: it needed the logo, the final copy, an API key, a decision on a name. All of that lived in someone else's head or inbox, so the work stalled on a person rather than on the code. BriefGate is that missing piece: the agent states what it needs, the client answers in a plain portal with nothing to sign up for, reminders go out on their own, and the result comes back as typed data.

BriefGate.dev's answer:

TypeScript throughout. The API is Fastify on Node, with PostgreSQL and Drizzle for data and Redis with BullMQ for the reminder queue. Credentials are encrypted with libsodium and passwords hashed with Argon2; files live in S3-compatible object storage. Email goes through Resend, billing through Stripe, error tracking through Sentry. The MCP server is published on npm as @briefgate/mcp. Everything runs in Docker on EU infrastructure.