Open-source document collaboration, honestly reviewed. The Web3 angle is real, the community is skeptical, and the deployment story is nothing like you’d expect.

TL;DR

What it is: An open-source, end-to-end encrypted document editor from Fileverse — marketed as an “onchain, privacy-first alternative to Google Docs” [README]. In practice it’s two things: a hosted service at ddocs.new, and an npm React component package for developers who want to embed the editor in their own app.
Who it’s for: Privacy-focused founders and developers who want document collaboration without their content touching Google’s servers, and who are comfortable with (or at least tolerant of) a Web3-flavored architecture. Also React developers looking to embed an encrypted collaborative editor in their own product.
Cost savings: Pricing data for ddocs.new is not publicly available. The npm package itself is free (AGPL-3.0). If you build on the package, your hosting costs are whatever your app runs on.
Key strength: Genuine peer-to-peer, end-to-end encryption with real-time collaboration — in a category where most “privacy-first” tools are just self-hosted versions of the same centralized architecture [README].
Key weakness: 186 GitHub stars, near-zero third-party coverage, community skepticism about long-term viability, and a blockchain dependency that adds meaningful technical complexity without a clear benefit for most users [5].

What is dDocs

dDocs is a document editor built by Fileverse, a company positioning itself in the privacy-first collaboration space with a Web3 twist. The GitHub repository (fileverse/fileverse-ddoc) contains the core editor package, published to npm as @fileverse-dev/ddoc. The live product is accessible at ddocs.new.

The README’s opening pitch: “your onchain, privacy-first alternative to Google Docs. A self-sovereign note-taking and collaboration app that is peer-to-peer, end-to-end encrypted, and decentralized.” [README]

The word “onchain” is doing a lot of work there. dDocs integrates with Ethereum wallets — the DdocProps interface includes a walletAddress field, and the peer dependency list includes viem, an Ethereum interface library [README]. This is not a cosmetic integration. The architecture is built around blockchain-based identity and storage, which is both the product’s most interesting feature and the thing most likely to make non-technical founders close the browser tab.

Under the hood, the editor is built on TipTap (a ProseMirror wrapper), supports Markdown and LaTeX, has real-time collaboration via a collaborationId session system, IndexedDB sync for offline editing, and mobile browser optimization [README]. The package ships as a React component that you drop into a project already using Tailwind CSS.

The website scrape for ddocs.new returned empty content — no meta description, no H1, no body text [scrape data]. Either the site is entirely client-side rendered, or the homepage is sparse to the point of being decorative. Neither is a great sign for a product trying to onboard non-technical users.

Why people choose it

Coverage of dDocs specifically is thin enough that most of the signal comes from the broader Fileverse discussion on Privacy Guides [5] and inference from general self-hosting conversations [1][4].

The privacy argument is real. The self-hosting community that talks seriously about document privacy tends to land on two concerns: data residency (who can read your files) and vendor lock-in (what happens when the service changes pricing or shuts down). An author on XDA Developers describes why they moved away from cloud productivity tools entirely: “I was getting uncomfortable with how much of my personal notes and projects were in the cloud. All of it was also tied to services that could change, lock their features, disappear, or even access my data in some cases.” [4] End-to-end encryption at the architecture level — not as an optional feature — directly addresses the first concern. The peer-to-peer model addresses the second.

The competition has trade-offs too. The Privacy Guides thread [5] that discusses Fileverse frames the alternatives as Nextcloud + OnlyOffice or Cryptpad. Nextcloud is mature and well-documented but requires serious self-hosting chops and ongoing maintenance. Cryptpad is the honest comparison — also open-source, also end-to-end encrypted, more established. The thread’s initial assessment of Fileverse: “Nextcloud + OnlyOffice seem highly preferable at the moment as they are true FOSS self-hostable projects that have been around for a long time.” [5]

Why someone might still pick dDocs: If you’re a developer building a product and want to embed an encrypted collaborative editor without building one from scratch, the npm package approach is genuinely useful. The alternative is CKEditor, Quill, Slate, or TipTap directly — and none of those ship with E2E encryption and P2P collaboration out of the box.

Features

From the README and package API documentation:

Core editing:

Rich text editor with Markdown support [README]
LaTeX rendering [README]
Dark mode [README]
Offline editing with IndexedDB sync [README]
Mobile browser optimization [README]
Preview/read-only mode [README]
Drag-and-drop block reordering via dnd-kit [README]

Collaboration:

Real-time collaboration sessions via collaborationId [README]
Collaborator presence tracking with display names [README]
Async collaboration support [README]
Wallet address integration for Web3 identity [README]

Privacy/Encryption:

End-to-end encryption (via @fileverse/crypto peer dependency) [README]
Peer-to-peer architecture — documents don’t route through a central server [README]

Developer integration:

Ships as a React component: <DdocEditor /> [README]
onChange callback for content changes [README]
ref for programmatic editor access [README]
Requires Tailwind CSS and specific peer dependencies [README]
TypeScript types via DdocProps interface [README]

What’s not here: No SSO, no RBAC, no audit logs, no webhook integration, no API beyond the React component interface. This is a document editor component, not a document management platform.

