Archive position — measured, not model output
0 likes on Devpost
2,264 of the 7,856 archived projects have more likes, and 5,592 share exactly 0 — so this project's #2,822 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
The company appears to be a solo project, Autodeck, which self-reports as an agentic deckbuilding tool for Magic: The Gathering. It is described as a Commander deckbuilding workspace where a player and GPT-5.6 collaborate on research, analysis, validation, and editing of decks. The author states that the tool uses Codex, Magic: The Gathering, Scryfall, and TanStack technologies.
There is no evidence of revenue, customers, or traction beyond the project's submission to a hackathon. The team size is listed as one. The description does not contain information about pricing, business model, or competitive positioning. The single most important open question is whether this tool has any real-world utility or adoption beyond its hackathon prototype.
Confidence: Low. This analysis is based entirely on self-reported information from a hackathon submission with no independent verification. No evidence of commercial traction, revenue, or customer data exists.
What The Product Actually Is
The description states that Autodeck is an agentic deckbuilding tool for Magic: The Gathering, specifically for Commander format. It is described as a workspace where the player and GPT-5.6 collaborate on research, analysis, validation, and editing of decks.
Inference The product appears to be a digital interface or application that integrates AI (specifically GPT-5.6) into the process of building and refining Magic: The Gathering decks.
Evidence The project write-up states: > "What it does: Agentic Deckbuilding tool for Magic: The Gathering"
The author also mentions:
"Built with (author-declared): codex, magicthegathering, scryfall, tanstack"
This suggests the product uses APIs or data from Scryfall and integrates with Magic: The Gathering card databases.
Not evidenced No information on how the tool functions beyond the collaboration between user and AI. No UI details, no specific features, no technical architecture are described.
Positioning & Claim Evolution
The description states that Autodeck is an agentic Commander deckbuilding workspace, where a player and GPT-5.6 work together to research, analyze, validate, and edit decks.
Claim
The tool positions itself as an AI-assisted workspace for Magic: The Gathering players, particularly in the Commander format.
Inference The positioning implies that it is intended to help users build better decks by leveraging AI for analysis and validation.
Not evidenced No evidence of prior versions or claim evolution. The project is described as a hackathon submission with no indication of how it evolved from an idea to this version.
Target Customer & ICP
The description states that Autodeck is for Magic: The Gathering players, particularly those who play Commander format.
Inference The target customer is likely a niche audience — Magic: The Gathering enthusiasts, especially those interested in the Commander variant of the game.
Not evidenced No information on:
- Specific user personas
- Demographics
- Customer segmentation
- ICP (Ideal Customer Profile) details
Business Model & Pricing Evidence
The description does not contain any information about a business model or pricing.
Not evidenced No evidence of:
- Revenue streams
- Pricing structure
- Monetization strategy
- Subscription or one-time purchase models
Technical & Delivery Signals
The author states that the tool was built using:
- Codex
- Magic: The Gathering
- Scryfall
- TanStack
Inference These technologies suggest a web-based application with API integration, likely using React (via TanStack) and data from Scryfall’s card database.
Not evidenced
- No information on architecture or scalability
- No evidence of delivery mechanism (e.g., web app, desktop, mobile)
- No mention of backend systems or infrastructure
Traction & Maturity Signals
The project is described as a hackathon submission, and the author states:
"Just iterate on what I have now."
Inference The product is in an early stage, likely a prototype or MVP.
Not evidenced
- No evidence of users or adoption
- No evidence of revenue or monetization
- No evidence of customer feedback or iteration history
- No evidence of product maturity beyond the hackathon submission
Competitive Context
The description does not provide any information about competitive landscape or existing solutions in the Magic: The Gathering deckbuilding space.
Not evidenced
- No mention of competitors
- No comparison to existing tools
- No indication of market positioning relative to others
Key Risks & Red Flags
Risk 1
Single-person team. The project is described as a solo effort, which may limit development speed and scalability.
Risk 2
Unverified AI integration. The description mentions GPT-5.6, but no details on how it's implemented or whether it’s actually functional.
Risk 3
Lack of traction or commercial viability. The project is described as a hackathon submission with no evidence of real-world use or monetization.
Risk 4
Unclear technical implementation. No information on how the tool functions beyond UI design and API usage.
Diligence Questions To Ask The Founders
- What specific problems in Commander deckbuilding does this tool solve that existing tools don’t?
- How is the AI integration implemented? Is it a chat interface, or something else?
- What are the technical limitations you've encountered with GPT-5.6 and rate limiting?
- Have you tested the tool with actual Magic: The Gathering players?
- What is your plan for monetization or scaling beyond the hackathon prototype?
Investment/Partnership Verdict
Verdict Not evidenced.
The project description does not provide sufficient evidence to assess investment or partnership potential. It is a solo hackathon submission with no commercial traction, revenue, or customer data. The tool’s functionality and viability remain unproven.
Inference At this stage, the project appears to be an early prototype with no clear path to commercialization or scalability. Any investment or partnership would require further development and evidence of real-world utility.
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.