Twake Drive – An open-source alternative to Google Drive

Original Article ↗ Hacker News Discussion ↗

Tech stack & architecture

  • Backend is TypeScript/Node.js with MongoDB, which triggers debate:
    • Some see Node/TS as reasonable for I/O‑heavy services and code-sharing with frontend.
    • Others argue a file‑sync system is also CPU‑heavy (hashing, crypto, concurrency) and that JS performance and single‑threaded model will become a bottleneck, similar criticism as for PHP‑based Nextcloud/ownCloud.
  • MongoDB choice is contentious:
    • Several report bad experiences and warn against using it for critical data; others say it’s been “rock solid” for years with WiredTiger.
    • Some note it’s at odds with a “fully open” mission; FerretDB is mentioned as an alternative.
  • Long back‑and‑forth on whether a database is needed at all:
    • One camp says filesystem/ACLs/snapshots/xattrs could store users, permissions, versions, and shareable links.
    • Others counter that complex metadata, joins, transactions, version history, and scalable sync essentially demand a DB.

Comparison with existing tools

  • Twake is compared heavily to Nextcloud/ownCloud:
    • Critics: Nextcloud seen as bloated, slow, and painful to install/maintain (especially outside their AIO stack).
    • Defenders: report years of stable use with Docker or Snap, good ecosystem, but admit rough edges and “2015‑era” web UI.
  • Seafile is praised as fast and reliable but upgrades can be painful.
  • Syncthing widely liked for peer‑to‑peer sync, but mobile and large‑file use cases are weaker.
  • Simple alternatives: filebrowser, Samba shares, rsync; plus other projects like CryptPad, Peergos, Seafile, Immich for photos.

UX, clients, and core features

  • Unclear whether Twake has polished native or mobile clients; screenshots exist but app‑store links are missing.
  • Many emphasize must‑haves for any Drive replacement:
    • Sync that is predictable and explainable to non‑technical users.
    • Simple conflict handling.
    • Zero‑drama upgrades and easy, testable backups.
    • Selective sync with placeholders (Dropbox/OneDrive‑style) is seen as a major gap in many OSS tools.
  • Integration with collaborative editors is crucial; Twake reportedly bundles OnlyOffice for realtime Docs/Sheets‑style editing.
  • Some users care strongly about advanced search (image/content understanding) where Google remains far ahead.

Security, deployment & sustainability

  • Strong warnings against exposing Samba to the internet; VPN (Tailscale/Wireguard) recommended.
  • Concerns about whether Twake can build a durable community and business model so it doesn’t disappear; corporate backing (Linagora, ex‑Cozy Cloud/Cozy Drive) is noted but not deeply analyzed.
  • Debate over name “Twake” and domain; some think it’s hard to say/spell and thus hurts adoption.