Collaboration Without the Server Reading Your Document

What this means for you

You can run a real-time shared document, with multiple people editing at once, without the server ever seeing what is written. The merge still works. The order is still correct. Nobody at the host can read the page.

The pitch

Fork Node Protocol is a collaboration backend that coordinates edits over encrypted content. The server sees enough math to keep everyone in sync. It never sees the words. Treat it as the part of Google Docs that ships, minus the part where the host reads your document.

Who it’s for

Teams who already trust end-to-end encryption for their messages and password vaults, and now want the same contract for the documents, notes, and shared workspaces that today still live in plaintext on someone else’s server.

Proof points

• Production server in Rust on actix-web, with PostgreSQL persistence, JWT auth, rate limiting, and Prometheus metrics shipped in fnp-server
• Multi-region deployment topology already documented under Kubernetes with Karpenter cost controls
• The three locks are independent and replaceable: content, ordering, and proof, each with its own published spec inside the platform docs

mindmap
  root((FNP))
    Private content
      host cannot read
      end to end keys
    Live ordering
      multi user merge
      no overwrites
    Verifiable edits
      every change provable
      audit on demand
    Future proof
      resists quantum attack
      keys rotate cleanly