Public beta available — Start here
Stesura

A Web-based Word processor that is powered by Prosemirror

Drop in as a component, extend and ship a word processor in your app.

Try the demos →

The live editor needs a bigger screen. Open this page on a desktop to try it — or explore the demos.

This document is all json.

For those who need a word processor in their app with a modern API and flexibility to match their value proposition.

Keep control of your data and your users on your app. Focus on building what makes your app special, don't spend months building a word clone.

And everything else to extend it and make it a pillar of your app.

A basic word processor is not enough. You want a a modern flexible processor whose api can comform to your app?

The whole ProseMirror API

Write plugins, change the schema, add your own nodes and marks, hook the transaction pipeline. Not a configuration object — the actual editor.

React inside the editor

NodeViews are real React components in your tree, with your context and your state. No portals, no second subtree, no overhead.

Editable on the server

Dispatch transactions from your backend while clients collaborate on the same document. Same schema, same validation as a keystroke.

Collaboration you host

Real-time editing on your own servers, against your own database. Documents never transit anyone else's infrastructure, including ours.

Runs on the client

A React component that does its work in the browser. No editing service to keep up, no per-document round trip.

* Proofreading, collaboration and PDF export are the exceptions as they run server-side.

A JSON document model

The document is a typed JSON tree, not an opaque blob. Diff it, validate it, generate it, and store it wherever the rest of your data lives.

Real HTML, not a canvas

The document is the DOM. Accessible by design — no pixel buffer to reimplement a11y against.

Your chrome, not ours

Build your own toolbar, menus, popovers, hover cards — whatever the rest of the app already uses. The editor does not own the chrome.

Your CSS

Theme it with the tokens you already have. No iframe, no sealed skin, no second design system to maintain.

What sets us apart

A full document stack, one package at a time.

Start free with the editor foundation. Add the premium packages — pagination, review, references, PDF, AI — as you need them.

Open-source core. Premium add-ons.

Ship the whole editor foundation from the open-source core. Add premium packages only where your product needs them.

Open-source corefree

The full editor foundation, MIT-licensed.

The entire schema, commands, and UI elements
Real-time collaboration
Multi-section layouts
Legal numbering
Advanced formatting
Stylesheets
Premium add-onslicensed

Bolt on as your product grows.

Pagination — headers & footers, first / even / odd pages
DOCX import & export
References — footnotes, endnotes, cross-references
Track changes
AI — autocomplete & document chat
Proofreading — 30+ languages, RTL
For your clients' users

Your clients deserve a real text editor.

The people inside your product open documents all day. Give them the desktop word processor they already know — in the browser, with nothing to install.

Familiar, accessible, and faithful to the page — so the document your client signs is exactly the one they saw on screen.

Familiar from day one

The Word-like surface your users already know — no training, no migration.

Nothing to install

Runs in any modern browser, on any OS — Chromebook and Linux included.

Accessible by default

Keyboard-first and screen-reader aware, built on real HTML semantics.

Documents they can trust

True pages, legal numbering, and footnotes that print exactly as shown.

Frequently asked questions

Are you going to do a non-React version?

Can I use the packages server-side?

Can I use this with Yjs for collab?

What happens if I downgrade from the premium packages to the free ones?

What about security?

Is it extensible?

Put a real word processor in your product.

Book a demo, or start with the open-source core today.

Want to know why we build this? Read it here: