Running Notes

The description states that Running Notes is a system where users record audio via a browser, which then becomes an email delivered to an IMAP mailbox. It uses Dovecot for mail infrastructure and FastAPI for backend services.

• Functionality: Voice recording → upload → conversion into email → delivery via LMTP to Dovecot.
• Delivery method: Email inbox (IMAP), accessible through standard mail clients like Outlook or Thunderbird.
• User interface: Browser-based mailbox view with audio playback.
• Deployment: Containerized, with TLS termination, public guest path, and autoconfiguration for mail clients.

Inference The product is not a note-taking app but a bridge between voice capture and email delivery. It leverages existing mail infrastructure rather than building its own.

The author claims that Running Notes was inspired by the need to capture ideas instantly and process them later using familiar tools — specifically, email inboxes.

• Original intent: To avoid disconnecting thoughts from work tools by delivering voice notes directly into a mailbox.
• Evolution: From a personal demo to a productized version with public access and developer-friendly deployment.
• Positioning: A minimal, no-registration solution for capturing and organizing ideas via email.

Inference The positioning is niche — targeting individuals who already use email as their primary work tool and want to capture spontaneous thoughts without switching apps.

The description does not state specific customer segments or personas.

• Self-reported target: Likely individuals who take voice memos during daily activities (e.g., walking, cooking) and prefer processing them in an email inbox.
• ICP inference: Early adopters of developer tools or productivity systems that integrate with email workflows.

Not evidenced No explicit customer data, user interviews, or segmentation beyond the author’s personal use case.

The description does not mention pricing or monetization strategies.

• Self-reported model: No registration required; public guest access.
• Monetization claims: None stated.

Inference The product appears to be free-to-use with no commercial layer. It may be a side project or prototype, not intended for revenue generation at this stage.

The author describes technical implementation details:

• Stack: FastAPI, Dovecot, IMAP, nginx, OAuth, Python, SQLite, voice recording via MediaRecorder API.
• Deployment: Containerized with Docker Compose; TLS termination; public access via boringproxy.
• AI integration: GPT-5.6 Sol used for DevOps tasks including debugging and service configuration.
• Workflow: Used tmux + Codex + Handsfree Vibe Coding Android app for remote development.

Inference The system is built with minimal infrastructure, leveraging existing mail servers and open-source tools. It shows a strong developer focus and use of AI in deployment and debugging.

The description does not provide any evidence of traction or user adoption.

• Maturity level: Productized but likely limited to the author’s own usage.
• User base: Not stated; no customers, users, or feedback mentioned.
• Growth metrics: None provided.

Inference The project is at a very early stage — possibly a prototype or personal tool with no external validation or market traction.

The description does not mention competitors or similar tools.

• No competitive analysis: No reference to existing voice-to-email, note-taking, or productivity apps.
• Market positioning: Not compared to other tools in the space.

Inference The author has not positioned Running Notes within a broader market context. It may be an isolated solution with no known direct competitors.

Several risks and red flags are evident from the self-reported description:

• No commercial traction or revenue: No evidence of users, customers, or monetization.
• Single-person team: Only one developer (Oleg Parashchenko) involved.
• Unverified claims: All information is self-reported; no independent verification.
• Limited scope: Designed for personal use and basic functionality — not scalable or enterprise-ready.
• Developer-centric tooling: Uses AI tools like GPT-5.6, but this may limit accessibility to non-developers.

Inference The project lacks commercial viability or scalability without further evidence of adoption or funding.

1. What is the actual user base beyond your own usage?
2. Are there any customers or users who have paid for or subscribed to this service?
3. How do you plan to scale beyond a single developer and personal use case?
4. Is there a long-term vision for monetization or commercial growth?
5. Have you considered how this would work in enterprise environments or with more complex workflows?