Everything your editor backend needs
A complete, production-oriented backend for RichTextEditor — collaboration, storage, conversion, and account management in one service.
Real-time multiplayer
CRDT-based editing so multiple people can type in the same document with no conflicts.
Live cursors & presence
See who else is in the document and where their caret is.
Per-document authorization
Short-lived, room-scoped tokens — users only join rooms they're granted.
Graceful degradation
If the collab server is unreachable, the editor falls back to single-user with autosave.
Cloud storage
Create, read, update, and delete documents through a clean REST API.
Autosave workspace
A Google-Docs-style editor that saves as you type.
Timestamps & ordering
Every document tracks created and updated times; lists come back newest-edited first.
Tenant isolation
Every API key is an isolated tenant; documents never leak across accounts.
HTML ⇄ Markdown ⇄ JSON
Round-trip between formats with the same engine the editor uses on the client.
Consistent output
What the editor converts matches what it renders — one engine, no drift.
Metered per plan
Monthly conversion allowances scale with your plan.
Accounts & sessions
Registration, login, expiring sessions, and secure password hashing (PBKDF2).
API keys & quotas
Per-account keys with plan-based limits enforced automatically.
SQL Server backed
Runs on SQL Server behind IIS — fits neatly into a Windows stack.
Self-host or hosted
Identical API whether you run it yourself or use the managed service.
The managed API exposes accounts, API keys, and document storage today. Real-time collaboration and format conversion run in the editor runtime and are metered by your plan; managed server-side endpoints for both are on the roadmap.
Start free