FILE-G · DOSSIER 05 · 2026.05.05 · KNOVYA EDITORIAL Field Notes Vol. III · The Outliner Question
The Logseq Alternative

Logseq alternatives,
honestly compared.

Logseq was right about a lot of things. The outline as a unit of thought, the daily journal as the front door, the local Markdown file you actually own. Then it spent two years rebuilding itself on a database engine, and the people who loved it most started asking: where is my mobile, where is my sync. Here's the read on the eight tools they consider next — and the ninth path we built for the era after the local-first vault.

Filed by Knovya Editorial, May 5, 2026. Cross-checked against the Logseq blog, the Open Collective ledger, the April 2026 Logseq DB announcement, the GNU AGPL-3.0 license file, and recurring complaints across r/logseq, r/PKMS, and the Logseq community forum itself.

Skip to the lineup Why we built Knovya
The Diagnosis

Four reasons people search for a Logseq alternative in 2026.

Logseq has not stopped being good at what it is good at. It has stopped being the safest place to keep the only copy of your thinking. The four pain points below are what surfaces most often when committed users describe why they started looking — drawn from the Logseq forum itself, third-party reviews, and the long arc of the DB-version rebuild.

  1. Recurring complaint · Mobile + sync

    The local-first promise breaks when the second device shows up.

    Logseq is built around a folder of plain Markdown files you control, which is exactly right until you want the same graph on a phone. The official Logseq Sync runs through Open Collective at a $5 per month backer tier and remains in beta. On the Logseq forum itself, multi-year users describe sync that disconnects, mobile sessions that crash on login, and a paid layer that has not yet earned the word "stable."

    → The point of local-first is freedom. Sync that fights you is the opposite of freedom.

  2. Architectural shift · DB version, Apr 26, 2026

    The good news is the rebuild. The hard news is everything is still beta.

    The April 26, 2026 update introduced the long-promised database engine, a new sync architecture, and a redesigned mobile app — material progress after a quiet 2024 and 2025. The Logseq DB graph itself is still in beta, the new mobile app and the real-time-collaboration layer are in alpha, both invite-only. The team's own guidance is to keep automated backups and to use a non-critical test graph during the transition.

    → A rebuild on the right foundation is still a rebuild you live through.

  3. Cross-platform refrain · The outliner tax

    The bullet-tree learns you faster than you learn it.

    Outliner thinking is a real cognitive style — and Logseq is the most committed expression of it. For people whose ideas arrive in nested fragments, nothing else feels right. For people whose ideas arrive in paragraphs, the outliner becomes structural overhead: every thought forced into a bullet, every paragraph chopped into blocks. The Logseq community itself acknowledges this is a fit problem, not a flaw.

    → The model that helped you think can also start thinking for you.

  4. Architectural gap · AI + collaboration era

    A graph for one person, in an era of graphs for many.

    Logseq is, by design, single-player. Real-time collaboration is finally arriving through the DB version's RTC layer, but it is invite-only and paid. Native AI sits outside the core: there is no built-in equivalent of weekly synthesis, no MCP server for Claude or Cursor, no end-to-end encryption tier where the cloud never sees plaintext. Plugins close some of these gaps. None of them close the gap of being the architecture.

    → The 2026 question is not which outliner is purest. It is which one was built for the way work happens now.

The Lineup

Nine alternatives, each its own bet.

