Roam Research

Name: Roam Research
Brand: Roam Research

A note-taking tool for networked thought

Est 2017|Valuation $200M|Raised $12.4M|8 Ref Customers

LinkedIn 2K|Web traffic 221K|FTEs 11|HQ San Francisco, us

MarketsPersonal Productivity

Published Oct 15, 2026

01Common complaints

Consider alternatives when: 1. Offline-first operation is required (for example, frequent travel or unreliable connectivity). Tools such as Obsidian or Logseq are typically more aligned with offline workflows. 2. Audited enterprise security and compliance are mandatory (SOC 2 reports, ISO certifications, DPA documentation, and explicit encryption statements were not publicly available in this research session). 3. The primary requirement is a team research repository with simple onboarding and governance; other platforms (Notion, specialized research tools) may better support structured team repositories. 4. Budget constraints make an ongoing subscription untenable; free or lower-cost alternatives may meet required workflows. 5. Stable, well-documented integrations and automations are required; evaluate platforms with public APIs and active integration marketplaces.

Deal disqualifiers (poor fit)

Requirement for offline-first operation by default
Requirement for audited enterprise security/compliance (SOC 2, SSO/SCIM, documented encryption)
Need for extensive team governance and simplified onboarding for large contributor sets
Highly price-sensitive users or organizations unable to justify an ongoing subscription

Performance limitations

Community reports indicate degraded performance on very large graphs (thousands of pages), including slow backlinks and general lag.

Pricing considerations

Repeated community feedback indicates concerns about affordability and limited regional or student pricing options.

Privacy/security uncertainty

Concerns persist that the hosted architecture could permit vendor-side access to notes; stronger client-side encryption and formal security documentation are requested by some users.

Integration limitations / ecosystem risk

Reports of third-party integration access being restricted have raised concerns about the stability of automation and third-party tooling.

API access (partial)

Roam provides API token functionality within graph settings and an official-scoped npm package exists for API access; however, the breadth and stability of third-party automation support appear limited based on community reports.

02Why they buy

Features commonly cited by users

Block-based outlining and rearrangement: users report the interface makes moving bullets and blocks straightforward.
Bi-directional linking and backlinks: users indicate this supports discovering relationships between notes and building interlinked topic pages.

Marketing-style claims and evidence quality

Claims such as improved cognitive outcomes or transformative problem solving are aspirational and not supported by measurable evidence in available public sources. Reported benefits are primarily anecdotal.

Areas where competitors have documented advantages

Obsidian: offline-first operation, local data ownership, and documented encryption options for sync services.
Logseq: open-source transparency and local-first control at lower direct cost.
Notion: team onboarding, databases, and structured organizational documentation.

03Field reports

Review-platform excerpts (Capterra)

- Positive (linking / thought mapping): - A reviewer described appreciation for linking between notes and indicated it helped create a mental map of thoughts. - Negative (pricing/value): - A reviewer expressed that the pricing model was high relative to perceived feature value and contrasted pricing with other tools such as Notion. - Mixed (feature scope and value): - A reviewer noted Roam performs well for a specific set of capabilities but requested additional new features and a different pricing approach.

Community/social excerpts (Reddit)

- Pricing pressure and affordability: - Some users indicated concern that a subscription in the low tens per month may not be affordable for students or users in certain regions and advocated for discounted plans. - Performance complaints at scale: - Reports from long-time users describe performance issues with large graphs and indicate difficulties on mobile/tablet devices. - Privacy trust model concern: - Community discussion includes concerns that the service could technically access user notes and requests for stronger encryption defaults. - Churn to alternatives: - Several users described leaving Roam for other tools due to perceived lag and offline limitations, while others remain due to Roam's block-based workflow.

Themes summarized from reviews and discussions

- Positive drivers: - Block-level writing and rearrangement - Bi-directional linking and backlinks - Daily Notes workflow for journaling and task capture - Query and block reference features enabling flexible retrieval - Common reasons cited for leaving: - Ongoing cost relative to feature velocity - Performance degradation on large graphs - Lack of a fully offline-first experience - Privacy/security model not meeting expectations for end-to-end encryption - Team onboarding friction and difficulty standardizing usage

Vendor-published case studies

No vendor-authored case studies with quantified ROI were retrievable from public sources during this research session.

Community-provided usage accounts (informal)

- Several long-term users report building multi-year systems and substantial personal investment in structure. - Other users report migrating away after extended use due to performance, cost, or perceived stagnation. Critical evaluation: These accounts describe real-world usage patterns but are anecdotal, lack independent validation, and are subject to selection bias. They can be informative for qualitative context but should not substitute for vendor-provided, audited case studies with measurable outcomes.

04Best fit

Organization size

Individuals and small teams (1–20) appear to have the strongest fit.
Larger organizations can use Roam but may encounter challenges related to onboarding consistency, security documentation, and governance.

Industries / verticals

Education and research
Writing and media
Software and AI research
Consulting and strategy

Roles and personas

Primary decision makers: individual users, team leads, or knowledge management champions
End users: researchers, writers, product managers, engineers, analysts, and students

Problems addressed

Capturing ideas rapidly without imposing a fixed organizational structure
Retrieving knowledge via linking/backlinks/queries rather than folder hierarchies
Connecting concepts over time through daily notes and cross-references

Qualification criteria (likely fit)

Intended for users with daily usage patterns that benefit from deep linking and block references
Willingness to accept an ongoing subscription for a focused tool
Preference for emergent structure over strict folder or database organization

05The pitch

What the product does (objective value proposition)

Roam Research is a web-based, block-structured note-taking and personal knowledge management (PKM) tool oriented around networked thought. The product's design emphasizes dense linking and searchability rather than a folder hierarchy. The interface uses an outliner-style approach (bullets/blocks) and supports bi-directional links, block references/embeds, and query capabilities to enable retrieval and connection of notes.

Target market and positioning

Roam is commonly used by:

Individual knowledge workers (writers, researchers, students, founders, consultants) seeking non-linear note-taking.
Power users who prefer block-level linking, daily notes journaling, and emergent structure.
Some small teams where team-level conventions are established; community feedback indicates operationalizing consistent team workflows can be challenging.

Get a comprehensive analysis of Roam Research including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →