Tagged 2.0.1 on GitHub, the first public beta of the database version replaces flat markdown files with a canonical SQLite store — adding structured properties, typed queries, real-time sync, and page publishing. Logseq is also splitting into two products: file-based "Logseq OG" and this database-backed Logseq.
2026-07-13 · by Moe Ameen
Logseq, the privacy-first, open-source outliner used as a "second brain" for networked note-taking, released the first public beta of its long-in-development database version on July 13, 2026 — "Logseq 2.0 Beta (DB version)," tagged 2.0.1 on GitHub. The headline change is architectural: instead of storing every graph as a folder of plain markdown files, the DB version keeps notes in a local SQLite database that is now the canonical source of truth. You can still export to markdown, but you no longer edit the underlying files by hand the way file-graph users do today.
Alongside the beta, the team confirmed Logseq is splitting into two products. The file-based, markdown-first app becomes "Logseq OG," moving to its own repository for users who want their notes to stay as editable local files; it keeps getting security and Electron maintenance but no new features. The database version — the one that gets the roadmap from here — inherits the "Logseq" name. Nothing changes overnight for existing users: file graphs keep working, and you migrate to the DB version whenever you're ready via an importer.
The database model unlocks features that flat files made hard. Pages and blocks are unified into a single concept called "nodes" that behave alike; properties are now typed (values like Text, Number, Date, Checkbox, URL, and Node), with defaults, choices, and multiple values; and tags act like classes that can inherit properties from parent tags, giving notes a lightweight schema. Queries become first-class tagged nodes with dashboard-style views. The release also adds a new sync approach called RTC (real-time collaboration) for syncing a graph across devices or editing with others — a paid, invite-only feature at launch — plus Logseq Publish for sharing individual pages publicly (optionally password-protected), and a new native mobile app starting on iOS.
Logseq is explicit that this is an early beta: the DB version can lose data, and regular backups are recommended, with the new mobile app and RTC still in alpha. Feature names, property types, and the sync/publishing details are evolving fast, so confirm the current state against Logseq's own docs and releases; you can try the latest web build at test.logseq.com before committing a real graph.
The quiet truth about any note-taking tool, Logseq very much included, is that most of what you capture never reaches an audience. The DB version makes that backlog more usable — you can query your graph for every node tagged "draft" or "content idea" and pull a clean topic cluster in seconds — but Logseq's own publishing stops at a read-only page on logseq.io. That's exactly the handoff Kompozy is built for. Export or copy the outline, research notes, or daily-notes thread you just assembled in Logseq, drop it into Kompozy as a source, and it becomes finished content: a Blog Article and an Email Newsletter drafted from the notes, a brand-exact Carousel that walks the argument point by point, Quote Graphics pulled from the sharpest lines, and native Text Posts for each platform — all held to one voice by your Persona Brief so a week of output reads as your brand, not raw note dumps.
That's the same-week move on this news, too. "Logseq just moved to a database" is a query your note-taking and productivity audience is searching right now, so turn your own take into a package: a captioned Clipped Short or Persona Short explaining the file-vs-DB tradeoff, a carousel comparing Logseq OG and the DB version, a blog explainer, and platform-native posts — then let Autopilot and the per-post review pipeline schedule and publish the whole set across nine social platforms plus blog and email from one queue. Keep Logseq as the brain where ideas live; use Kompozy as the engine that ships them.
It is the first public beta of Logseq's database version, released July 13, 2026 and tagged 2.0.1 on GitHub. Instead of storing notes as plain markdown files, it keeps them in a canonical local SQLite database, adding typed properties, dashboard queries, real-time sync (RTC), page publishing, and a new mobile app. Logseq calls it an early beta and recommends backing up your graph.
Logseq OG is the file-based, markdown-first app: your notes stay as editable local files, and it keeps getting security and maintenance updates but no new features. The database version stores notes in SQLite (the database is canonical, though you can export markdown), you cannot hand-edit the underlying files, and it gets all future feature work — nodes, typed properties, sync, and publishing.
Treat it as beta software. Logseq says the DB version can lose data and recommends automated or regular backups, and the new mobile app and RTC sync are still in alpha. File graphs keep working on Logseq OG, so many users test the DB version on a copy of their graph before migrating anything important.
No. Logseq Publish shares a page to a read-only site on logseq.io, optionally password-protected; it does not create clips, carousels, or posts, and it publishes to no social platform. To turn Logseq notes into finished, on-brand content across platforms, creators pair it with a content engine like Kompozy, which generates the posts and publishes across nine social platforms plus blog and email.