Flowplan vs Inkling

Editor take

Choose Flowplan for phone and desktop apps, and for one container on SQLite. Choose Inkling for Obsidian-style wikilinks and graph, and for JSON Canvas files.

Editor

Where they differ

Only what is true of one of them and not the other. Each app's weak spots are the other app's strengths.

Flowplan

Where Flowplan is stronger

  • Phone and desktop appsiPhone and iPad from the App Store, an Android APK, and macOS, Windows and Linux builds; Inkling is a web app only.1
  • One container on SQLiteEverything sits in one data directory with SQLite, and Postgres is optional for more people; Inkling needs Postgres and a backup sidecar.2
  • Imports from many other toolsNotion, AppFlowy, AFFiNE, Obsidian, Confluence, Evernote, Google Docs and Word, plus OneNote through a Word export; Inkling imports Notion exports and Markdown.3

Inkling

Where Inkling is stronger

  • Obsidian-style wikilinks and graphLinks between pages build backlinks, and a workspace graph and a local graph show how pages connect.4
  • JSON Canvas, the Obsidian formatWhiteboards are saved as JSON Canvas, the format Obsidian uses, so a canvas moves between the two without conversion.5

Flowplan vs Inkling: specs side by side

Every spec for both apps in one table, so you can check install options, hardware and client apps before you pick one.

Spec
PriceFreeFree
LicenceAGPL-3.0MIT
Web UIYesYes
iOSYes–
AndroidYes–
WindowsYes–
macOSYes–
LinuxYes–
DockerYesYes
Tech stackNodeNode
Docker Containers1 (app only)3 (app + Postgres, backup)
DatabaseSQLitePostgres
Architecturex86 + ARMx86 + ARM

Common questions

Sources: Flowplan docs and Inkling docs.

Updated