For legal
Contract platforms, CLM, and legal ops tools live on redlines and sign-off. Velt embeds that loop in your product: clause-anchored comments, suggestion-mode redlining accepted or rejected like a diff, and approval chains from counsel to partner to client, every change attributed.
Free tier. No credit card. First comment in 5 minutes.
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.
The review reality
If your product carries contracts, NDAs, or matters that more than one lawyer marks up before a client signs, this page is for you.
Redlines live in a Word file emailed back and forth, and your product is where the final version gets pasted.
A comment about clause 7 pointed at clause 9 by the time counsel read it, because the contract moved underneath it.
“Who changed the indemnification cap” took a weekend of version archaeology before the client call.
Two associates marked up the same draft during a handoff and one set of redlines disappeared.
The loop
Velt runs one counterparty contract through the full review loop inside your product: clause-anchored threads, suggestion-mode redlines accepted or rejected like a diff, an approval chain from counsel to partner to client, and an attributed history of every clause. Both humans and agents act through the same primitives; nothing changes the contract without a human accepting it.
// one contract, five steps, one attributed clause history. The client never sees the negotiating-position debate.
Counterparty paper, an NDA, is uploaded into your product, and the deal team opens review on the matter.
Threads anchor to the clause, not the page: the indemnification cap gets a thread, the term clause gets another. Deal strategy stays in threads scoped to the internal team; the client never sees the negotiating-position debate.
Team-only: push back on the 2x cap before we send. INTERNAL
Counsel proposes replacement language on clause 7 inline; an agent proposes a fallback definition on the liability clause with its rationale attached. Each pending redline shows current and proposed language; the reviewer accepts or rejects like a diff, with a reason on reject. Your code applies accepted language; the SDK never mutates the contract.
Liability capped at fees paid 2x fees paid in the prior 12 months.
The workflow routes the contract in order: counsel approves the redlines, the partner approves the position, and the client's approver records the final decision as a user your product provisioned with access to this contract. Approve advances it, reject routes it back with the redlines attached, and every transition is timestamped and attributed.
Who proposed the language, who accepted the redline, who approved the version, when, and the note they left: queryable by document, user, or time range. The history of clause 7 reads as one chain, not a stack of file versions.
Feature map
Each card links its feature page. Preview the UI, or read the code that renders it.
Accept or reject like a diff: a reason is logged on reject.
<VeltSuggestions />Redlining inside your product: proposed language on the exact clause, accepted or rejected like a diff, with a reason on reject. Your code applies accepted language; nothing changes the contract silently.
Explore SuggestionsAnchored to the indemnification clause: survives the redline that moves it.
<VeltComments />Threads anchored to the clause, surviving edits as the contract moves. Deal strategy scoped to the internal team; the client reads only the thread meant for them.
Explore Comments<VeltApprovalFlow
stages={["counsel", "partner", "client"]}
/>Counsel to partner to client, in order, with quorum where two partners must sign. Approve advances the contract; reject routes it back with the redlines attached.
Explore Approval flowsEvery transition is already an attributed, exportable record.
POST /v2/activities/get
{ "data": { "organizationId": "your-org-id", "documentId": "mutual-nda" } }Who proposed the clause, who accepted the redline, who approved the version: an attributed history queryable by contract, user, or time range, exportable when the dispute lands.
Explore Audit trailPen passes on accept: no racing, no overwrite.
velt.setSingleEditorMode(true);One associate holds the pen while the deal team watches live: clean handoffs between drafts, no overwritten redlines.
Explore Single editor modeAgent action layer
An agent that flags a missing limitation-of-liability clause and proposes fallback language is a first-pass reviewer that never sleeps. An agent that rewrites the contract on its own is a problem no engagement letter covers. In Velt, every agent proposal lands as a suggestion on the exact clause, with the rationale attached and Accept and Reject on the dialog. On acceptance, your code applies the language and the record carries who allowed it; on rejection, nothing changes and the reason is logged. The agent never holds write access to contracts, clauses, or matter data. In legal work the redline is the product: a change without an author and an acceptor is not a redline, it is a liability.
Proposes · fallback limitation-of-liability language on the liability clause
attributed clause history
Accepted · Counsel · Tue 09:14 · clause applied · agent never held write access
on reject, nothing changes and the reason is logged
In production
Customers in this space include contract, CLM, and legal ops platforms running counsel, partner, and client review on redlines and sign-off inside their own products. They embed clause-anchored comments, suggestion-mode redlining, approval chains, and the attributed clause history their clients ask for in a dispute, instead of round-tripping redlines through emailed Word files.
See it running in products like yours.
30 minutes, with an engineer, not a sales deck.
Compliance
This buyer's customers bill for discretion, so the strip leads with confidentiality.
Per-thread visibility scopes keep deal-team deliberation off the client's screen, and notifications generate only for documents and threads a user can access. Scoping decides what crosses the matter line.
Data residency options including the EU; self-hosted data providers keep comment and suggestion content plus user PII on your infrastructure, and Velt stores minimal identifiers.
Self-hostingSOC 2 Type II, with an attributed record of who changed and approved every clause, exportable for disputes and client audits.
GovernanceCertifications and qualifiers beyond SOC 2 Type II are verified before they render.
FAQ
Yes. Proposed language lands inline on the exact clause as a pending suggestion showing current and proposed text; the reviewer accepts or rejects each one like a diff, with a reason on reject. Accept fires an event and your code applies the language, so nothing changes the contract without a name attached. Works in supported editors and your own custom components. Suggestions is in beta.
Yes. Threads anchor to the content itself, with robust anchoring to text and complex elements, so the comment on clause 7 stays on clause 7 as the draft moves. If a suggestion's target disappears before review, it goes stale instead of applying.
Yes, when the client's approver is a user in your product. The workflow routes steps in order, counsel to partner to the client's signer, with quorum available where two partners must approve; every decision is timestamped and attributed. Internal-only threads never reach the client. Approval flows is in beta.
No, not when threads are scoped. Any thread can be limited to the author, the team, or specific people, and notifications generate only for what a user can access. The client sees the shared thread move; the deal team's deliberation never reaches their inbox.
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, so a quiet matter costs nothing and a busy closing does not multiply per-user fees. There is a free tier for development and early production.
Free tier. No credit card. First comment in 5 minutes.
30 minutes, with an engineer, not a sales deck.
@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.