Hack Stack

Note: This analysis is based entirely on the self-reported project description provided. No external verification or historical data is available. All claims are unverified and should be treated as stated by the authors only.

• The description states that Hack Stack indexes codebases of hackathon projects submitted to Devpost.
• It uses AI agents (e.g., Codex) to explore repositories, verify claimed features from READMEs, and extract analytics.
• It aggregates data about technologies used, commit counts, lines added/deleted, and coding agents involved.
• It allows exporting indexed projects into a local coding agent for further exploration.
• The platform is built with Next.js, React, Supabase, Trigger.dev, Vercel, and other tools listed in the author-declared tech stack.

Inference: Based on the description, Hack Stack appears to be an indexing and analysis tool that bridges the gap between hackathon submission UIs (like Devpost) and actual code-level insights. It is not a platform for creating or hosting hackathons but rather a tool for analyzing them post-submission.

• The tagline “Devpost + GitHub + AI = Hack Stack” positions the product as an enhanced version of existing tools.
• The authors claim that current hackathon platforms like Devpost lack discovery and code-level insight, resulting in projects being lost or misrepresented.
• They assert that their solution addresses this gap by providing:
  • Feature verification
  • Analytics
  • Export functionality
  • Unified interface for browsing projects

Claim: Hack Stack fills a real gap in hackathon platforms.

Evidence: The description states the authors identified this issue while brainstorming and built a solution to address it.

• The primary target customer appears to be hackathon judges or organizers, who want to understand what’s actually in submitted projects.
• Secondary users may include hackers themselves, who might use the tool for idea discovery or project validation.
• The description does not name specific personas, but implies a need for deeper technical insight than current platforms offer.

Inference: Based on the write-up, the ICP likely includes judges and organizers of hackathons, particularly those using Devpost. There is no evidence of direct user feedback or customer segmentation beyond this.

• No pricing model, monetization strategy, or revenue streams are mentioned in the description.
• The authors state they plan to raise funding or sell to Devpost, suggesting a potential future business model.
• There is no indication of whether Hack Stack is currently available for public use or if it's limited to internal development.

Claim: There is no evidence of a current business model or pricing structure.

Evidence: Not evidenced.

• The platform uses AI agents (Codex) extensively, including for code generation and analysis.
• It leverages tools such as Supabase, Trigger.dev, Vercel, GitHub API, and others.
• The authors describe using branching strategies, CI/CD discipline, and manual migration reviews to maintain quality despite agentic development.
• They mention using Codex with specific skills like Browser Harness and Imagen for image generation.
• The system is designed to be scalable within compute constraints through approval gating and project caps.

Inference: The technical approach shows a blend of modern SaaS architecture (Next.js, Supabase) with agentic workflows. The authors emphasize safety practices despite rapid development via AI.

• The project was submitted to the OpenAI 2026 hackathon.
• It is described as built by two people (Mann Malviya and XY Lau).
• The authors claim they indexed a subset of recent hackathons, not all of Devpost.
• No mention of active users, usage metrics, or adoption beyond the team’s own development.

Claim: There is no evidence of traction or user engagement.

Evidence: Not evidenced.

• The description references Devpost as the main competitor or baseline platform.
• It implies that Devpost lacks discovery and code-level insight.
• No other competitors are named, nor is there any competitive analysis provided.

Inference: Hack Stack positions itself as an improvement over Devpost’s UI and functionality. However, no evidence of broader market positioning or competitive landscape exists in the description.

• The platform relies heavily on AI agents (Codex), which may be unreliable or expensive at scale.
• Compute constraints were a major challenge during development; this could limit scalability.
• No mention of data privacy, security, or compliance considerations for indexing third-party codebases.
• The project is described as built by only two people — raises questions about long-term maintainability and growth potential.
• There is no evidence of product-market fit beyond the authors’ own experience.

Red Flag: Heavy reliance on AI agents without clear scalability or cost control mechanisms.

Red Flag: Lack of traction, revenue, or customer base.

1. Is Hack Stack currently live and used by anyone outside the development team?
2. What is the current scope of indexing (e.g., how many hackathons are indexed)?
3. How does the platform handle data privacy for third-party repositories?
4. Are there any plans to monetize or commercialize the platform beyond raising investment or selling to Devpost?
5. What are the actual compute costs and limitations, and how do they impact scalability?
6. Have you received feedback from judges or organizers about the utility of the platform?