Pricing: SaaS vs self-hosted math

ddocs.new (hosted service): Pricing is not publicly documented. The website returned empty content in the scrape [scrape data], and no pricing page is referenced in the available sources. Data not available.

npm package (self-hosted / embedded): Free to use under AGPL-3.0. You’re responsible for your own infrastructure, which means this is only “free” if you’re already running a React app and have the technical capacity to integrate it. AGPL-3.0 has a specific implication: if you use this in a networked service (SaaS), your application code must also be open-sourced under AGPL [LICENSE]. This matters if you’re building a commercial product on top of it.

Google Docs for comparison: Free for individuals, $6/user/month for Google Workspace Business Starter. No self-hosted option.

Cryptpad for comparison (the honest alternative): Free tier available, hosted plans start at €5/month. Full self-host option exists. Has been running since 2014. MIT and AGPL licensed [community comparison — 5].

The economics here depend entirely on what you’re building. If you’re a solo founder using Google Docs, dDocs is not going to save you money — it’s going to add complexity. If you’re building a product that needs collaborative document editing and you want to avoid licensing fees for something like CKEditor’s commercial tier, the package is worth evaluating.

Deployment reality check

This is where dDocs diverges most sharply from typical self-hosted tools reviewed in this space.

There is no Docker container. There is no docker-compose.yml. There is no “install on a VPS in 30 minutes” path. dDocs is an npm package that you install inside a React application you’re building or already running [README].

What you actually need to use the package:

An existing React project with Tailwind CSS configured [README]
Install 8 peer dependencies: @dnd-kit/core, @dnd-kit/sortable, @dnd-kit/utilities, @fileverse/ui, @fileverse/crypto, viem, framer-motion, frimousse [README]
Update your Tailwind config to include the dDocs dist path [README]
An Ethereum wallet integration if you want the identity/encryption features to work as designed [README]

The Tailwind config update is a minor footgun: you must add @fileverse-dev/ddoc/dist/index.es.js to your content array or the editor’s styles won’t render correctly [README].

The viem dependency is the real signal. viem is a TypeScript library for Ethereum. This is not optional cruft — it’s core to how dDocs handles identity and possibly storage. If you’re a non-technical founder who has never touched a blockchain, this dependency chain will either break your setup or require you to hand the integration to an engineer.

To use ddocs.new directly (the hosted service): You don’t need to install anything. It’s a web app. But pricing is unknown and you’re trusting Fileverse’s infrastructure with your documents, which somewhat undercuts the privacy pitch.

What can go sideways:

The Privacy Guides thread [5] flags that Fileverse’s website has dependencies on “questionable crypto websites and Google fonts” — a reviewer using NoScript caught third-party requests that undercut the privacy-first positioning
One detailed reviewer on Privacy Guides describes the project as driven by “hype hype hype” and “SHIP FAST!” mentality, with questions about long-term stability: “looking at the dDocs.new packages, there is nothing very sturdy and project will probably just be dead in 6 months when the maintainers are bored of this current project” [5]
186 GitHub stars and no visible traction in the self-hosting community [merged profile]
Empty website at time of scrape [scrape data] — unclear if this was a scraping issue or genuinely thin content

Pros and Cons

Pros

Genuine E2E encryption at the architecture level. Not a feature toggle — the encryption is baked into the component’s peer dependency stack [README]. For users who need document content to be unreadable to the service provider, this is a meaningful technical guarantee.
Peer-to-peer collaboration. Real-time and async collaboration without central server routing. Documents don’t pass through Fileverse’s infrastructure in plaintext [README].
Offline editing. IndexedDB sync works without a network connection, and sync picks up when reconnected [README].
Rich feature set for an npm package. Markdown, LaTeX, dark mode, mobile optimization, drag-and-drop blocks — more polished than rolling your own TipTap integration [README].
AGPL-3.0. Free to use, modify, and self-host. Open codebase you can audit [merged profile].
npm distribution makes it trivially embeddable in existing React applications [README].

Cons

Web3 dependency is mandatory, not optional. The viem peer dependency and wallet address integration mean you’re shipping Ethereum tooling into your stack even if you don’t want the blockchain features [README]. This adds bundle size, adds conceptual complexity, and will confuse developers (and users) who aren’t Web3-native.
186 GitHub stars. For context, Cryptpad has 6,400+. Actual has 9,000+. n8n has 100,000+. dDocs is a micro-project with no demonstrated community gravity [merged profile].
Community skepticism about longevity. The Privacy Guides review is harsh but specific: “nothing more than hype hype hype”, questions about whether maintainers will abandon it [5]. This is a legitimate concern for any tool you’re building business processes on.
Fileverse website privacy concerns. The same privacy-focused community that is dDocs’s target audience flagged third-party dependencies (crypto sites, Google Fonts) on the Fileverse website itself [5]. The gap between the privacy pitch and the actual network footprint is a credibility problem.
Not a standalone self-hosted app. Non-technical founders cannot deploy this on a VPS. There’s no Docker image, no installation guide for servers, no admin panel [README]. You’re either using the hosted ddocs.new or you’re embedding the npm package into an app you’re already building.
AGPL license has commercial implications. Using this in a SaaS product requires open-sourcing your application code. Many founders will need to read the license carefully before integrating [merged profile].
Empty website. At time of research, ddocs.new returned no indexable content [scrape data]. Pricing unknown. Unclear what the hosted product actually offers versus the open-source package.
No pricing transparency. Can’t evaluate cost savings versus Google Workspace without knowing what ddocs.new charges [scrape data].

