Click-to-comment on any live URL. Staging sites included. No extension required for you or your client.
The truth
Screenshot emails arrive with red circles and no element reference.
Clients annotate a PDF of a screenshot instead of the live site.
You rebuilt the wrong thing because the feedback was unclear.
How kiro fixes it
Problem
"Make the button bigger"
kiro's answer
Client clicks the exact button. kiro captures CSS selector, viewport, browser, OS. No ambiguity.
Problem
Staging sites need auth
kiro's answer
Enter HTTP basic auth on canvas creation. kiro proxies through it. Your client never knows the difference.
Problem
Mobile vs desktop confusion
kiro's answer
Multi-viewport mode. Switch between desktop, tablet, and mobile. Ghost pins show comments from other viewports.
The workflow
Paste the staging URL. Add basic auth if needed.
Share the link with your client.
They click where something needs to change. kiro captures everything.
Fix the issue. Resolve the comment. Push to Jira if needed.
New version? Create v2, archive v1, compare side by side.
What you get
Proxied. No extension. Clients click anywhere on the live site and a pin captures full context.
HTTP basic auth credentials are encrypted at rest and used only to fetch the page.
Desktop, tablet, mobile. One canvas. Ghost pins show comments from other viewports.
Push every comment to a Jira issue or Slack message with screenshot and metadata attached.
Recommended plan
15 projects · 5 seats · Jira + Slack · PDF export
Ready?
Set up your first canvas in under a minute. Free plan, forever.