ARCHITECTURE · COMPARISON

Nabu and the others

If you write Svelte and need a rich editor, these are your real options. Where Nabu is different, where the others are clearly ahead, and how we checked.

Your real options in Svelte

Svedit

Svelte 5 native · alpha
Engine
its own
Collab
not stated

The closest to Nabu: Svelte 5, one contenteditable. Younger, no collaboration story.

Where Nabu is different

  • Svelte 5 nativeNo wrapper around another engine. Blocks are Svelte components, state is runes.
  • The CRDT is the documentNot a binding that syncs another model: the Loro tree and text are what you edit.
  • Local-first in the boxIndexedDB, merge across tabs, backup and quarantine, an asset store. Elsewhere: y-indexeddb and your own wiring.
  • Nothing paidMIT. No cloud tier, no GPL packages.
  • Undo that puts the caret backEven after remote edits, on stable Loro cursors.

Where the others are clearly ahead

  • MaturityYears in production, tens of thousands of stars. Nabu: beta, one author, first alpha in March 2026.
  • TablesTiptap, ProseMirror, Lexical, BlockNote, Plate have them. Nabu has none.
  • Network collaborationReady-made servers and providers. Nabu gives you the CRDT bytes; you write the transport.
  • Mobile and browsersYears of Android fixes elsewhere. Nabu is tested in Chromium only.
  • WeightLoro’s WebAssembly is 1.2 MB gzipped. Yjs is 28 KB.
  • ReachNabu is Svelte only. Others serve React, Vue and plain JS.

Side by side

So, which one?

  • Tiptapif you need tables, network collaboration and a large ecosystem of extensions today, and a paid cloud for collaboration is fine.
  • ProseKitif you want ProseMirror’s maturity with a Svelte adapter and room to build your own UI.
  • Nabuif you build in Svelte 5, your documents must survive crashes, tabs and offline without a server, and you can ship a beta.
What Nabu doesn’t do well (yet) →