TinyDocy is a free, open-source (MIT) document editor where several people edit the same page at once and see each other's cursors. It is built with Tiptap 3, Yjs and Hocuspocus, needs no account, installs as an app, and keeps working offline. It is the public testbed for docs.plus: editor features land here first and move to docs.plus once they pass collaboration and scale checks.

Live demo: tiny.docs.plus. Open it in two windows and watch edits sync. It is a public sandbox: everyone sees the same documents, so don't type anything private.

• Features
• Quick start
• How it works
• Configuration
• Deploying
• Development
• Documentation
• Community

Requires Bun 1.4.4 or later. Node.js is not needed: Next.js, ESLint, Playwright and the git hooks run on the Bun runtime ([run] bun = true in bunfig.toml), and unit tests use bun test.

bun install

Then start both services:

make dev

Open http://localhost:3000, then open the same address in a second window to see collaboration.

make dev runs two processes:

The service worker and offline page register only in production builds. To try them locally, build and start the app:

bun run build && bun run start

flowchart LR
  subgraph Browser
    UI[Next.js app<br/>skeleton → editor]
    SW[Service worker<br/>pages + static files]
    IDB[(IndexedDB<br/>offline copies)]
    UI <--> IDB
    UI -. offline fallback .- SW
  end
  UI <-- "one shared WebSocket<br/>(Yjs sync)" --> HP[Hocuspocus 4<br/>Bun.serve]
  UI -- "DELETE /api/documents/:id" --> API[Next.js route]
  HP <--> DB[(SQLite<br/>documents, activity,<br/>tombstones)]
  API --> DB

• Documents are Yjs docs. Each tab is one document; the tab list itself is a shared document named global-tabs. Hocuspocus stores the encoded state in SQLite and enforces the guardrails in lib/security/.
• One WebSocket per browser tab. lib/collab-session.ts multiplexes every document on a shared socket. It reuses sessions across remounts, keeps sessions with unsynced edits alive, and restores offline copies (lib/offline/) before the socket attaches.
• The page renders before the editor loads. The server sends an app-shell skeleton with real intro text (good for SEO and slow connections). The editor bundle loads separately while the tab list syncs.
• Editor extensions are layered. Heading fold, drag, filter and scale live in extensions/ and work in any Tiptap 3 app. Links, inline code, indent, placeholders, Mermaid and media come from the @docs.plus/extension-* packages.

app/                 Routes: editor, /about, /privacy, /offline, metadata, API
components/
  app-skeleton/      Server-rendered loading shell
  document-editor/   The integrated editor
  editor-app/        Client shell: tabs, lazy editor, offline states
  pwa/               Service worker registration, install button, offline UI
  tab-bar/  toc-sidebar/  tiptap-ui/  tiptap-node/  ui/ (shadcn/ui)
extensions/          Standalone Tiptap extensions (heading-*, render-once,
                     table-of-contents, title-document)
hooks/               React hooks (synced tabs, Yjs document, connection state)
lib/
  collab-session.ts  Shared sessions on one socket
  offline/           Offline document copies (IndexedDB)
  pwa/               Service worker and its routing rules
  security/          Guardrails, CSP, tombstones, rate limits
scripts/             Hocuspocus server, retention purge
tests/               Unit, e2e, PWA, perf, soak, load (see tests/TESTING.md)
docs/                Runbooks, plans, brainstorms

Everything is configured through environment variables, and most of them have safe defaults. There are two kinds.

These are inlined by bun run build. Put them in .env.production before building; setting them at runtime has no effect.

These are read when the Next.js app, Hocuspocus or the retention script starts. The full list, with defaults, is in lib/security/guardrail-config.ts; operational guidance is in the abuse guardrails runbook.

Production runs as three PM2 processes defined in ecosystem.config.cjs: Next.js on 3847, Hocuspocus on 3848, and an optional Redis on 6380. They sit behind a TLS-terminating reverse proxy.

To deploy or update:

git pull && bun install --frozen-lockfile && bun run build && bunx [email protected] restart ecosystem.config.cjs --update-env

Requirements:

• TLS and the proxy. The collaboration URL must be wss://. Only the proxy may reach the app ports, because TRUSTED_PROXY=1 trusts its forwarding headers.
• Service worker headers. The proxy must not change Cache-Control on /_next/static/service-worker/sw.js; it must stay public, max-age=0, must-revalidate.
• Retention. Run bun scripts/purge-retention.ts daily (cron or a systemd timer) and rotate the PM2 logs; abuse events contain IP addresses.
• Taking content down. Delete the document; never reset its stored state, because offline copies would push it back.

Release notes for each change, including deploy steps, are in the changelog.

Test layers, environments and CI notes: tests/TESTING.md.

Conventions:

• Bun only (bun, bunx; never npm or npx).
• Conventional Commits, enforced by commitlint.
• Named exports; kebab-case files; PascalCase components with title-case acronyms.
• shadcn/ui for new UI.
• Every pull request adds an entry to CHANGELOG.md.

The full conventions are in AGENTS.md.

Stack: Bun · Next.js 16 (App Router, Turbopack) · React 19 · Tiptap 3 and ProseMirror · Yjs and Hocuspocus 4 · SQLite · Tailwind CSS 4 and Sass · TypeScript (strict) · Biome, ESLint, Husky and commitlint · bun test and Playwright.

CI (.github/workflows/ci.yml) runs on every pull request and push to main. One job runs bun audit, Biome, ESLint, the typecheck, unit tests and the production build; the other runs the Playwright Chromium suite. A nightly workflow (.github/workflows/nightly.yml) runs the service worker, soak and load layers twice a day (03:41 and 08:00 UTC).

Releases: tag main with vX.Y.Z and push the tag; .github/workflows/release.yml publishes the GitHub release, listing the pull requests merged since the previous tag and linking to CHANGELOG.md.

The @docs.plus/extension-* packages are refreshed daily (04:17 UTC) by .github/workflows/docs-plus-extensions.yml. It opens a pull request after a read-only verification job, which needs "Allow GitHub Actions to create and approve pull requests" in the repository's Actions settings.

TinyDocy is the validation testbed for docs.plus: features are proven here before they land in the production editor.

• docs.plus: the live platform
• docs-plus/docs.plus: the production repository
• Discord: the community

MIT. See LICENSE.