Skip to content

What Notesflow is ​

Notesflow is a team knowledge base that knows when things were actually written.

Add a note today to a journal dated three months ago. Every other tool files it under January. Notesflow files it under January and shows it under today in the timeline — because that is when you wrote it. Move the block to another page next week and it keeps both facts.

That separation — where content is filed versus when it was authored — is the whole point, and everything else in the design is arranged so it cannot be compromised.

The shape of it ​

Web-first, real-time collaborative, block-based, and Markdown-compatible by contract rather than by accident.

  • Blocks and an append-only op log are canonical. Every edit is appended, attributed and timestamped; nothing is overwritten.
  • Markdown is a projection of those blocks, not the storage format. Every block type declares what it becomes in Markdown and at which fidelity tier.
  • Git is an export target, not the database. You can export, mirror continuously, and merge external edits back — but Notesflow does not need a repository to work.

The timeline is an ordinary query over the op log, ordered by when each edit happened and entirely independent of which page anything sits on. There is no journal-file convention to keep to and no diffing of documents to reconstruct a history that was never recorded.

What it is not ​

Stated up front, because knowing the edges is worth more than a longer feature list:

  • Not a live two-way bridge to your filesystem. Editing the same content in an external editor and in Notesflow at the same time is reconcile-on-demand, not live. See what is promised.
  • Not tied to one way of running it. It runs on a server — for one team, or as a platform people sign up to and pay for through packages.
  • Not a wiki with version history bolted on. The history is the storage; the documents are the derived thing.

Where to go next ​

If you want toRead
Start writing in a minuteQuick start
Look around before signing upTrying it without an account
Understand the model before you commit to itCore concepts
Know what every pane on screen doesA tour of the window
See the argument in actionThe timeline
Write in plain Markdown insteadWriting a page as Markdown
Keep track of what needs doingTasks and Taskflows
Start from something already writtenTemplates
Write on the moveOn your phone
Put it in front of a teamAdministration
Keep your notes in gitMarkdown and git

Blocks and the op log are canonical. Markdown is a projection. Git is a target.