No tool below is "better than Notion" in the abstract. Each is a different bet about what a workspace should do — local versus cloud, AI-native versus AI-bolted, encrypted versus open, structured versus free-form. Read across, then read down.

  1. 01 · The third path

    Knovya AI-native

    The cloud-synced, MCP-native, end-to-end encrypted notes app for the era after the local-first vault.

    What it bets on

    Outliner-friendly thinking without the outliner tax. Bidirectional [[backlinks]], a knowledge graph, and a daily-journal mode sit alongside NoteRank personal ranking, hybrid search over Postgres FTS plus pgvector, and an Experience Envelope that surfaces past precedents by outcome. 34 MCP tools mean Claude, ChatGPT, Cursor, Gemini, Copilot, Windsurf and Goose can read and write your knowledge base directly.

    Pricing reality

    Free forever — 50 notes, 50 AI credits, 50 MCP calls per month. Pro $15. Team $25. Note-level AES-256-GCM encryption on Pro and Team — encrypted notes are never embedded on the server. Web, macOS, Windows, iOS, and Android with day-one parity.

    The full Knovya story
  2. 02 · Local-first markdown

    Obsidian

    The most common landing pad after Logseq — same files, page-first model.

    What shone

    Plain Markdown vault you own. Backlinks, graph view, and a plugin ecosystem (Outliner, Dataview, Templater) that respects power users. Mobile is genuinely native, not a wrapper. Free for personal use.

    Where it breaks

    Page-first, not block-first — outlining is a plugin, not the architecture. Sync is a paid add-on (~$4/mo). AI is bring-your-own. Sharing requires Publish, GitHub, or a workaround.

    Obsidian dossier
  3. 03 · The block-reference origin

    Roam Research

    The graph that started the genre Logseq carries forward.

    What shone

    Bidirectional links and block references as a unit of thought. Daily-notes-first interface. Cloud-hosted from day one — no sync configuration. Roam invented the workflow Logseq democratized.

    Where it breaks

    $15 per month with no free tier. Development pace cooled after 2022. Mobile remains a thin shell. Closed-source — your graph lives on Roam's cloud, in Roam's format.

    Roam dossier
  4. 04 · Outliner with supertags

    Tana

    The modern outliner that crossed the bullet with the database.

    What shone

    Supertags turn a bullet into a typed object — a meeting, a person, a task — with fields and views. Cloud-native. Active development. AI features baked into the core, not a plugin.

    Where it breaks

    Cloud-only — no local-first option. Pricing aimed at professionals (paid tiers). Closed-source. The supertag system is powerful but adds setup overhead before any thinking happens.

    Tana dossier
  5. 05 · Outliner meets flashcards

    RemNote

    Bullet-tree thinking wired into spaced repetition.

    What shone

    Every bullet can become a flashcard. Built-in spaced repetition algorithm. PDF annotation links highlights to source pages. The natural Logseq alternative for students and active-recall learners.

    Where it breaks

    Cloud-first, with a paywall on advanced features. Closed-source. The all-in-one PKM aspect feels grafted onto a study tool, not the other way around.

    RemNote dossier
  6. 06 · Open-source kindred

    AppFlowy

    If the AGPL part of Logseq is what you loved, here is the cousin.

    What shone

    GPL-3.0, with a Docker Compose self-host path that is first-class. Pages, nested blocks, slash commands, Grid + Board + Calendar databases. Built in Flutter and Rust for cross-platform parity.

    Where it breaks

    Page-first like Notion, not outliner-first like Logseq. AI is bring-your-own. The mobile experience is improving but still trails desktop.

    AppFlowy dossier
  7. 07 · Privacy-first, encrypted

    Anytype

    Local-first, end-to-end encrypted, peer-to-peer sync.

    What shone

    E2E encryption by default. Object-based data model with typed relations. Free local use; paid plans add cloud sync. AnySync protocol open under MIT — closer to Logseq's privacy ethic than to Notion's cloud.

    Where it breaks

    No real AI features beyond search. No MCP. P2P sync expects a device online; mobile catches up only in range. Object model is closer to a database than a notebook.

    Anytype dossier
  8. 08 · The original outliner

    Workflowy

    One zoomable bulleted list — the lineage Logseq built on.

    What shone

    Pure outliner DNA — every bullet is its own page, every page is just a bullet. Mirrors and live backlinks added in recent years. Fast capture, low overhead, no theme to choose. Cross-platform sync that just works.

    Where it breaks

    No graph view. No PDF annotation. No flashcards. Free tier limits the daily-bullet count. The tool ends where Logseq's plugin marketplace begins.

    Workflowy dossier
  9. 09 · Cloud all-in-one

    Notion

    The opposite bet — pages, databases, and a workspace built for teams.

    What shone

    Real-time collaboration that works. Database views — Table, Board, Gallery, Calendar — out of the box. Notion 3.0 added AI Agents in September 2025. The tool teams default to.

    Where it breaks

    Pages, not blocks — outlining is a side feature, not the model. Cloud-only. No end-to-end encryption. Full AI now lives in the $20/seat Business tier after the May 2025 restructure.

    Notion dossier
Side-by-side

The matrix, without the marketing.

Each cell below is a question of architecture, not preference. Yes means the capability is first-party and core. ~ means partial, paid add-on, alpha/beta, or workaround. No means absent. Read across.

