OpenAI 2026 hackathon

echooo

Just talk, just snap — "echooo" helps turn it all into memories you can find again.

Solo project by Frank Ho · 2 likes · 0 comments

Archive position — measured, not model output

2 likes on Devpost

221 of the 7,856 archived projects have more likes, and 285 share exactly 2 — so this project's #311 place in the like-ranked listing is a tie-break inside that group, not a ranking.

Projects (log scale)

1
10
100
1k
10k
05,592
11,758
2285
3–4132
5–975
10+14

Likes on Devpost. ▲ marks this project's group.

Show the figures
LikesProjectsShare of archive
05,59271.2%
11,75822.4%
22853.6%
3–41321.7%
5–9751.0%
10+140.2%
Devpost like counts for all 7,856 archived projects, captured when this archive was built.

Executive Summary

What the company appears to be

echooo is a self-reported personal memory capture and retrieval tool built as a prototype for the OpenAI 2026 hackathon. It allows users to record voice notes (optionally with photos) in a private, voice-first space and later transform those into structured drafts for review and confirmation before saving them as memories. The system uses AI to process audio transcripts and natural language queries, aiming to reduce the effort required to organize personal experiences.

What changed

The project is described as an experimental prototype built under time constraints during a hackathon. It does not appear to have moved beyond that stage or gained any traction, revenue, or customer base.

Single most important open question

Is there evidence of real user adoption or engagement beyond the author’s own use and limited testing with friends?

Back to contents

What The Product Actually Is

The description states that echooo is a private, voice-first space where users can capture life stories, thoughts, and future intentions. It supports:

  • Voice recording (with optional photo attachment)
  • Saving raw content as pending records
  • Conversion into editable drafts via AI
  • Review and modification of structured elements like people, events, emotions, and follow-ups
  • Confirmation and storage of memories
  • Retrieval through natural voice queries or filtering

The system is described as using AI models (GPT-5.6, Nova-3) for transcription and structuring, but not for direct database access. The backend is built with Rust/Axum, frontend with React/Next.js, and uses PostgreSQL for data storage.

Not evidenced: whether the product works beyond the prototype level or has been tested at scale.

Back to contents

Positioning & Claim Evolution

The author claims echooo addresses a personal problem — documenting life without public sharing or organizational effort. The positioning is:

  • Private
  • Low-effort capture
  • Voice-first
  • Designed for people who don’t want to organize but still want to remember

It evolved from a personal frustration into a working prototype, with the author stating that the solution emerged gradually during development.

Inferred: The product may be positioned as a niche tool for individuals seeking a less burdensome way to preserve memories — not a mass-market or enterprise offering.

Not evidenced: Any market positioning beyond personal use, nor any claims about competitive differentiation or scalability.

Back to contents

Target Customer & ICP

The description states that echooo targets people who don’t want to share publicly and don’t have time to organize. These users are said to:

  • Want to document life but avoid social media
  • Prefer natural capture over formal journaling
  • Value low-effort recording and retrieval

It is implied that the primary user is an individual, not a business or organization.

Not evidenced: Specific demographics, usage patterns, or whether there’s a defined ICP beyond "someone with a busy life".

Back to contents

Business Model & Pricing Evidence

The description does not state any business model or pricing strategy. It only describes the product as a personal tool, built for a hackathon.

Inferred: If this were to evolve into a commercial product, it might be subscription-based or freemium, but no such claims are made.

Not evidenced: Any monetization approach, revenue streams, or pricing tiers.

Back to contents

Technical & Delivery Signals

The system is described as:

  • Built with React/Next.js (frontend)
  • Rust/Axum (backend)
  • Uses PostgreSQL for storage
  • Leverages AI models: GPT-5.6, Nova-3, Codex
  • Uses MediaRecorder API for browser-based recording
  • Deployed via Docker/Docker Compose
  • Has a mobile-first experience

The author notes that AI was used extensively in development but not for isolated code snippets — instead, tasks were defined as complete units with clear scope and validation.

Not evidenced: Production readiness, scalability, or performance metrics. The system is described as a prototype deployed on an HTTPS server.

Back to contents

Traction & Maturity Signals

The description states that the project was built within a hackathon timeframe, under time constraints due to full-time employment.

It mentions:

  • Deployment of a working version
  • Invitation of a small group of friends for testing
  • Iteration planned based on feedback

However, no data is provided about:

  • Number of users or active users
  • Retention rates
  • Conversion from recording to confirmation
  • Usage frequency or duration

Not evidenced: Any traction, adoption, or user engagement beyond the author’s own experience and limited friend testing.

Back to contents

Competitive Context

The description does not mention any competitors. It implies that existing tools help store information but few reduce the cost of organizing life.

Inferred: The product may compete with personal journaling apps, voice recorders, note-taking tools, or AI-powered memory systems — though no direct comparison is made.

Not evidenced: Any competitive landscape, market size, or differentiation from similar offerings.

Back to contents

Key Risks & Red Flags

  • Prototype-only status: No evidence of real-world usage beyond the author and a few friends.
  • No revenue or monetization strategy described.
  • High reliance on AI tools (Codex, GPT) without clear governance or validation systems for long-running tasks.
  • Limited scalability: Built as a hackathon prototype with no indication of infrastructure or performance testing.
  • Privacy and data handling: While privacy is emphasized, no details are given about how user data is protected or managed.

Not evidenced: Any risk mitigation strategies or compliance measures beyond stated constraints.

Back to contents

Diligence Questions To Ask The Founders

  1. What specific problems do users encounter when trying to organize their memories manually?
  2. How does the system handle ambiguity in natural language queries or voice inputs?
  3. Are there any plans for user data ownership, export, or deletion?
  4. Has the product been tested with more than a few friends? If so, what were the key feedback points?
  5. What is the long-term vision for monetization or commercial viability?
  6. How does the team plan to scale beyond the current prototype?
  7. What are the limitations of AI-assisted development in this context, and how are they being addressed?

Back to contents

Investment/Partnership Verdict

This project is described as a hackathon prototype with no evidence of traction, revenue, or customer base.

The author states that the product works but remains in early-stage testing. There is no indication of any commercialization path, user growth, or market validation.

Inferred: This is an experimental idea with potential for future development — not a ready-to-invest or partner opportunity.

Not evidenced: Any commercial viability, scalability, or strategic fit for investment or partnership.

Back to contents

Source

Submitted to the OpenAI 2026 hackathon on Devpost. Project home on DevPost.

The analysis above was generated by a language model from the project's own one-line description. It is not independent research and contains no verified traction, revenue or customer data.