rumi.md

The description states that rumi.md is a self-hosted, open-source markdown editor with database-like functionality and block editing capabilities. The author describes it as an alternative to Obsidian and Notion, aiming for file-based reliability and AI-friendliness while offering cloud-like access and sharing features.

Key elements from the description:

• It uses a server-client architecture where the server watches a folder and exposes it via localhost.
• The client is swappable web UI built with React, ProseMirror, and other technologies.
• It supports GitHub-flavored markdown and can run offline.
• The project pivoted from an Electron app to a self-hosted model for better scalability and sync.
• It includes custom .db.md and .index.md extensions to structure content while preserving file-first principles.

The author claims this is a personal project built with AI assistance (Claude, Codex), and the core idea emerged from dissatisfaction with existing tools like Obsidian and Notion.

Most important open question: Is there any evidence of user adoption or commercial traction beyond the author's own development efforts?

The description states that rumi.md is:

• A self-hosted, open-source markdown editor
• With database-like functionality (flavored DB)
• And block editor capabilities
• Built with a server-client architecture
• File-based like Obsidian but cloud-like in access and sharing features
• Runs offline via localhost

It uses:

• JavaScript, Node.js, React, ProseMirror, shadcn, SQLite, Tailwind, TypeScript, Zustand
• GitHub-flavored markdown support
• A folder-based workspace that gets indexed/cache by the server
• Client-side rendering of MD/HTML and sending changes to the server
• Custom .db.md and .index.md extensions for structuring content

Inferred from the description:

• The client is swappable web UI, implying flexibility in interface design or functionality.
• It supports asynchronous work and AI-friendly organization.

Not evidenced:

• Specific features beyond what's described (e.g., views, props, formulas).
• Any actual product usage or user feedback.
• Revenue model or monetization strategy.

The description states that rumi.md was inspired by a "love/hate" relationship with Obsidian and Notion:

• File-first approach is seen as more reliable, faster, and AI-friendly than cloud-based solutions
• Notion’s structure and collaboration features are appreciated but criticized for speed and integrations
• The name “Rumi” comes from the idea of ruminating — a metaphor for deep thinking or memory organization

The author positions rumi.md as:

• A tool for personal knowledge management and asynchronous work
• An alternative to Obsidian (file-based) and Notion (cloud-based)
• Designed with AI in mind, supporting memory, organization, and async workflows

Inferred from the description:

• The project evolved from an Electron app to a self-hosted model due to sync challenges.
• It aims to combine the best of both worlds: file-first reliability and cloud-like access.

Not evidenced:

• Market positioning or competitive differentiation beyond personal preference.
• Any marketing claims or user testimonials.
• Evidence of product-market fit or early adopter feedback.

The description states that rumi.md targets users who:

• Prefer file-based systems over cloud/MCP
• Value AI-friendliness and memory organization
• Want highly customizable workspaces
• Like to have swappable clients for appearance and functionality

It is described as being for people who:

• Are interested in asynchronous work
• Want reliable, fast, and AI-friendly tools
• Prefer self-hosted solutions over proprietary platforms

Inferred from the description:

• Likely appeals to developers or power users familiar with markdown and file systems.
• Could attract individuals seeking alternatives to Obsidian or Notion.

Not evidenced:

• Specific customer segments or personas.
• Customer acquisition strategy or early user base.
• Any evidence of target market size or demand.

The description states that rumi.md is:

• Open-source and self-hosted
• Built with AI tools (Claude, Codex)
• Not monetized in the current version

No explicit business model or pricing information is provided. The author mentions:

• Hosting as a future feature for casual users
• OAuth support for authentication providers
• Custom client support as a potential next step

Inferred from the description:

• Future monetization could come through hosting services or premium client features.
• It may eventually offer paid hosting or enterprise-grade functionality.

Not evidenced:

• Any revenue streams, pricing tiers, or commercial partnerships.
• Evidence of monetization strategy beyond future plans.

The description states that rumi.md was built using:

• JavaScript, Node.js, React, ProseMirror, shadcn, SQLite, Tailwind, TypeScript, Zustand
• Electron initially, then pivoted to server-client architecture
• Built with AI tools (Claude, Codex)
• Uses GitHub-flavored markdown
• Supports offline operation via localhost

It includes:

• Folder-based workspace that gets indexed/cache by the server
• Client-side rendering of MD/HTML and sending changes to the server
• Custom .db.md and .index.md extensions for structuring content
• Tests integrated into task pipeline (investigate, interview, implement, write test, run tests, commit)

Inferred from the description:

• The architecture supports scalability through self-hosting.
• It leverages modern frontend frameworks and state management.

Not evidenced:

• Performance benchmarks or technical scalability data.
• Any production deployment or infrastructure details.
• Integration with third-party APIs or services.

The description states that rumi.md is:

• A personal project by one developer (Illia Korchahin)
• Submitted to the OpenAI 2026 hackathon
• Built using AI tools and agent-based workflows
• Includes tests in its development pipeline

It was built with:

• AI agents for task planning and execution
• Agent-based documentation (agents.md instructions)

Inferred from the description:

• The project is at an early stage of development.
• It has some level of automation in its build process.

Not evidenced:

• Any user adoption or customer base.
• Revenue, ARR, or funding data.
• Product maturity indicators like release history or feature roadmap.
• Evidence of traction beyond the author's own efforts.

The description states that rumi.md aims to be an alternative to:

• Obsidian (file-first, reliable, fast)
• Notion (cloud-based, collaborative, structured)

It is positioned as a solution that combines:

• File-first reliability and AI-friendliness
• Cloud-like access and sharing features

Inferred from the description:

• It competes with tools like Obsidian and Notion in knowledge management.
• The author sees gaps in both platforms that rumi.md intends to fill.

Not evidenced:

• Direct competitors or competitive analysis.
• Market share, pricing, or differentiation metrics.
• Any evidence of market presence or user feedback from competitors.

The description states several challenges faced during development:

• Sync across devices was a major challenge — led to the pivot to self-hosted model
• Block editor development was difficult due to lack of suitable existing editors (TipTap was close but not quite)
• Building new features often broke old ones, so tests were integrated into the pipeline

Inferred from the description:

• The project may struggle with complex feature integration without breaking existing functionality.
• Sync and backup mechanisms are critical for user experience but remain unproven in this version.
• The author is building a tool primarily for personal use or niche needs.

Red flags:

• No evidence of commercial traction or user feedback.
• Single-person development team implies limited scalability.
• Lack of clear monetization strategy or business model.

Not evidenced:

• Any risk mitigation strategies beyond test integration.
• Evidence of market validation or product-market fit.

1. What specific problems are you solving that existing tools like Obsidian and Notion don’t address well?
2. How do you plan to scale beyond a single developer’s effort, especially in terms of feature development and maintenance?
3. Are there any early adopters or users who have provided feedback on the current version?
4. What is your roadmap for monetization? Is hosting or premium features part of that?
5. Can you walk us through how the sync and backup mechanisms work in practice?
6. How do you intend to attract users beyond personal interest or niche usage?
7. Have you considered integrating with popular platforms like GitHub, GitLab, or cloud storage providers?