Capability Knovya Logseq Obsidian Roam Tana RemNote AppFlowy Anytype Workflowy Notion
Outliner-first thinking ○ Hybrid ● Core ○ Plugin ● Core ● Core ● Core — Page-first — Object-first ● Pure — Page-first
Block references & backlinks ● [[wiki]] ● Yes ● Yes ● Yes ● Yes ● Yes ○ Pages ○ Relations ● Mirrors ○ Page links
AI-native, not bolted on ● Core — Plugin only — Plugin — No ● Yes ○ Add-on ○ BYO model — No — No ○ Bolted (3.0)
MCP support (read & write) ● 34 tools — No — No — No — No — No — No — No — No ○ First-party
End-to-end encryption ● AES-256-GCM ○ Sync only, beta ○ Local files — Cloud — Cloud — Cloud ○ Self-host ● Default — Cloud — Transport only
Reliable cloud sync ● Day-one ○ Beta, paid ○ $4/mo add-on ● Cloud-only ● Cloud-native ● Cloud-native ○ Self-host ○ P2P + node ● Cloud-native ● Default
Native mobile parity ● iOS + Android ○ Reduced; new app alpha ● Native ○ Thin shell ○ iOS-only ● iOS + Android ○ Catching up ● Yes ● Yes ○ Web wrapper
Open source — No ● AGPL-3.0 — Source-avail. — Closed — Closed — Closed ● GPL-3.0 ● AnySync MIT — Closed — Closed
Self-hostable — Cloud ● Local + RTC ● Local files — No — No — No ● Docker ● Backup node — No — No
Free tier (genuinely usable) ● 50/50/50 ● Fully free ● Personal — No free ○ Limited ○ Limited ● Fully free ● Local + 1 GB ○ 250 bullets/day ● Generous
Real-time team collab ● Team plan ○ RTC alpha — Workaround ● Multiplayer ● Yes ○ Limited ○ Catching up ○ P2P shared ● Yes ● Yes
Personal entry pricing $15/mo Pro Free / $5 sync Free + $4 sync $15/mo only ~$10/mo Pro ~$8/mo Pro Free / $0 Free / $5 Free / $5 $10 Plus, $20 AI
Migration path from Logseq ● .md + EDN — ● Native .md ○ Manual ○ Markdown ○ Markdown ○ Markdown ○ Markdown ○ Manual ○ Markdown

Logseq DB version (April 26, 2026) introduced a new sync architecture and a redesigned mobile app, both currently in alpha and invite-only. Logseq Sync runs through Open Collective at a $5 per month backer tier and remains in beta. Existing classic-version users continue on the stable Markdown-graph path.

Pick by Question

The honest framing: what cracked first?

The wrong question is "what is the best Logseq alternative." The right one is "which Logseq promise stopped landing in my workflow." Three honest paths, each pointing at a different tool.

Path A · The AI-native outliner

You want bullets and backlinks plus AI that knows your graph.

You loved the daily-journal flow and the [[wiki]] links. What broke was the rest: a sync layer that disconnects on your phone, no MCP for Claude or Cursor, no native synthesis of last week into this week. You want outliner thinking with AI sitting inside the graph, not a plugin you wire yourself, and you want it to open on every device the same way.

Recommendation Knovya
Path B · The pure markdown vault

You want to stay local-first, just with mobile that works.

Local files matter to you more than AI. You'd rather have a folder of plain Markdown you can open in any text editor for the next fifteen years than a cloud product whose roadmap you don't control. The friction with Logseq is mostly the mobile-and-sync side — and Obsidian's mobile is genuinely native, with a $4 sync that holds.

Recommendation Obsidian
Path C · The privacy-first kindred

You want encryption by default, not as an upgrade tier.

Logseq's local-first ethic was the part that mattered to you most. You don't want a cloud at all in the trust path; you want devices syncing peer-to-peer, every byte encrypted before it leaves the machine. AI is secondary — control of the data is the requirement.

Recommendation Anytype
The Migration Path

From Logseq to Knovya, graph and journal intact.

