Skip to content

Real-time · Markdown by contract

A 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 — because that is when you wrote it.

A workspace of your own in one click: no address, no password. Sign up later to keep it. How trials work

Journal · 12 March 2014filed here
Ordered the replacement sensor.

the same block, written today

Timelinewhen it was written, not where it is filed
Monday, 7 September 2 entries
17:22
Ordered the replacement sensor.
wrotefiled under 2014-03-12placed on Mar 12, 2014
Wednesday, 12 March 2014 1 entry
—
Ordered the replacement sensor.
placed herewritten Sep 7

Two dates, kept apart on purpose

Where something is filed is not when it was written.

Every note tool conflates those. Notesflow keeps them as separate fields, so declaring one can never rewrite the other — and “what did I actually do in March” stays answerable for as long as the log exists.

Axis one

When the writing happened

Derived from the append-only op log, never asserted. Move a block to another page next week and its authored date does not budge.

Axis two

The day the author chose

A block can be placed on a day you pick. It then appears under both days, each row saying which axis put it there.

And so

The timeline is just a query

Ordered by when each edit happened and entirely independent of which page anything sits on. There is no journal-file convention to keep to.

What it does

A complete knowledge base, not a demo of one idea.

Everything below is built, tested in a browser, and documented in the guide — the links go straight to the page that explains it.

The timeline, and journals

What was written on a day, by whom, across the whole workspace. Today’s journal is one click away, and appending to an old one still shows up under today.

Read more →

A block editor

Markdown input rules, a slash menu, links, tables, callouts, maths and diagrams, find and replace, folding — and Markdown on the clipboard both ways.

Read more →

Or write it as Markdown

Any page can be edited as plain Markdown, with live preview and Obsidian’s syntax for references. Still blocks underneath, so the timeline and history are unchanged.

Read more →

Templates and kits

161 built-in templates for software teams, personal life, study and the family, snippets at the caret, and 33 kits that set up a sprint board or a reading list in one go.

Read more →

History you can trust, and take back

Every version of every page, restored by appending. And when something must really go — a pasted password, a customer’s details — redact it from every version, or purge a page for good.

Read more →

Real-time, with presence

Two windows, one document, remote carets — every edit attributed to the account that made it, and “Saved” only once the server has it.

Read more →

Links, backlinks and mentions

[[page]] links with a picker, backlinks, and names written but never joined up, offered one button away from being a link.

Read more →

Block references

((block)) renders the block it points at, live — and edits in place, landing on that block’s own page and its own history. Name a block or a region, Obsidian-style.

Read more →

Search, and an inbox

Every match grouped by the page it is on, opened at the block that matched. Comments, suggestions and @mentions reach the people who watch.

Read more →

Database views

A saved query over pages, as a table or a board. Rows are pages, cells are their properties — the table holds nothing.

Read more →

Tasks where they were written

A to-do in any page is a task: due dates, priorities, repeats, My tasks, lists and a calendar drawn live, Taskflows whose steps tell the next person, and a weekly update drafted from the log.

Read more →

Comments and review

Threads anchored to the words they were made about. And proposals: a whole suggested version of a page, decided block by block by somebody who can edit it.

Read more →

An assistant that works as you

Ask about anything you can read, with the pages it came from. It writes only as you could, asks first unless told otherwise, and turns a rough draft into pages in the team’s own words.

Read more →

Suggestions, and a morning briefing

Overdue tasks, stalled steps, pages left behind, links to superseded decisions — found by looking the workspace over each morning, from facts it already holds.

Read more →

For software teams

Code fences with a file name, diffs, PROJ-123 drawn as a link to your tracker, numbered decision records, and an incident page that shows when each line was written.

Read more →

Permissions that inherit

Workspace roles plus per-page grants that apply to everything underneath. A read-only page opens with no caret.

Read more →

Publish a site

Turn a page and the pages you choose beneath it into a website — for anybody, anybody signed in, or a list. Nothing is published because of where it is filed.

Read more →

Offline, honestly dated

Write with the network cut. The work arrives dated to when it happened, not to when the wifi came back — and what this device holds can be saved to a file and brought back.

Read more →

On your phone

The same editor in the phone’s browser, opening in reading mode so a stray tap changes nothing, or in the Android app: quick capture, a widget, the share sheet, and a plain-text editor.

Read more →

Notices in your chat app

Telegram, Signal or WhatsApp told when your step is next, within your working hours — and a reply ticks the step or saves a note to today’s journal.

Read more →

Markdown and git

Import a vault, export a deterministic .md tree, mirror it to git continuously, and merge external edits back.

Read more →

Printing that behaves

Paper size, margins and typography come from the page’s own properties. The browser breaks the pages; the editor has no second opinion.

Read more →

Your company’s sign-in

Each workspace connects its own OIDC provider: domains proven by DNS, roles from the provider’s groups, members synced over SCIM, and rules such as “two-step for everyone”.

Read more →

Run it as a service

Packages that set what each workspace may use, people asking for one in the app, and invoices drafted, issued, paid and chased — for a deployment that is a platform.

Read more →

Many workspaces, one deployment

Each with its own pages, history, search, attachments and admins — kept apart by the database, not by a WHERE clause.

Read more →

How it is built

Blocks and an op log are canonical. Markdown is a projection.

Most tools store documents and reconstruct history by diffing them. Notesflow stores the history and projects the documents — which is why the timeline costs a query rather than a crawl, and why exporting cannot lose what the editor knows.

  • Every edit is an op — appended, attributed and timestamped. Nothing is overwritten, so page history restores by appending rather than erasing.
  • Every block type declares its Markdown fidelity tier, and the tier table is generated from the code so it cannot drift from what the code actually does.
  • Exported links are relative .md paths built from slugs. No identifier appears in any link target — the single largest source of “my links broke” in comparable tools.
  • One projection, three consumers. Export, clipboard and import all go through the same serialiser, and CI fails the build if a second one appears.
field-notes.md — what export writes
---
title: Field notes
tags: [sensors, maintenance]
---

## Bridge 4

- Ordered the replacement sensor.
<!-- notesflow:paragraph {"date":"2014-03-12"} -->

See [Sensor inventory](../inventory/sensor-inventory.md).

One click to the first page

Write something today. Find out in a year when you wrote it.

Try it without an account, then follow the quick start’s two-minute demonstration of the point.

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