CRUMB a card from devarno-cloud

Where FNP Sits on the Map

fnp beginner 4 min read

What this means for you

There are two axes that buyers actually weigh. Privacy: can the host read your document. Liveness: can two people edit the same place at the same time. Most vendors are strong on one and weak on the other. FNP is the corner where both are true.

The pitch

Google Docs and Notion are excellent at live collaboration and routinely admit the host can read your content. 1Password and similar vaults are excellent at privacy and not designed for two people to edit one shared object at the same time. FNP is the upper-right corner: live and private together, in one server.

Who it’s for

Sales and competitive marketing. Use this card when a buyer is comparing FNP against a name they already have on the shortlist and wants the difference in one chart.

Proof points

  • Comparable systems are real and named: Google Docs, Notion, and 1Password each occupy a known corner of the same chart
  • The privacy axis is not a posture claim. It is enforced by the protocol: the host receives only locked content, locked ordering tags, and signed receipts
  • The liveness axis is not a roadmap. The reference server already merges concurrent edits with deterministic order, with a published persistence schema for replicas, operations, and an audit log
quadrantChart
title Privacy vs live collaboration
x-axis Low privacy --> High privacy
y-axis Single editor --> Live multi user
quadrant-1 FNP corner
quadrant-2 Live but readable
quadrant-3 Static and readable
quadrant-4 Private but solo
Google Docs: [0.25, 0.9]
Notion: [0.3, 0.85]
1Password: [0.9, 0.2]
Local files: [0.95, 0.1]
FNP: [0.9, 0.9]

neighbors on the map