Five steps, roughly twenty minutes for a graph under a thousand pages. Wiki-links remap automatically, daily-journal pages stay daily-journal pages, block references resolve to inline anchors, and the encrypted layer is one toggle away on Pro.

  1. Copy your Logseq graph folder.

    Logseq stores everything as plain Markdown (or Org-mode) inside a folder you already control. Find it in Settings → Files — typically ~/Documents/Logseq/ or your iCloud / Syncthing path. Zip the whole folder, including journals/, pages/, assets/, and logseq/ so the configuration travels with it.

    $ cd ~/Documents/Logseq $ ls # journals/ pages/ assets/ logseq/ $ zip -r logseq-graph.zip .

  2. Drop the .zip into Knovya's importer.

    Open knovya.com/import, choose Logseq graph, drop the .zip. Knovya unpacks journals/ as daily-note pages with the right dates, pages/ as named notes, and assets as attachments. YAML frontmatter and Logseq properties parse into Knovya metadata; #tags become Knovya tags. You'll be reading the graph inside ten minutes.

  3. [[Wiki-links]] and block references resolve automatically.

    Logseq's [[Page Title]] wiki-links resolve by fuzzy title match against the new workspace and become live mention blocks. Unresolved links stay literal so nothing is silently lost. Block references — ((block-id)) — are converted to inline anchors that survive the move; the bidirectional backlink graph lights up in the right pane on first load.

  4. Connect Claude, Cursor, or ChatGPT through MCP.

    In Knovya, open Settings → MCP → Generate token. In Claude Desktop or Cursor, paste the server URL into the MCP config. Thirty-four tools become available — knovya_search, knovya_write, knovya_experience, and the rest — and the model can read and write your knowledge graph directly. Free tier ships 50 MCP calls per month, enough to wire Claude or Cursor and try the full memory layer.

    # claude_desktop_config.json "mcpServers": { "knovya": { "url": "https://mcp.knovya.com/v1", "auth": "oauth" } }

  5. Turn on end-to-end encryption for what matters.

    On Pro and Team, you can mark any note encrypted in the right pane. AES-256-GCM with a key derived from your passphrase; the ciphertext sits on Knovya's servers, the plaintext never does. Encrypted notes are excluded from server-side embeddings — search on those happens on-device. Privacy as a property of the data, not a backer-tier subscription.

The honest caveat: Logseq's Datalog queries ({{query …}}) and a handful of advanced plugins do not have a direct equivalent in Knovya. Most journal-and-graph workflows transfer cleanly. If your graph leans heavily on custom queries, keep the Logseq copy as a read archive and use Knovya for active capture and AI work while a query-translation layer matures.

Why we built it

Knovya isn't here to replace Logseq.
It's built for the era after the local-first vault.

Each tool above got one bet right. Obsidian's respect for your files. Roam's invention of the block reference. Anytype's privacy ethic. Tana's typed outliner. Logseq's open-source courage. Knovya's bet is the era after MCP — when outliner thinking, AI, and encryption travel together, on every device, without the technical tax.

  1. CLAIM 01

    NoteRank — the right note, before you finish typing.

    A fourteen-signal personal ranking that learns which notes you actually return to, then surfaces them first. Hybrid search blends Postgres full-text and pgvector embeddings via reciprocal rank fusion — the retrieval Logseq's classic full-text search never tried to be.

  2. CLAIM 02

    Experience Envelope — past precedents, by outcome.

    Group your archived plans, decisions, and retros by what actually happened next. The system surfaces the precedent that matches the situation in front of you — not just the matching keyword. The weekly synthesis is a property of the graph, not a prompt you write.

  3. CLAIM 03

    MCP-native — 34 tools, OAuth 2.1 with PKCE.

    The Model Context Protocol arrived November 25, 2024 and was donated to the Linux Foundation in December 2025. Knovya was designed around it. Claude, ChatGPT, Cursor, Gemini, Copilot, Windsurf, and Goose can read and write your graph directly — no plugin, no glue code.

  4. CLAIM 04

    End-to-end encrypted — AES-256-GCM, never embedded.

    Pro and Team include note-level end-to-end encryption. Encrypted notes are not searchable or embeddable on the server — search on those happens on your device. The cloud sees ciphertext or it sees nothing. Privacy as architecture, not as a backer-tier upgrade.

Start free — 50 notes, 50 AI credits, 50 MCP calls See pricing

Filed by · Knovya Editorial · 2026.05.05 · The Outliner Question

Reader Questions

The eight questions most often asked.

Drawn from People-Also-Ask boxes on the search results for "logseq alternative" and "logseq alternatives", and the threads on r/logseq, r/PKMS, and the Logseq community forum itself that surface the same questions in slightly different words.

What is the best Logseq alternative in 2026?

There is no single best Logseq alternative. The right choice depends on what you wanted from Logseq that Logseq cannot quite finish — reliable cloud sync, a mobile experience that does not feel like an afterthought, real-time collaboration, or AI that lives inside the outline rather than next to it.

Knovya is built for that last category — outliner-friendly with bidirectional links, MCP-native, end-to-end encrypted on Pro, with cross-platform parity from day one. Obsidian remains the closest like-for-like for users who want to stay local-first. AppFlowy is the closest open-source clone of Notion-style tools. Tana is the modern outliner with supertags.

Is there a free Logseq alternative?

Yes, several. Knovya Free includes 50 notes, 50 AI credits per month, and 50 MCP calls per month — enough to connect Knovya to Claude or Cursor and try the full memory layer with no credit card.

