Oyma vs Logseq

Logseq and Oyma both appeal to people who care deeply about digital privacy, data sovereignty, and offline-first personal knowledge management. Neither tool relies on a corporate cloud to function, and neither tool monetizes your personal thoughts.

However, they represent two radically different approaches to note-taking architecture and meeting capture. Logseq is a community-driven, open-source outliner inspired by Roam Research, where every note is a tree of nested bullet blocks. Oyma is a focused, polished document editor for macOS that combines Obsidian-compatible Markdown files with native, on-device meeting recording.

Furthermore, Logseq is currently navigating a major architectural transition—moving from plain text files to a local SQLite database in Logseq 2.0—while Oyma doubles down on standard Markdown files on disk.

Writing structure: outliner blocks vs document prose

The most immediate practical difference between Logseq and Oyma is how you compose words on the screen.

In Logseq, the entire application is an outliner:

• Every paragraph is an indented bullet point, internally tracked as a discrete block with its own unique block ID (block-id).
• You organize thoughts by indenting (Tab) and unindenting (Shift+Tab), creating deep parent-child hierarchies.
• You can reference or embed individual blocks across multiple pages without copying text, updating automatically when the source block changes.
• Complex properties and Datalog queries allow you to query blocks across your entire knowledge base like a relational database.

For structured task tracking, research indexing, and granular thought aggregation, this outliner model is immensely powerful. But for long-form writing—such as essays, technical documentation, meeting minutes, client proposals, and narrative summaries—an outliner can feel restrictive. Many writers experience “bullet fatigue,” finding it unnatural to break paragraphs of prose into disjointed bullet points.

In Oyma, the writing experience is document-first:

• You write continuous, flowing Markdown prose with headings, standard paragraphs, blockquotes, and callouts.
• The editor features active live preview: Markdown syntax disappears cleanly behind formatted typography while remaining plain text under the hood.
• Tables behave like familiar desktop spreadsheets: you can navigate cells with Tab and Enter, sort columns alphabetically or numerically, and paste tabular data directly from Numbers or Excel.
• Links use standard bidirectional [[WikiLink]] syntax with piped aliases, heading autocompletion, and an interactive force-directed graph view.

If your primary thinking style revolves around atomic, bulleted concepts and block transclusion, Logseq is purpose-built for you. If you write narratives, documentation, and formatted meeting records, Oyma offers a far more natural canvas.

The storage divide: Logseq’s database rewrite vs plain Markdown files

When Logseq originally gained widespread popularity, its core promise was that your graph lived as plain .md and .org files in a local folder. However, synchronizing thousands of granular block hierarchies against text files created persistent technical challenges, including frequent re-indexing delays, cache desynchronization, and merge conflicts.

In response, the Logseq team announced a fundamental architectural pivot:

• Logseq OG (file-based): The classic Markdown file version is now in maintenance mode, receiving security patches and dependency updates only.
• Logseq 2.0 (database-based): The new generation of Logseq stores user graphs in a local SQLite database, treating Markdown as an import/export format rather than the primary storage medium. The 2.0 beta explicitly cautions users about potential stability issues during development.

This transition has placed many users in a difficult dilemma: accept a proprietary database format to receive new features, or remain on a legacy version that will receive no further enhancements.

Oyma resolves this tension by maintaining a strict, non-negotiable contract with the local filesystem:

• Every note is an ordinary .md file stored directly on disk in a folder you control.
• Your vault requires no proprietary background daemon, SQLite schema conversion, or import/export pipeline.
• You can open your vault folder directly in Obsidian, Visual Studio Code, iA Writer, or standard command-line tools without data loss.
• SQLite is utilized strictly as an ephemeral, read-only search index (sqlite-fts5) for sub-10ms full-text search, never as the authoritative storage layer.

Meetings: zero capability vs native on-device recording

A defining capability of Oyma is that meeting intelligence is built directly into the note-taking core. Logseq has no built-in meeting recording, audio capture, or transcription functionality.

To manage meeting notes in Logseq, you must assemble a patchwork of external utilities:

1. Launch an external recorder or cloud meeting bot (such as Otter or Granola).
2. Wait for audio upload, cloud processing, and transcript generation.
3. Export the resulting text and manually paste it into a Logseq journal page.
4. Manually reformat paragraphs into indented bullet blocks and add link brackets.

Oyma turns meeting capture into an effortless, private macOS workflow:

• Zero-bot audio capture: Using ScreenCaptureKit (macOS 14.2+) and CoreAudio, Oyma captures both your microphone and call audio from Google Meet, Zoom, Microsoft Teams, Slack huddles, or Webex without dispatching a bot.
• Local transcription: Embedded Whisper models transcribe spoken dialogue directly on Apple Silicon across 13 languages, with zero audio bytes transmitted over the network.
• Automated vault integration: When the call ends, your recording, verbatim transcript, and structured summary land immediately as a clean Markdown note in your vault.
• On-device AI summaries: With Ollama installed, Oyma summarizes meetings into five deterministic archetypes (Executive, Action items, Decision log, Thematic, and Comprehensive) completely offline.

Privacy, platforms, and open source

Logseq’s greatest strength is its open-source lineage. It is licensed under the AGPL-3.0, backed by a global open-source community, and runs natively across macOS, Windows, Linux, Android, and iOS. If you require multi-platform access on Linux or mobile devices today, or if open-source licensing is a strict requirement for your organization, Logseq is the clear winner.

Oyma is tailored specifically for knowledge workers on macOS:

• Engineered for Apple Silicon unified memory, delivering sub-50ms note switching and instant startup.
• Local-only mode completely isolates the application from outbound network requests at the socket level, verified by a transparent egress log.
• Native macOS integration includes calendar attendee detection, Keychain credential storage for BYOK AI keys, and full VoiceOver accessibility compliance.

Summary verdict

Choose Logseq if you think in nested bullet outlines, depend on block-level transclusion and complex queries, need to sync your notes to Linux or mobile devices, and prioritize open-source software.

Choose Oyma if you want a fast, elegant Markdown document editor on macOS that keeps your notes as standard files on disk and captures your meetings with on-device transcription and zero cloud dependencies.

Where Logseq is better

• Free and open source with an active community (45k+ GitHub stars).
• Outliner-first block references and queries that a page-based editor lacks.
• Runs on Windows, Linux and Android as well as Mac.
• Plugin marketplace and themes.

Thinking of moving? Your notes in Oyma are plain Markdown, so you can always take them with you. Start withgetting started, or read what leaves your Mac.

Looking at other options too? Read our guide to the best Logseq alternatives.