Logseq
Logseq is a free, open-source, privacy-first note-taking and knowledge management application supporting Markdown and Org-mode syntax. Founded in 2020 by Tienson Qin, the app emphasizes local-first data storage with bi-directional linking, block-level referencing, and an outliner-based interface. Available on Windows, macOS, Linux, Android, and iOS.
Score generated by AI agents based on publicly cited evidence and reviewed by the project maintainer. Not independently validated.
Score History
Timeline events are AI-curated from public reporting. Score trajectory is derived from documented events.
Tienson Qin builds Logseq as an open-source side project, a privacy-first outliner storing notes as local Markdown files. The app has near-zero enshittification concerns: no monetization, no proprietary formats, fully transparent AGPL code. Minor scores reflect inherent early-stage roughness (buggy beta software) and the competitive PKM landscape it enters alongside Roam Research and Obsidian.
Logseq raises $4.1M from prominent tech leaders, incorporates as Logseq Inc., and expands rapidly with iOS and Android apps, PDF annotation, flashcards, and a plugin ecosystem reaching 300+ extensions. Open Collective funding provides Sync beta access to backers. The VC raise introduces minimal shareholder extraction pressure, but the team's ambitions to build real-time collaboration and a 'World Knowledge Graph' set the stage for the complex database rewrite to come.
The database architecture rewrite, quietly started in late 2022, consumes all development resources. Sync reliability issues cause persistent data loss reports. On-disk encryption is deprecated and a plaintext cache leak is discovered, both undermining the privacy-first positioning. A CLA request sparks community backlash over potential AGPL relicensing. Feature development effectively halts for the existing Markdown version as the team goes quiet on progress for nearly two years.
A 13-month gap between stable releases (April 2024 to May 2025) triggers 'Is Logseq dead?' discussions and visible user migration to Obsidian and Affine. The Markdown version enters maintenance mode with no new features planned. Sync issues and data loss reports continue unresolved. The DB version makes progress with RTC alpha and E2E encryption, but remains far from general availability. Community trust erodes despite the project's fundamentally healthy open-source architecture.
Alternatives
The most popular local-first Markdown note-taking app with a thriving plugin ecosystem, active development, and reliable sync ($4/month). Directly reads Logseq's Markdown files with minimal adjustment. Easy switch — your notes are already in compatible format. Not open-source, but local-first.
All-in-one workspace with databases, wikis, and project management. Cloud-based rather than local-first, so a significant privacy tradeoff. Much more actively developed than Logseq currently. Moderate switch — requires importing notes and rebuilding structure. Free for personal use.
Open-source (AGPL), privacy-focused note-taking app with E2E encrypted sync. Supports Markdown with notebooks rather than an outliner structure. Self-hostable sync or paid Joplin Cloud ($2.99/month). Less feature-rich than Logseq but more actively maintained and stable.
Dimensional Breakdown
Summaries below were written by AI agents based on the cited evidence. They are editorial interpretations, not independent research findings.
Dimension History
Timeline (32 events)
Tienson Qin begins building Logseq as side project
Software engineer Tienson Qin, frustrated that his Org-mode notes tool didn't work on tablets, starts building Logseq as a privacy-first, open-source outliner with bi-directional linking. The project is written in Clojure/ClojureScript and stores data as local Markdown or Org-mode files.
First public GitHub release (v0.0.1)
Logseq publishes its first public release on GitHub as version 0.0.1, making the open-source knowledge management tool available to early adopters. Initially a web-based app, it supports Markdown and Org-mode syntax with bi-directional linking inspired by Roam Research.
Logseq reaches Hacker News front page
Logseq is featured on the Hacker News front page, generating significant developer interest as a privacy-first, open-source alternative to Roam Research. The discussion highlights features like backlinks, graph views, and block embeds alongside the AGPL-3.0 license.
Logseq launches on Product Hunt
Logseq launches on Product Hunt as a 'joyful, open-source outliner' working on local plain-text Markdown and Org-mode files. The launch brings wider visibility to the project beyond the developer community, attracting PKM enthusiasts seeking open-source alternatives.
PDF annotation and spaced repetition flashcards added
Logseq adds PDF annotation support allowing users to highlight text within PDFs and create block references from annotations, along with a spaced repetition flashcard system. These features significantly expand Logseq's appeal to researchers and students, making it competitive with specialized tools.
Android mobile app released
Logseq releases its Android mobile app, extending the platform from desktop-only to mobile. The app allows users to access their local knowledge graphs on Android devices, though sync between devices remains a significant challenge using third-party solutions like iCloud or Syncthing.
Community begins asking about Logseq's business model
A long-running forum discussion begins about Logseq's business model, with the team explaining they plan to keep the core app free while charging for advanced features, storage, and collaboration. They acknowledge Logseq may not make money for the first 2-3 years, relying on Open Collective donations and planned premium features.
iOS app launches on Apple App Store
After months of beta testing through TestFlight, Logseq goes live on the iOS App Store, making the knowledge management tool available across all major desktop and mobile platforms. The launch completes Logseq's cross-platform story, though multi-device sync remains dependent on third-party services.
Logseq raises $4.1M seed round from prominent tech leaders
Logseq announces a $4.1M seed round led by Stripe CEO Patrick Collison, Shopify founder Tobias Lutke, and former GitHub CEO Nat Friedman, with participation from Craft Ventures, Matrix Partners China, Day One Ventures, and A16Z GP Sriram Krishnan. TechCrunch and VentureBeat report the tool is used at Google Brain, Meta, Tesla, MIT, Stanford, and Harvard.
Users report repeated data loss, trust in Logseq erodes
A prominent forum thread titled 'Data loss happened twice, I can't trust Logseq anymore' accumulates dozens of replies from users experiencing data loss across platforms. Reports describe notes disappearing, sync conflicts overwriting content, and the app failing to write edits to local files. The thread remains active for over two years.
Logseq Sync beta opens to Open Collective backers
Logseq begins giving active Open Collective contributors ($5-$15/month) early access to the Logseq Sync beta feature, which provides end-to-end encrypted sync between devices. Initially available only to Sponsors, access expands to Backers tier in late September 2022. This represents the first paid service Logseq offers.
On-disk encryption feature deprecated in v0.8.10
Logseq removes the experimental on-disk encryption feature from the codebase after v0.8.10, citing maintenance burden and conflicts with Logseq Sync. Users who relied on the feature discover their notes are readable in plaintext at ~/.logseq/graphs, contradicting Logseq's privacy-first positioning. The team suggests third-party encryption tools like VeraCrypt as alternatives.
Security issue: notes cached in plaintext outside graph directory
Users discover that Logseq stores a plaintext transit file of all graph content at ~/.logseq/graphs, outside the user's chosen notes directory. This means even users who encrypt their notes folder have unencrypted copies elsewhere on disk. The issue contradicts Logseq's 'you control your data' philosophy and remains unresolved.
Whiteboards feature announced for early backers
Logseq announces Whiteboards, integrating the Tldraw drawing library for spatial note-taking. The feature is initially rolled out to financial backers as early access, with plans to make it publicly available. Whiteboards aim to make visual canvases first-class citizens alongside pages and blocks.
Version 0.9.0 releases Whiteboards and Query Builder to all users
Logseq v0.9.0 makes Whiteboards and a new simple Query Builder available to all users on desktop and mobile. The Whiteboards feature works across platforms and on published graphs. This represents the high-water mark of Logseq's feature velocity before the database rewrite consumes development resources.
Community calls for clearer development roadmap
Forum posts begin requesting more transparency about Logseq's development direction, with users noting the outdated Trello roadmap has never been respected and new features are not listed on it. The team develops privately without regular public communication about priorities, a pattern that intensifies as the database rewrite consumes resources.
Contributor License Agreement introduced for potential relicensing
Logseq sends an email to contributors requesting they sign a Contributor License Agreement (CLA), explaining the AGPL license is 'so viral' that some companies like Google ban it. The community pushes back, arguing AGPL protects open-source values and that a CLA could enable future proprietary relicensing. The requirement creates friction for new contributors.
Community AI plugins emerge using GPT-3 and GPT-4
Community-developed plugins integrate OpenAI's GPT-3 and GPT-4 APIs into Logseq, enabling AI-assisted note-taking, text generation, and audio transcription via Whisper. These are third-party plugins requiring users to provide their own API keys, not official Logseq features. Privacy concerns surface about sending note content to external APIs.
Logseq 0.9.14 introduces Smart Merge for Sync
Version 0.9.14 adds an experimental Smart Merge feature allowing users to edit the same page on multiple devices simultaneously without data loss. The feature requires manual enabling and re-indexing on each device. While still experimental, it addresses the core multi-device editing problem that has plagued Logseq since launch.
Privacy violation found in export/publish feature
A GitHub issue reports that Logseq's export/publish feature for 'public pages' inadvertently includes private information about the graph that should never be public. For a privacy-focused app, the bug is described as 'absolutely devastating' since many users may have already leaked private data without knowing.
Unrecoverable data loss from edits not written to files
Users report a critical bug where edits made in Logseq are not written to the underlying markdown files, with content existing only in Logseq's internal cache. When the cache is cleared or corrupted, edits are permanently lost. The issue affects users across platforms and undermines the local-first promise that notes are always on-disk.
Version 0.10.9 released — last stable update for over a year
Logseq releases v0.10.9 with Linux ARM64 support and bug fixes. This becomes the last stable release for over 13 months, as all development resources shift to the database version rewrite. The Android APK is also frozen at this version, with no beta releases for mobile users during the gap.
First official communication about database rewrite after two years
Tienson Qin publishes the first official post explaining why the database version is being developed and its progress, apologizing for spending 'almost all the time on developing it without communicating about the progress.' The post comes nearly two years after planning began in late 2022, during which the community received minimal updates.
Community asks 'Why isn't Logseq updating?' after release gap
Forum threads questioning why Logseq hasn't released updates in months begin appearing, with the two-month gap at the time eventually extending to over a year. Users note existing bugs remain unfixed while all development focuses on the unreleased database version.
'Is Logseq dead?' community discussion surfaces
A widely-viewed forum thread titled 'Is Logseq dead?' aggregates community frustration about the prolonged development silence. Some users describe the original open-source single-user app as effectively dead, with all future development focused on the database version, collaboration, and monetization. Others note weekly DB development updates as evidence of continued work.
Users begin migrating to Obsidian and Affine amid development stagnation
Blog posts and forum discussions document users migrating from Logseq to Obsidian or Affine, citing data loss concerns, development stagnation, and the uncertain future of the Markdown version. Community migration tools appear on GitHub to automate the Logseq-to-Obsidian conversion. The pain is described as acute for users who invested heavily in Logseq workflows.
'2024: A Year of Logseq' review documents development stagnation
A detailed retrospective by a long-time user documents 2024 as a year of near-total development stagnation for Logseq's stable release, with the last update in April 2024. The review catalogs persistent sync issues, mobile bugs, and growing competition from more actively maintained tools. Despite this, the author notes the core note-taking experience remains strong.
Logseq migration journey analysis highlights challenges and delays
A comprehensive analysis documents the database migration journey, noting the DB rewrite began in late 2022 but the first official communication came only in April 2024. The piece highlights how the migration created uncertainty, paused feature development, and led users to explore alternatives, while acknowledging the technical necessity of the architectural change.
Version 0.10.10 breaks year-long release freeze
Logseq releases v0.10.10 after a 13-month gap since v0.10.9, followed quickly by v0.10.11 (May 19) and v0.10.12 (May 26) to fix regressions. The Markdown version is placed in 'maintenance mode' — receiving only security patches and compatibility fixes, with no new features planned. This signals the team's full commitment to the database version.
DB version mobile app and RTC alpha opens for testing
Logseq announces that both the new DB-based mobile app (iOS) and Real-Time Collaboration (RTC) sync are ready for alpha testing, beginning with sponsors, backers, and contributors. The Android DB mobile app remains in development. This represents the first tangible output of the multi-year database rewrite available to early users.
End-to-end encryption delivered for real-time collaboration
Logseq delivers E2EE for its Real-Time Collaboration feature, along with a Page Publishing Platform using Cloudflare Workers. These are described as 'transformative initiatives' representing progress on the database version. The DB version also receives a major Android experience overhaul.
Logseq publishes official product roadmap
After years of community requests for development transparency, Logseq publishes an official product roadmap on the discussion forum, outlining the DB version as the primary development focus with the Markdown version in maintenance mode. The roadmap addresses long-standing community criticism about opaque decision-making.