Obsidian is free for personal use, with optional Sync at around $4 to $5 per month. AppFlowy is fully free and open-source under GPL-3.0. Anytype has a free tier with end-to-end encrypted local data. Logseq itself is free under AGPL-3.0; the optional Logseq Sync runs through Open Collective at a $5 per month backer tier and remains in beta.

Is there an open-source Logseq alternative?

AppFlowy is the closest open-source clone for Logseq users who also want database-style structure — GPL-3.0, with a self-hostable cloud. Joplin is open-source and supports end-to-end encrypted sync across iCloud, Dropbox, and OneDrive. Anytype is open-source, local-first, and end-to-end encrypted by default. AFFiNE is a strong second for users who also want whiteboard-style canvases.

None of these match Knovya on AI-native search and MCP integration. The trade is open-source control versus AI-era capability.

Why does Logseq feel slow to develop?

Logseq is in the middle of a major architectural shift. The team is rebuilding the app on a database engine — known as Logseq DB — to support real-time collaboration, faster search on large graphs, and a redesigned mobile app.

The DB version reached an April 26, 2026 update with a new sync architecture and command-line tooling, but it is still in beta status, with the new mobile app and the RTC collaboration layer in alpha. That explains why public stable releases slowed in 2024 and 2025; the team is finishing the foundation underneath, not abandoning the project.

Does Logseq have a reliable mobile app?

The Logseq mobile app exists for iOS and Android, but it has long felt secondary to the desktop client. Across third-party reviews and the Logseq forum itself, users describe sync that disconnects, login flows that fail repeatedly, and a layout that does not hold up under heavy daily use.

The Logseq team is shipping a redesigned mobile app as part of the DB version, but at time of writing it is in invite-only alpha. Users who need true mobile parity now typically choose Obsidian, Anytype, or Knovya.

Logseq vs Obsidian — which is better for outlining?

Logseq is the more committed outliner: every line is a block, every block is referenceable, and the daily journal is the default workspace. Obsidian is page-first, with outlining available through the Outliner community plugin.

If your brain genuinely thinks in nested bullets and block references, Logseq's model fits better. If you write in longer paragraphs with the occasional list, Obsidian's page model is less friction. We cover the deeper trade-off on the Logseq vs Obsidian comparison page.

How do I move my Logseq graph to a new app?

Logseq stores notes as plain Markdown or Org-mode files in a folder you control, so migration is straightforward in principle. The journey is: export or copy your graph folder, import the Markdown into the new app, and accept that block references and Logseq-specific queries will need translation.

Knovya's import path keeps wiki-style [[backlinks]] live as mentions, preserves daily-journal pages, and converts block references to inline anchors where possible. Tools like AppFlowy, Obsidian, and Anytype each provide their own Markdown import; quality varies by feature.

Does Knovya support MCP for Claude and ChatGPT?

Yes. Knovya speaks the Model Context Protocol — the open standard Anthropic introduced on November 25, 2024 and donated to the Linux Foundation's Agentic AI Foundation in December 2025.

Knovya ships 34 MCP tools with OAuth 2.1 plus PKCE, so Claude, ChatGPT, Cursor, Gemini, Copilot, Windsurf, and Goose can read and write to your knowledge base directly. Free includes 50 MCP calls per month, Pro 5,000, Team unlimited.

The Bonded Panel

Where this dossier connects to the rest of the archive.

If you arrived here looking for one tool and want to read the others — or understand the concepts behind the bets — these are the next pages in the file.

Sibling alternative dossiers

Knovya features in this story

Concepts & adjacent hubs

The Conclusion

Logseq taught the field what an outliner could feel like.
It also taught us the cost of building it alone.

Each of the nine tools above got something right that no one else got first. Obsidian's respect for your files. Roam's invention of the block reference. Tana's typed outliner. RemNote's flashcards inside the bullet tree. AppFlowy's open-source ambition. Anytype's encryption ethic. Workflowy's pure outliner DNA. Notion's all-in-one bet. And Logseq's quiet, AGPL-licensed insistence that local-first matters.

On November 25, 2024, Anthropic introduced the Model Context Protocol — the first open standard for AI to read and write across your knowledge. Knovya launches in 2026 for that era: outliner-friendly capture, MCP-native AI, end-to-end encryption, cloud sync without the backer-tier asterisk, mobile parity, and the speed of a desktop app. Built on the lessons each of these tools — Logseq especially — taught the field.

The rest of the archive is at /features and /manifesto if you want to see what we built and why.

— Filed by Knovya Editorial · 2026.05.05