Who should use this / who shouldn’t

Use dDocs if:

You’re a React developer building a product that needs embedded collaborative document editing with genuine E2E encryption, and you’re comfortable shipping Ethereum dependencies.
You’re privacy-focused to the point where you’d rather accept significant setup complexity than trust any central server with document content.
You understand the AGPL license implications for your use case.
You’re experimenting and 186-star project risk is acceptable for your context.

Skip it (use Cryptpad instead) if:

You want E2E encrypted collaboration as a service or straightforward self-hosted deployment. Cryptpad has been running since 2014, has real community support, and doesn’t require blockchain integration [5].

Skip it (use Nextcloud + OnlyOffice) if:

You want a full document management system with file storage, sharing, and office editing in one self-hosted package. More setup work, but substantially more mature and well-documented [5][4].

Skip it entirely if:

You’re a non-technical founder with no developer resources. There is no path to self-hosting dDocs that doesn’t require writing code.
You need pricing transparency before committing. Data not available [scrape data].
You need a project with demonstrated longevity. The community assessment is not reassuring [5].

Alternatives worth considering

Cryptpad — The honest comparison. E2E encrypted, open-source (AGPL), self-hostable via Docker, no blockchain dependencies, running since 2014. Has a real self-hosted install path. More community trust.
Nextcloud + OnlyOffice — More complex to self-host but the most complete privacy-first office suite available. Nextcloud handles file storage and user management; OnlyOffice handles documents. Recommended by the Privacy Guides community over Fileverse [5].
AFFiNE — Hybrid PKM/doc editor, self-hostable, PostgreSQL + Redis backend [4]. Closer to Notion than Google Docs, but worth evaluating for knowledge management use cases.
Docmost — A wiki/notes hybrid for teams that want self-hosted knowledge bases [4]. Less about E2E encryption, more about ownership of the data.
Google Docs — Free, genuinely excellent, trusted by billions. If your threat model doesn’t require E2E encryption, the case for switching to anything on this list is weak.
HedgeDoc — Self-hostable Markdown collaboration tool. No blockchain, no frills, works.

Bottom line

dDocs is a technically interesting npm package in search of a product. The privacy architecture is real — peer-to-peer, end-to-end encrypted collaboration is a hard problem and the component solves it. But the blockchain dependencies, the 186-star GitHub project, the empty website, the unknown pricing, and the community skepticism about Fileverse’s durability add up to a tool that requires significant trust to bet on. The self-hosting community’s instinct to reach for Cryptpad or Nextcloud instead [5] is correct for most use cases. If you’re a React developer specifically looking to embed encrypted collaborative editing in your own app — and you’ve audited the AGPL implications — the package is worth a prototype. If you’re a founder trying to escape Google Docs, there are more reliable tools with clearer paths to deployment and better answers to “will this still exist in two years.”

Sources

Kitchen-Patience8176, r/selfhosted — “Best Self-Hosted Open Source Document Management?” (2025). https://www.reddit.com/r/selfhosted/comments/1r9icxn/best_selfhosted_open_source_document_management/
Ferndesk — “Docusaurus Review 2026: The Free Documentation Tool With Hidden Costs” (2026). https://ferndesk.com/blog/docusaurus-review
Fern / buildwithfern.com — “Self-Hosted Documentation Tools January 2026” (Jan 2026). https://buildwithfern.com/post/self-hosted-documentation-tools-enterprise-security
Nolen Jonker, XDA Developers — “I started self-hosting my entire productivity stack, and I’m never going back” (Jan 29, 2026). https://www.xda-developers.com/started-self-hosting-entire-productivity-stack/
Privacy Guides Community — “Thoughts on Fileverse?” (Sep 2025 – Feb 2026). https://discuss.privacyguides.net/t/thoughts-on-fileverse/30800

Primary sources:

GitHub repository and README: https://github.com/fileverse/fileverse-ddoc (186 stars, AGPL-3.0)
npm package: @fileverse-dev/ddoc
Product website: https://ddocs.new

Replaces

Related Office & Productivity Tools

View all 75 →

Excalidraw

119K

Open-source virtual whiteboard for sketching hand-drawn style diagrams, wireframes, and architecture charts — collaborative and end-to-end encrypted.

office MIT

reveal.js

71K

The open-source HTML presentation framework — create beautiful, interactive slide decks using HTML, Markdown, or a visual editor, with 70K+ GitHub stars.

office MIT

tldraw

46K

Infinite canvas whiteboard with real-time collaboration. Embed in your app as a React component or use as a standalone drawing tool. No signup required.

office

Penpot

45K

Penpot is the open-source design and prototyping platform that bridges designers and developers with web-native standards, real-time collaboration, and no vendor lock-in.

office MPL-2.0