Velt×
NutrientAdd comments and shared annotations, plus live presence, to PDFs in your Nutrient viewer, for your users and your AI agents. Threads stay pinned to the page and region across versions, and every agent markup lands for your reviewer to approve, so the markup stays where it belongs.
Free tier. No credit card. First comment in 5 minutes.
7.2 The Provider shall indemnify and hold harmless the Client against all claims arising from the Services.
Flagged a missing liability cap on the clause and suggested a redline.
The problem
Your users expect to comment and co-edit in Nutrient, and your AI agents need that same document with a human approving before they touch user work. Comments that survive Nutrient's version changes are a multi-quarter build, and the moment anchoring breaks, feedback lands on the wrong region. Co-editing is the harder half: rolled by hand it means overwrites, lost work, and merge conflicts, the "my changes disappeared" bug reports, plus a websocket fleet and offline merge to keep alive. And the harder question is your agents: a useful agent needs to change the work, but an agent with write access to user content is what your buyers' security review blocks, so without a consent step you choose between an agent that is useful and an agent that is safe. Every quarter spent on this is a quarter not spent on your own product.
Velt is the review and collaboration layer built for Nutrient: your users and your AI agents work the same document, with comment threads anchored to the page and region, and every agent suggestion is a change a human approves before it lands.
Features
Clause 7 omits a liability cap. Suggested fix attached.
// An agent posts a suggestion as a first-class user.
await velt.comments().add({ author: agent, suggestion });
// On approve, the change fires through your webhook.Your AI agent comments and suggests on the document as a first-class user; a human approves or rejects, and on approve the change fires through your webhook with a permanent record.
@Maya pulled into the thread
2 Repliesimport { VeltComments } from "@veltdev/react";
<VeltComments textMode />Anchored to page regions, with replies, @mentions, and attachments.
This pricing claim conflicts with the rate table on slide 4.
// Anchor shared markup to any region.
<VeltCommentTool />Shared, live-synced markup on the page region.
import { VeltPresence, VeltCursor } from "@veltdev/react";
<VeltPresence />
<VeltCursor />Live presence on the document.
Suggested a tighter figure on the rate line.
// Propose changes reviewed like a diff.
<VeltComments suggestionMode />Propose redlines as accept-or-reject suggestions.
Maya mentioned you on Q3 forecastmention
“@you can you review before Friday?”
Sarah replied on the Q3 threadreply
forecast.xlsx · cell B12
Ethan requested your sign-offsign-off
contract.pdf · due today
import { VeltNotificationsTool } from "@veltdev/react";
<VeltNotificationsTool />In-app, email, and Slack alerts on every comment and @mention.
voice note · pinned to this cell
“The variance comes from the vendor rate change, see row 18.”
import { VeltRecorderControlPanel } from "@veltdev/react";
<VeltRecorderControlPanel />Pin a quick voice, screen, or video clip in context on the page.
await velt.versions().save({ name: "Draft v3" });
await velt.versions().restore({ id });Named checkpoints on the document, saved and restored by API.
const log = await velt.activities().get({ documentId });Every markup and approval on the matter, exportable.
A clause-review agent flags a missing term on the page region and suggests the redline as a first-class user; your reviewer approves or rejects, and on approve the change fires through your webhook with a permanent record of who allowed what.
Setup
npm install @veltdev/react @veltdev/nutrient-reactimport { VeltProvider } from "@veltdev/react";
<VeltProvider apiKey={API_KEY}>
<App />
</VeltProvider>// Mount Velt on Nutrient
<VeltComments />
// + the CRDT adapter for co-editingWhy Velt
Liveblocks syncs people and agents into your app's state; Velt adds the step Liveblocks does not, every agent change on Nutrient is a suggestion your user approves or rejects, on the record.
Enterprise
The controls your buyers' security reviews ask for, in writing.
Adding Velt to Nutrient does not move that surface's content off your stack. Per-feature data providers keep comment content, attachments, and user PII on your own infrastructure; Velt stores only minimal identifiers.
FAQ
Annotations on a read surface; comments and shared annotations both work on PDFs in Nutrient.
Yes. The Velt adapter maps to Nutrient's annotation layer so the two coexist on the same document without conflict.
Yes. Velt's primitives follow Nutrient's mobile rendering, so threads anchor correctly on phone and tablet viewports.
Yes. An agent posts a comment or suggestion on the region as a first-class user, and a human approves or rejects before anything changes.
Yes. The audit trail captures every markup and approval and is exportable via API.
On usage, not seats or integrations: you pay for documents with review activity in a month, with a free tier for development and early production.
Free tier. No credit card.
First comment in 5 minutes.
Apryse
SuperDoc