Skip to content

FAQ ​

Where does it run? ​

On a server it is deployed to — and it runs from a fresh clone with no database server, no container and no account; see quick start. A deployment can be private to one team, or a platform the public signs up to, with passwords, a workspace of their own, and packages and invoices for what they pay for. See authentication.

What licence is it under? ​

A proprietary one: all rights reserved, and using, copying or changing it needs a written agreement with the copyright holder. The third-party components it uses keep their own licences. See LICENSE in the repository.

How is this different from Obsidian, Logseq or Notion? ​

The difference is what is canonical.

  • Obsidian and Logseq (files) — Markdown files are the truth. History is whatever git or the tool's own snapshots recovered, and when something was written is inferred from the file it landed in. Appending to January's journal file today dates that writing to January.
  • Notion (blocks) — blocks are the truth, and export is a snapshot bolted on afterwards. Database rows exist only inside their database, which is why exporting one gives you a CSV.
  • Notesflow — blocks and an append-only op log are the truth; Markdown is a projection with a declared fidelity tier per block type, and rows are ordinary pages.

The practical consequences: the timeline is a query rather than a crawl, exported links contain no identifiers, and a database view exports as real pages with real frontmatter.

Will it lock my notes in? ​

The answer this project offers is a mechanism rather than a promise: pnpm export:git writes the whole workspace as .md files with real frontmatter and relative links, deterministically, and pnpm mirror:git keeps that repository in step continuously.

What an export does not carry is the op log — so it has your documents, and not when each line was written.

Can I edit the files directly? ​

You can edit them and merge them back, which is a three-way merge against what the export last wrote. Blocks keep their identity and their authored dates.

What you cannot do is edit both sides at once and expect them to converge. That is stated up front rather than discovered: interop is reconcile-on-demand, not live.

Do I need Postgres? ​

No. PGlite — Postgres compiled to WebAssembly, in-process — is the default and needs nothing installed. You want a server once you run more than one API process, or want backups you can take without stopping the app. Nothing else changes.

Does it work offline? ​

Yes, for pages you have opened before, and the writing arrives dated to when it happened rather than to when the network came back. What does not work offline — page creation, renaming, comments, search, sharing — is listed plainly in working offline.

Can two people edit the same page? ​

Yes, character by character, with presence and remote carets. Every edit is attributed to the account that made it. See collaboration.

On a page written as Markdown, each block is written by one person at a time, and two people can still write the same page at once — in different blocks.

Can I just write Markdown? ​

Yes. Any page can be written as Markdown — the text itself, with live preview, Obsidian's reference syntax, and an option to keep your formatting byte for byte. It is still blocks underneath, so the timeline, history and everything else work as on any page.

How do I know my writing is saved? ​

The indicator beside the connection pill says so — and it says Saved only once the server has written your change into the log, never because it was merely sent. See collaboration.

Can a company use its own sign-in? ​

Yes, per workspace: an OpenID Connect provider such as Okta, Entra ID or Google Workspace, with domains proven by DNS, roles and groups from the provider, members kept in step over SCIM, and rules such as "everyone uses two-step sign-in" or "no passwords". SAML is not supported. See single sign-on.

Can I keep several teams on one deployment? ​

Yes. Each workspace has its own pages, history, search, attachments and admins, and the boundary is enforced by the database's row-level security rather than by application code remembering to filter. See workspaces.

Why can't I set a journal date on an ordinary page? ​

The sidebar only offers today's journal; a journal for another day is created over the API (POST /api/journals). See journals.

This is a gap in the UI rather than in the model — and note that the feature people usually want here is the other axis: placing a block on a day, which needs no journal page at all.

How do I import my existing vault? ​

Import at the foot of the sidebar, or Import Markdown or Logseq… in the command palette: drop a folder — an Obsidian vault, a Logseq graph or any folder of Markdown — read the preview, and import. pnpm import:md <dir> does the same from the command line. For a single page, paste the Markdown. See importing.

Why is there no pagination in the editor? ​

Because a paginating editor has to agree with the print output, and when the two disagree you get a document that looks right on screen and breaks wrongly on paper. Notesflow describes the sheet and lets the browser's own layout engine do the breaking. See printing.

Why can't I make a bolded code span? ​

CommonMark genuinely cannot express one adjacent to a word — code spans bind tighter than emphasis delimiters, so the markup reparses as literal asterisks. Bold code is a marginal typographic nicety; silently corrupting a document on export is not. Code can be a link: [`store.ts`](…) is ordinary CommonMark.

Something looks wrong — where is the honest list of limits? ​

The guide states each feature's known limits up front, usually under Not built at the foot of its page — written when the feature was built rather than when somebody complained.

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