Skip to main content
The Revise SDK is proprietary, closed-source software published on npm so you can install it without asking us first.

Evaluation

Free, with no time limit: develop, test, and prototype, including for a product you plan to sell.

Personal and education

Free in production for an individual’s noncommercial projects, and for accredited nonprofit or public schools, colleges, and universities.

Everything else

Production use by businesses, nonprofits, and government needs a paid license. Email sdk@revise.io.
The full terms ship with the package in its LICENSE file. If this page and that file ever disagree, the LICENSE file wins.

​
Common questions

Yes. Install it, build a prototype, and test it on your own documents, with no time limit. You need a license before it goes into production, including internal tools and products that are free or not yet earning.
Not in production. Nonprofits and government entities need a license to deploy it, whether or not the app earns money. Evaluation is free.
Yes, for accredited nonprofit or public schools, colleges, and universities: teaching, learning, research, and your own internal operations. For-profit schools, and companies building products for schools, need a license.
Yes, if it is yours as an individual and is not meant to make money, promote a paid offering, or support an organization. Ads, subscriptions, or a paid tier make it commercial, even before it earns anything.
Yes. The document tools and agent integration ship in the same package and under the same terms as the rest of the SDK: free for evaluation, personal projects, and education, and covered by a commercial license otherwise. Revise’s hosted agent is billed separately through the Revise API.
No. Unlike the AGPL, using the SDK never obliges you to release your own code.
No. The package ships as a compiled bundle, and the license does not allow decompiling, reverse engineering, or modifying it. Configuring it through its documented options is fine.
Once per page load, the editor sends one anonymous ping to api.revise.io so we know where Revise is running. It carries the SDK version; your browser adds your site’s origin (for example https://app.example.com). For production sites we keep only that origin and version. From localhost and other development hosts we keep less: a daily count per version, with no origin at all. The ping sets no cookies, is left out of our request logs, and carries no user data or document content.Turn it off with <ReviseEditor telemetry={false} />. Nothing else connects to Revise unless you configure Revise’s hosted agent yourself.