dDocs (Fileverse dDocs) is an end-to-end encrypted collaborative document editor written in TypeScript, licensed under AGPL-3.0, published as the @fileverse-dev/ddoc package and offered as a hosted app at ddocs.new, and it is built for developers and privacy-conscious teams who want multiplayer document editing without giving up control of the underlying data.

What it is

dDocs is an open-source, end-to-end encrypted document editor that the README describes as a privacy-focused alternative to Google Docs. The repository ships the core editor under /package, alongside example and demo source code that showcases what the editor can do. The editor is consumed as a React component named DdocEditor, imported from @fileverse-dev/ddoc with a companion stylesheet, and it is designed to sit inside an application that already uses Tailwind CSS rather than standing alone as a finished hosted product in the repository itself.

The concrete problem it solves is ownership. In a conventional cloud document suite, the storage provider holds the plaintext of every document and effectively acts as the authority on who may read it. dDocs moves that authority to the user: content is encrypted end to end, private access permissions are enabled through zero-knowledge proofs, and account and file recovery is handled through private social recovery that also relies on zero-knowledge proofs. Import and export of .docx, .md, .pdf, .html and other formats keeps documents portable, so adopting the editor does not trap content inside a single vendor's file model.

Key capabilities

• End-to-end encryption applied across the document lifecycle, including an end-to-end encrypted, programmable API optimised for agents on an opt-in basis.
• Real-time and asynchronous collaboration, configured through the enableCollaboration, collaborationId, username, setUsername, walletAddress and onCollaboratorChange props on the DdocProps interface.
• Suggestion mode with tracked changes, plus commenting, so review happens inside the document instead of in a separate thread.
• Markdown and LaTeX support, alongside MermaidJS diagram rendering.
• Import and export of .docx, .md, .pdf, .html and more, which keeps documents movable between dDocs and other editors.
• Offline and online editing, extended by enableIndexeddbSync and ddocId, so users can continue writing and open older documents with no WiFi connection, with cross-device syncing across desktop and mobile.
• Version history, dark mode and colour themes, and a mobile-optimised webapp delivered as a PWA.
• Editor-level control through initialContent, onChange, ref, isPreviewMode, editorCanvasClassNames, ignoreCorruptedData and onInvalidContentError.

Who uses it and how

• Product teams embedding a document editor directly into their own React application, using DdocEditor as a component and keeping encryption in their own stack.
• Privacy-sensitive organisations that need multiplayer editing but will not accept a provider holding plaintext or controlling access, and that prefer zero-knowledge proof based permissions and social recovery.
• Distributed teams working across desktop and mobile, including the installed PWA, where offline editing and later IndexedDB sync matter for intermittent connectivity.
• Agent and automation workflows that use the opt-in, end-to-end encrypted programmable API to operate on document content.
• Any user who starts on the hosted ddocs.new instance and exports to .docx, .md, .pdf or .html when handing work to people outside the tool.

Getting started

The README documents the package route: install the peer dependencies with npm install @dnd-kit/core @dnd-kit/sortable @dnd-kit/utilities @fileverse/ui @fileverse/crypto viem framer-motion frimousse, then import { DdocEditor } from '@fileverse-dev/ddoc' together with '@fileverse-dev/ddoc/styles' in App.jsx or App.tsx, and add @fileverse-dev/ddoc/dist/index.es.js to the content array in the Tailwind config. A hosted option also exists at ddocs.new for users who would rather not wire the package up themselves.

How it compares

Against Google Docs, the comparison the README draws, dDocs is AGPL-3.0 licensed open source rather than a proprietary hosted service, and its end-to-end encryption means the operator does not hold readable document contents. Access permissions and file recovery are enforced with zero-knowledge proofs instead of an account system administered by the vendor, and the component can be embedded in an application the operator already controls.

When to use it — and when not to

A self-hoster must already run a project with Tailwind CSS and a Tailwind configuration file, and must accept the peer dependency set above, including viem and @fileverse/crypto. Anyone working outside React and Tailwind, or expecting a turnkey server deployment, should look elsewhere: this repository documents the editor package plus demo code, and it does not describe how to operate the hosted service or any backend infrastructure behind it. The registry entry also lists no topics, so discovery metadata is sparse and the README is the main source of truth.

import { DdocEditor } from '@fileverse-dev/ddoc';
import '@fileverse-dev/ddoc/styles'; // in App.jsx/App.tsx

npm install @dnd-kit/core @dnd-kit/sortable @dnd-kit/utilities @fileverse/ui @fileverse/crypto viem framer-motion frimousse

interface ThemeVariantValue {
  light: string;
  dark: string;
}

interface DocumentStyling {
  /**
   * Background styling for the outer document area.
   * Supports CSS background values including gradients.
   * Example: "linear-gradient(135deg, #667eea 0%, #764ba2 100%)"
   */
  background?: string | ThemeVariantValue;

  /**
   * Background color for the editor canvas/content area.
   * Should be a solid color value.
   * Example: "#ffffff" or "rgb(255, 255, 255)"
   */
  canvasBackground?: string | ThemeVariantValue;

  /**
   * Text color for the editor content.
   * Example: "#333333" or "rgb(51, 51, 51)"
   */
  textColor?: string | ThemeVariantValue;

  /**
   * Font family for the editor content.
   * Example: "Inter, sans-serif" or "'Times New Roman', serif"
   */
  fontFamily?: string;
}

<DdocEditor
  documentStyling={{
    background: {
      light: 'linear-gradient(135deg, #667eea 0%, #764ba2 100%)',
      dark: 'linear-gradient(135deg, #2a3145 0%, #3a2f59 100%)',
    },
    canvasBackground: { light: '#ffffff', dark: '#1e1f22' },
    textColor: { light: '#333333', dark: '#e8ebec' },
    fontFamily: 'Inter, sans-serif',
  }}
  // ... other props
/>