Is Drafty harder to use than Markup.io?

No — sharing a link and commenting works the same way. Markup.io has a more polished designer-first UI; Drafty trades a little of that for threads, a library, and the agent loop.

Can reviewers comment without an account?

Yes, on both. Drafty also keeps a guest identity so a thread reads as a real conversation.

What does Drafty do that Markup.io doesn't?

Threaded resolve/reopen, a searchable library of every artifact, comments on any artifact (not just uploads/sites), and Claude shipping the fix on the same link.

drafty

Markup.io collects the comment. Drafty ships the fix.

Both let a client point at the exact spot with no login. Drafty goes further — threaded discussion, a library of every artifact, and Claude reading the feedback and pushing a new version on the same link.

Open a live demo

Public linkNo loginAny artifact

drafty.im/canvas/dashboardv1v2

Dashboard

make this weekly, not daily

claude code

$ drafty comments inbox

● “make this weekly, not daily” · Dashboard

✦ Claude is working…

✓ pushed v2 — same link · thread resolved

A comment becomes a shipped fix — on the same link.

Drafty vs Markup.io

An honest, capability-by-capability look — including where Markup.io is the better pick.

What your client needs	Drafty	Markup.io
Point-and-comment with no account
Threaded reply / resolve / reopen
Searchable library of every artifact
Agent reads the feedback and ships the fix
Comment on a live website, not just an upload		limited
Polished, designer-first markup UI	good

How it works

Point at the exact spot

Hover any element, click, leave a note pinned to it.

Discuss it in a thread

Reply, resolve, reopen — a real conversation, not a one-off sticky.

YouJaneLove this line

Claude ships the fix

It reads the thread and pushes a new version on the same link.

we are really very goodfaster, every loop

make it punchier

Why people switch

The old way

Comments pile up with no way to reply or close them
Last month's markups are lost in a list of links
You still make every change by hand

With Drafty

Threaded resolve / reopen — Every note has a clear status
A searchable library — Find any artifact and its feedback in ⌘K
Claude reads the thread — The fix lands on the same link, versioned

Who it's for

Freelance designer

Send the client a mockup link. Get notes on the design, not a vague email thread.

Solo consultant

Share the deliverable. The client reacts inline — and it looks like your work.

Indie builder

Drop your v0 app in a thread. Testers comment without signing up for anything.

Questions

Is Drafty harder to use than Markup.io?: No — sharing a link and commenting works the same way. Markup.io has a more polished designer-first UI; Drafty trades a little of that for threads, a library, and the agent loop.
Can reviewers comment without an account?: Yes, on both. Drafty also keeps a guest identity so a thread reads as a real conversation.
What does Drafty do that Markup.io doesn't?: Threaded resolve/reopen, a searchable library of every artifact, comments on any artifact (not just uploads/sites), and Claude shipping the fix on the same link.