Archive position — measured, not model output
4 likes on Devpost
89 of the 7,856 archived projects have more likes, and 39 share exactly 4 — so this project's #111 place in the like-ranked listing is a tie-break inside that group, not a ranking.
Projects (log scale)
Likes on Devpost. ▲ marks this project's group.
Show the figures
| Likes | Projects | Share of archive |
|---|---|---|
| 0 | 5,592 | 71.2% |
| 1 | 1,758 | 22.4% |
| 2 | 285 | 3.6% |
| 3–4 | 132 | 1.7% |
| 5–9 | 75 | 1.0% |
| 10+ | 14 | 0.2% |
Executive Summary
What the company appears to be
Mnemcore is a self-reported semantic memory system for video, built as a web platform that transforms human-authored timestamped notes and video into a searchable knowledge base. It claims to enable organizations to ask natural-language questions about video content and receive evidence-backed answers grounded in the original moments.
What changed
The project description is a self-reported account of a hackathon submission. There is no evidence of prior traction, revenue, or customer adoption beyond the author's own development work.
Single most important open question
Is there any evidence that Mnemcore has been used by teams outside of its creator’s own development process, and if so, how does it perform in real-world use?
What The Product Actually Is
The description states that Mnemcore is a semantic memory system for video. It transforms human-authored timestamped notes and video into a searchable knowledge base. Users can ask natural-language questions and receive answers grounded in the original video moments.
It uses:
- Semantic vector search
- Lexical search
- Timestamp constraints
- Reciprocal rank fusion
- OpenAI models for answer synthesis
The system is built with Vue, TypeScript, Tailwind, FastAPI, PostgreSQL, Supabase, pgvector, and cloud video infrastructure.
Evidence The author’s own write-up.
Inference Mnemcore appears to be a hybrid search and retrieval system that combines vector embeddings with traditional text search and temporal constraints to surface relevant evidence from video content.
Positioning & Claim Evolution
The description states that Mnemcore is designed to help teams preserve the meaning they discover while watching video, turning disconnected notes into shared organizational knowledge. It positions itself as a tool for storing, organizing, and extending human experience through AI.
It began with sports but has a broader vision: “anywhere important knowledge is trapped inside video.”
Evidence The author’s own write-up.
Inference Mnemcore's positioning evolved from a niche solution for sports analysis to a general-purpose semantic memory system for any domain where video contains valuable, scattered insights.
Target Customer & ICP
The description states that Mnemcore was inspired by the need to preserve organizational knowledge in sports teams. It targets organizations that have accumulated knowledge inside video but lack systems to retrieve it effectively.
It also mentions potential applications in education, research, training, operations, interviews, and creative work.
Evidence The author’s own write-up.
Inference The primary ICP appears to be teams or individuals who consume video content for learning or analysis and want to make that knowledge searchable and reusable. It is not clear if there are specific verticals prioritized beyond sports.
Business Model & Pricing Evidence
Not evidenced.
The description does not mention any pricing, monetization strategy, or business model.
Evidence The author’s own write-up.
Technical & Delivery Signals
Mnemcore uses:
- Semantic vector search (pgvector, text-embedding-3-large)
- Lexical search (PostgreSQL full-text search)
- Hybrid retrieval (reciprocal rank fusion)
- Timestamped evidence linking
- Retrieval-augmented generation (RAG) pipeline with OpenAI models
- Video ingestion and note capture workflows
It is built using Vue.js, TypeScript, FastAPI, PostgreSQL, Supabase, Docker, Cloudflare Pages, and other technologies.
Evidence The author’s own write-up.
Inference The system is designed to be modular and scalable, with a focus on retrieval accuracy over generative complexity. It emphasizes grounding answers in evidence rather than hallucination.
Traction & Maturity Signals
Not evidenced.
There is no mention of users, customers, revenue, or adoption beyond the author’s own development work.
Evidence The author’s own write-up.
Competitive Context
Not evidenced.
The description does not reference any competitors or market positioning relative to existing tools for video analysis, semantic search, or knowledge management.
Evidence The author’s own write-up.
Key Risks & Red Flags
- No evidence of real-world use: The system appears to be a prototype built by one person for a hackathon.
- Unproven scalability: The description mentions challenges with scale and stability, especially around clustering and signal detection.
- Lack of commercial traction: No data on users, revenue, or customer feedback.
- Overreliance on author's own evaluation: The system’s performance is based on internal testing rather than external validation.
Evidence The author’s own write-up.
Diligence Questions To Ask The Founders
- What specific use cases have you tested Mnemcore with beyond your own development?
- How do you plan to validate the accuracy and utility of retrieved evidence in real-world settings?
- Are there any early adopters or pilot users who are providing feedback?
- What is the current architecture for handling large-scale video ingestion and embedding?
- How do you intend to monetize this product, if at all?
Evidence The author’s own write-up.
Investment/Partnership Verdict
Not evidenced.
There is no evidence of funding, valuation, or any commercial interest from investors or partners beyond the project being submitted to a hackathon.
Evidence The author’s own write-up.
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.
