Archive position — measured, not model output
0 likes on Devpost
2,263 of the 7,850 archived projects have more likes, and 5,587 share exactly 0 — so this project's #7,832 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,587 | 71.2% |
| 1 | 1,758 | 22.4% |
| 2 | 284 | 3.6% |
| 3–4 | 132 | 1.7% |
| 5–9 | 75 | 1.0% |
| 10+ | 14 | 0.2% |
User Stories BotA demo video on every pull request
Get a demo video on every new feature
GitHub App that watches your pull requests and records a narrated, captioned demo.
Save time on demo prep and make informed decisions faster with a video walkthrough of every new feature.
Executive Summary
What the company appears to be
Kotobako is an anonymous question-and-answer service designed for Threads users, built as a hackathon project by one developer (RAY Paw). The product allows users to receive anonymous questions, draft replies, and publish selected question-answer pairs sequentially to Threads. It includes features like recovery of interrupted publishing jobs, previewing content as paired images, and managing notifications.
What changed
The author states that this was built during the OpenAI 2026 hackathon. No prior version or evolution is described; it is presented as a new product concept with no evidence of prior traction or development history.
Single most important open question
Is there any evidence of user adoption, revenue, or customer engagement beyond the author's self-reported claims?
Note: This analysis is based entirely on the self-reported and unverified project description provided by the author. No third-party verification, archived data, or independent sources are available.
What The Product Actually Is
The description states that Kotobako is an anonymous question-and-answer service for Threads users. It enables:
- Creation of a personal "Kotobako inbox"
- Receiving anonymous questions
- Writing and saving replies
- Previewing questions and answers as paired images
- Publishing question-answer pairs sequentially to Threads
- Tracking publishing progress
- Recovering interrupted or failed publishing jobs
- Controlling anonymous messages, muted words, and notifications
The system avoids publishing only the question; it treats the question and answer as a single publishing flow.
Inference: The product is a tool for managing anonymous Q&A on Threads, with an emphasis on reliability in publishing workflows.
Claim vs Fact: These are claims made by the author about what the product does — not verified or substantiated.
Positioning & Claim Evolution
The author positions Kotobako as a way to enable honest feedback and conversation on Threads by allowing users to ask questions anonymously. The tagline is: “Anonymous questions, thoughtful replies, and seamless Threads publishing.”
Inference: The positioning reflects a desire to improve engagement on Threads through anonymity and structured publishing.
Claim vs Fact: This is the author’s stated intent and positioning — not evidence of traction or market validation.
Target Customer & ICP
The description states that Kotobako is designed for Threads users who want to receive anonymous questions and publish selected replies as conversations. It does not specify a segment beyond general Threads users, nor does it indicate any targeting strategy or customer persona.
Inference: The target audience is likely individuals or creators using Threads who value anonymity in feedback collection.
Claim vs Fact: This is an inferred ICP based on the stated use case; no explicit segmentation or customer data are provided.
Business Model & Pricing Evidence
There is no evidence of pricing, monetization strategy, or business model in the description. The author does not mention any paid features, subscriptions, or revenue streams.
Not evidenced: No indication of how the product would generate value or income.
Technical & Delivery Signals
The project was built using:
- Frontend: Next.js, React, TypeScript, Tailwind CSS
- Backend: Neon Postgres, Vercel Blob, Resend
- APIs: Threads API
- Tools: Codex with GPT-5.6 for code investigation and implementation planning
Key technical features include:
- Multi-step publishing reliability
- Recovery of interrupted jobs
- State management for publishing workflows
- Operational boundaries between production and preview environments
Inference: The product shows some engineering sophistication in handling complex publishing edge cases.
Claim vs Fact: These are claims about the tech stack and functionality — not validated or verified.
Traction & Maturity Signals
The author describes this as a hackathon project submitted to the OpenAI 2026 hackathon. There is no evidence of:
- Revenue
- Customers
- User adoption
- Product-market fit
- Prior versions or iterations
Not evidenced: No traction, usage metrics, or customer data are available.
Competitive Context
No mention of competitors or competitive landscape in the description. The author does not reference existing tools for anonymous Q&A or social publishing on Threads.
Not evidenced: No competitive analysis or market positioning is provided.
Open Questions & Risks
- Single-founder project: Only one team member (RAY Paw) is listed.
- No traction or revenue: The product is described as a hackathon submission with no evidence of adoption or monetization.
- Unverified claims: All features and functionality are self-reported without external validation.
- Limited scope: No indication of scalability, moderation tools, or long-term product vision beyond the initial implementation.
Inference: The lack of traction, team size, and business model raises questions about viability and future development.
Questions the description leaves open
- What is your plan for scaling beyond a single developer?
- Have you tested this with real users or gathered feedback from Threads users?
- How do you intend to monetize the platform if at all?
- What are the specific edge cases in publishing that remain unresolved?
- Are there any plans to expand beyond Threads or support other platforms?
Overall Assessment
Not evidenced: There is no evidence of revenue, customers, or traction to assess investment or partnership potential.
Confidence level: Low — based on self-reported claims only, with no external validation or data points.
Assessment: This is a concept-level product from a hackathon submission. No commercial due-diligence signal can be drawn without further evidence of adoption, revenue, or market traction.
User Stories BotA demo video on every pull request
Get a demo video on every new feature
GitHub App that watches your pull requests and records a narrated, captioned demo.
Save time on demo prep and make informed decisions faster with a video walkthrough of every new feature.
Source
Submitted to the OpenAI 2026 hackathon on Devpost. Project home on Devpost. Back to the full gallery on Devpost.
This competitive analysis was produced by
top-founders.com (opens in a new tab)
Generated by a language model from this project's public Devpost page — its tagline, the author's own write-up and any built-with tags listed there — as captured in August 2026. Short quotations are the author's words. It is an opinion on the idea as a business, not on the people behind it, and it reflects the description as published then. If the project has moved on, request a correction below. The analysis is not independent research and contains no verified traction, revenue or customer data.
An independent guide by KFG International LLC — not affiliated with, endorsed by, or connected to Devpost or OpenAI.