Read the DocsContact us

A document editor component for your web app

Tell your coding agent:

The Revise SDK adds a powerful document editor to your application in minutes, with manual and agentic editing in the same interface.

Integrate in minutes

Render the component, pass in a file, and listen for changes.

The Revise SDK runs entirely in the browser, and on your servers. Use the backend package to build your own persistence, collaboration, or server-side editing.

Read the Docs

import ReviseEditor from "revise";
import "revise/style.css";

export function DocumentPane({ file }) {
  return (
    <ReviseEditor
      initialDocuments={[{ id: "msa", title: "Agreement", source: file }]}
      onChange={(id, document) => saveDraft(id, document)}
    />
  );
}

Examples

Six small, open-source apps built on the SDK. Each is a standalone project you can clone and run.

Tools for your agent

Revise was designed for agentic editing. The SDK exposes tools for editing and formatting text, leaving comments, and adjusting page layout — all with tracked changes.

Expose the editor tools in your agent loop and feed the results back in to add collaborative document editing to your AI product.

Live collaboration

Revise supports collaboration among people and agents. Pass in a Yjs provider to share the document with live carets, presence, and participant roles.

Use the backend package to run your own sync server, persist changes, and propose tracked changes from a service. The same tool contract works in the browser and on the server.

Try collaboration in the interactive demo below:

Pricing

Free for evaluation and personal projects. Buy a commercial license online, or talk to us about enterprise terms.

Free

Free

For evaluation and testing, personal noncommercial apps, and accredited schools.

  • Full DOCX editor library
  • Backend syncing & collaboration
  • Tracked changes & comments
  • All major file formats
  • Tools API for AI agents
  • No open source requirement
Get started

Commercial

$2,000

For production use by businesses, nonprofits, and government, including internal tools.

  • Everything in Free
  • Commercial use in one application
  • License key delivered instantly
  • Email support

See the Commercial License for details

Enterprise

Let’s talk

For high touch support, source code access, and custom terms.

  • Everything in Commercial
  • Multiple applications
  • Source code access
  • Support SLAs

Or email sdk@revise.io

Have questions? Reach out to sdk@revise.io.

Start building with the Revise editor

Read the DocsContact us

Common questions

Do my documents pass through Revise servers?

No. The editor runs entirely inside your app, and documents move only between your users' browsers and your own servers. There's no Revise account, API key, or hosted backend to depend on: storage, real-time collaboration, and server-side editing all run on your infrastructure through revise/server.

The only request the SDK makes on its own is an anonymous usage ping with the SDK version and your site's origin. It never includes document data or cookies, we don't store IP addresses, and you can turn it off with telemetry={false}.

How the usage ping works

Is the Revise SDK open source?

No, and we don't pretend to be. The SDK is proprietary software under a short, plain license: free for evaluation, personal noncommercial apps, and education, with a commercial license for production use. There's no copyleft license wrapped around a closed engine, and nothing in our terms reaches into your own code.

Commercial customers can get source code access as part of their agreement, so your team can audit and build the editor you ship.

Ask about source access

Which AI models does it work with?

Any model that supports tool calling. The editor hands your agent its editing tools as JSON schemas and runs the calls your agent makes, so you can use Claude, GPT, Gemini, or a self-hosted model with your own prompts and keys.

How well does it handle Word documents?

Revise opens DOCX files with Word-style page layout and exports them back to DOCX. Tracked changes, comments, footnotes, tables with merged cells, multi-column sections, headers and footers, list numbering, and styles all make the round trip.

It's the same engine that powers the Revise editor, where people edit real Word documents every day.