Comments
Contextual threads from humans or agents, on any element, doc, cell, or canvas, so feedback stops scattering across email, Slack, and screenshots.
No more two-quarter detours to build threads, mentions, and anchoring.
Free tier. No credit card. First comment in 5 minutes.
This pricing claim conflicts with the rate table on slide 4.
$85 doesn’t match the approved Q3 number.
1 Reply7.2 The Provider shall indemnify and hold harmless the Client against all claims arising from the Services, including but not limited to indirect and consequential losses.
Brand Agent flagged a pricing claim agent
“conflicts with the rate table on slide 4”
Maya mentioned you on Clause 7 mention
“needs a liability cap before we send”
Sarah resolved the Q3 forecast thread resolved
forecast.xlsx · cell B12
This sounds a bit flat — try a warmer take here.
Comment threads running inside products at
What it is
Velt Comments adds contextual comment threads to any part of your product: text, documents, spreadsheet cells, canvases, video frames, charts, or your own custom components. Both humans and agents can comment through the same API; an agent is just a user with type agent. Threads support mentions, assignment, resolve states, reactions, attachments, and visibility controls, and every comment is queryable through the API and fires events to your backend.
One thread, both actors
This pricing claim conflicts with the rate table on slide 4. Suggested fix attached.
@Maya can you confirm the Q3 number?
Confirmed, accepting.
accepted · webhook review.approved fired · consent visible
How it works
Install the SDK, wrap your app, and add VeltComments. Threads anchor to any element, stream live to your UI, answer REST queries, and fire webhooks to your backend.
npm install @veltdev/react<VeltProvider
apiKey={VELT_API_KEY}>
<YourApp />
</VeltProvider><VeltComments />
// threads anchor to any
// element you wrapInstall the SDK, wrap the target element, and threads anchor to it. Threads support mentions, assignment, resolve states, reactions, attachments, and visibility controls. Every comment is queryable through the API and fires events to your backend. Agents comment through the Comments REST API, the same surface humans use.
// VeltComments anchors to any element · queryable via API · webhooks on every event
Teams that build it budget a quarter for the first version and keep paying for the long tail. The 3 steps above replace the first quarter; the capability wall below replaces the long tail.
Skip the steps. Have your agent set it up.
npx -y @velt-js/mcp-installer
claude mcp add velt-installer -- npx -y @velt-js/mcp-installer
npx -y @velt-js/mcp-installer
npx -y @velt-js/mcp-installer
npx -y @velt-js/mcp-installer
Editors and surfaces
APIs and pipes
Launch comments this week.
No credit card. Works with React, Next.js, Vue, Angular, and HTML.
Capabilities
Each card is the live SDK. Toggle to Code for the exact snippet that renders it.
This pricing claim conflicts with the rate table on slide 4.
React
Next.js
Angular
Vue
HTML
Tiptap
Lexical
Quill
CodeMirror// anchors to text and complex DOM
<VeltComments />A doc, a PDF, a table cell, a chart datapoint, a video frame, a canvas. Robust anchoring to text and complex DOM elements; the anchor model works on your custom components too.
Clause 7 omits a liability cap. Suggested fix attached.
POST /v2/comments
{ "type": "agent", "actions": ["approve", "reject"] }Your agent reviews and drops findings as contextual comments, anchored to the exact clause, cell, or claim, with Approve and Reject attached. In the work, not in a separate report.
Hold the discount: let's counter at 12%.
2 Replies<VeltComments visibility="private" />Scope any thread to me, my team, or specific people. Internal debate stays internal: notes the client never sees, deliberation the counterparty can’t read, drafts only the author can open.
@Maya pulled into the thread
2 Replies// @Maya pulled in · assigned to Sarah@mention pulls the right reviewer into the thread; assignment makes the decision someone’s job. Reviews move when ownership is explicit.
{ "status": "resolved", "seenBy": 3 }Open, in progress, resolved, and who has seen what. The “did legal look at this?” question answers itself.
@Maya Update text based on this
// files + emoji reactions on any threadDrop the evidence in the thread: the source file, the field photo, the reference deck. Reactions clear the noise of +1 replies.
Please see the recording to update the slides
// voice + screen recordings, pinned in contextA voice note on a cell, a screen recording on a draft. When saying it beats typing it, the recording pins where the work is.
POST /your-webhook
{
"event": "comment.added",
"documentId": "deck-q3"
}comment · reply · resolve · approval: full payload
POST /your-webhook
{ "event": "comment.added" }Every comment, reply, resolve, and approval fires a webhook with the full payload. Pipe review activity into your backend, your analytics, your audit pipeline.
Feedback used to live in email chains about the asset. Now it lives on the asset, in a thread anyone can resolve.
Product lead · collaborative editor
Little big details
Everything that goes into building the best commenting experience
15+ first-party integrations. SDK works in any framework via web components.
Make it yours
Prebuilt components for the fast path, wireframes and primitives for fully custom comment UIs, and custom types, data, CRUD APIs, and webhooks underneath.
Prebuilt components (Comments Sidebar, Comment Pin, Comment Bubble, Comment Composer, Standalone Thread) for the fast path; wireframe components and primitives for fully custom comment UIs; themes and template variables.
Kim & 3 others
We should be updating all the new assets with the new logo
<VeltCommentsWireframe>
// your markup, Velt threads
</VeltCommentsWireframe>Custom comment types, custom data on threads, full CRUD APIs, and webhooks into your pipeline.
velt.comments.create({ type: "suggestion" });
velt.webhooks.subscribe({ events: ["comment.*"] });We restyled the prebuilt thread with our own wireframe in a day. Our comment UI looks nothing like Velt’s defaults, and the hard parts were already done.
Design engineer · fintech platform
In production
Tabbed by vertical, with verified customer screenshots.
This Digital Sales Room gives you everything you need to move forward — from proposal to plan.
@Fin We need to make a working demo for Rene and his team
Brand, legal, and the client comment on the deck, the email, the digital sales room itself. Feedback lands on the asset, not in an email chain about the asset.For sales enablement
finance / receivables
Can we confirm the PO before approving this one? @Sarah
1 ReplyCell-level threads on budgets, forecasts, and filings. The question about Q3 sits on the Q3 cell, attributed, resolved, and on the record.For fintech and FP&A
Cotton Supplier Ltd.
AgriCotton Farms
Village Kheda, Gujarat, India
SpinCo Yarns
18 Narol Rd, Gujarat, India
DyeWorks International
Calle de Mayo, Mexico
Can you attach the GOTS cert for this lot before we approve? @Sean
1 ReplyThreads on the order, the shipment, the field record. Your team’s debate stays internal; the counterparty sees only what is meant for them.For operations
Privacy Risk Review
Wren discovered a feature request in Jira involving users' health data and triggered a review after analyzing the PRD in Confluence against company policy and US regulation.
JStarted by Juan MendezThis feature processes PHI, so HIPAA applies. I recommend a PIA and a vendor BAA review before any data flows. @Juan
Threads pinned to the exact control, filing line, or attestation. The deliberation stays internal until officers sign off, and every decision is on the record.For compliance
Superflow
1 · Subscription & Fees
Customer subscribes to the Service on a monthly basis and shall pay the then-current fees in advance of each billing period. Fees are non-refundable except as expressly set out in this Agreement.
2 · Term & Auto-Renewal
The subscription renews automatically for successive one-month terms unless either party gives at least thirty (30) days' written notice of non-renewal before the end of the then-current term.
3 · Limitation of Liability
Except for breaches of confidentiality, each party's total aggregate liability under this Agreement shall not exceed the fees paid by Customer in the one (1) month preceding the event giving rise to the claim.
4 · Governing Law
This Agreement is governed by the laws of the State of Delaware, without regard to its conflict-of-laws provisions, and the parties consent to the exclusive jurisdiction of its courts.
@Jordan Auto-renewal needs 60 days' notice to match our policy, not 30.
@Maya Liability cap is one month of fees — Legal wants 12 months before we sign.
@Maya Governing law should be New York to match the MSA.
Clause-level threads on the matter. Counsel debates the redline internally, the counterparty never sees it, and the attributed history survives the next revision.For legal
Make the hero headline punchier and add a primary CTA.
Done — rewrote the headline, tightened the subtext, and added a primary CTA in hero.tsx.
Add a logo strip with social proof under the CTA.
Added a five-logo trust strip below the CTA and wired it into hero.tsx.
Ship your app in a weekend
Get startedUse our brand orange on the CTA and cut the headline to one line. @Sean
Every agent finding is a comment with Approve and Reject attached. The review loop for generated work runs on the same threads your users already know.For AI-native SaaS
See it running in products like yours.
30 minutes, with an engineer, not a sales deck.
Related primitives
A comment with a proposed change, a finding that lands as a comment, the pipeline that keeps threads alive.
A suggestion is a comment with a proposed change.
Findings land as comments, anchored to the work.
Finding lands as a comment, anchored to the work.
2 RepliesThe pipeline that keeps threads alive.
Maya replied to your thread
the pipeline that keeps threads alive
Comment content can live on your infrastructure via the self-host data provider, with only minimal identifiers on Velt. GDPR deletion runs through the compliance API with its own audit log. Comments run on the same isolation guarantees as the rest of the SDK. See self-hosting and governance.
Book DemoProof
Threads, mentions, and anchoring, without the detour.
2 quarters
We’d scoped two quarters to build threads, mentions, and anchoring ourselves. We dropped in VeltComments and shipped it in a week.
1 thread
Brand, legal, and the client comment on the asset itself now. Feedback stopped scattering across email, Slack, and screenshots.
100%
Every agent finding lands as a comment with approve and reject attached. Our reviewers act on it in the work, not in a separate report.
FAQ
Anything that renders on the web. Comments anchor to elements, so the surface type does not matter: rich text editors (Tiptap, BlockNote, Lexical, Plate, Quill, Slate, ProseMirror, CodeMirror, Ace), documents and PDFs, spreadsheets and tables, charts (ChartJS, Highcharts, Nivo, or your own), HTML canvas, video, Lottie animations, and any custom component via the anchor API.
Yes. Agents post through the same Comments REST API humans use; an agent is a user with type agent. Findings can carry approve and reject actions so a human decides what happens next.
Velt handles anchoring so threads stay attached when content moves or changes.
Yes. The comments data provider keeps comment content on your infrastructure while Velt stores only minimal identifiers. See /self-hosting.
Install @veltdev/react, wrap your app in VeltProvider with your API key, and add the VeltComments component. The first comment renders in about five minutes; the quickstart walks through it.
Yes. Use the prebuilt components as-is, restyle them with wireframes and template variables, or build fully custom UIs on the primitives and APIs. Your comment UI can look nothing like Velt’s defaults.
Yes, through the Comments REST API: import threads with authors, timestamps, and anchors.
Yes. Velt is optimized for mobile web, works inside WebViews in native apps, and pure native apps can integrate through the REST APIs with your own native UI.
Velt is priced on usage, not seats: you pay for documents with review activity in a month, and there is a free tier for development and early production. Comments is part of the SDK, not a separately priced add-on.
Free tier. No credit card. First comment in 5 minutes.
30 minutes, with an engineer, not a sales deck.
This clause needs a liability cap before we send. @Sarah can you confirm scope?