OpenAI 2026 hackathon

Shapeships

Shapeships is a strategy board game where shared dice become lines, lines become ships, and ships grow into strange, powerful fleets.

Solo project by Judd Madden · 0 likes · 0 comments

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 #6,651 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

The company appears to be a solo indie developer project named Shapeships, a digital strategy board game built using AI-assisted development tools like Codex and GPT. The description states it began as a paper-based dice game, evolved into a browser-based strategy game with simultaneous turns, and uses a server-authoritative architecture. It supports private online matches and solo play against bots, and is designed for desktop and mobile browsers.

What changed: The author transitioned from a physical pen-and-paper game to a digital version using modern web technologies (React, TypeScript, Supabase) and AI development tools. The project was submitted to the OpenAI 2026 hackathon.

The single most important open question: Is there evidence of any traction, revenue, or user adoption beyond the author's own playtesting and development? The description contains no data on users, monetization, or market validation.

Analysis basis: This report is based entirely on the self-reported, unverified account provided by the author in the project description. No third-party verification, archived data, or independent sources are available. All claims are stated by the author and not independently confirmed.

Back to contents

What The Product Actually Is

The description states that Shapeships is a strategy board game where players use shared dice to create lines, which become ships, and those ships grow into fleets with unique powers. Players secretly commit builds from shared resources, reveal simultaneously, and adapt as their fleets evolve.

It supports:

  • Private online matches
  • Solo play against bots (described as "pretty decent")
  • Desktop and mobile browser play

The game uses a server-authoritative architecture, where the browser handles interaction and previews, while the server validates and resolves gameplay. The frontend is built with React, TypeScript, Vite, and Tailwind CSS; the backend uses Supabase Edge Functions, Deno, and Hono.

Inference: The product is described as a digital version of an existing pen-and-paper game, suggesting it's a re-imagining rather than a completely new concept.

Back to contents

Positioning & Claim Evolution

The author describes Shapeships as:

  • A strategy board game with simultaneous turns
  • A digital adaptation of a paper-based dice game
  • A game that supports private online matches and solo play
  • A game with deep meta, including openings, counter-builds, and debates about ship balance

The positioning appears to be:

  • A browser-based strategy game for casual and competitive players
  • A digital reimagining of a tabletop experience
  • A game with potential for community growth and competitive play

Claim vs. Fact: The description states the author's intent and vision, but does not provide evidence of market positioning or user reception.

Back to contents

Target Customer & ICP

The description states that Shapeships supports:

  • Private online matches (suggesting a social or multiplayer audience)
  • Solo play against bots (indicating single-player appeal)

It is designed for desktop and mobile browsers, suggesting a broad but potentially niche audience of strategy game enthusiasts.

Inference: The target customer likely includes:

  • Strategy board game fans
  • Casual and competitive online players
  • Users interested in browser-based games with deep mechanics

Not evidenced: No specific customer segments, personas, or user data are provided.

Back to contents

Business Model & Pricing Evidence

The description does not state anything about:

  • Revenue streams
  • Pricing models
  • Monetization strategy
  • Paid features or subscriptions

It only mentions that the game supports private online matches and solo play against bots, but no indication of how users pay or if there are any paid elements.

Not evidenced: No business model or pricing evidence is provided.

Back to contents

Technical & Delivery Signals

The project was built using:

  • Frontend: React, TypeScript, Vite, Tailwind CSS
  • Backend: Supabase Edge Functions, Deno, Hono
  • Development tools: GPT and Codex (AI-assisted development)

Key technical details include:

  • Server-authoritative architecture
  • Lightweight polling for game state updates
  • Separation of chat, match history, and live payload
  • Use of AI as a "director-level assistant" and "live code editor"

Inference: The use of modern web stack and AI tools suggests a developer-focused approach with attention to scalability and development workflow.

Back to contents

Traction & Maturity Signals

The description states:

  • The game was submitted to the OpenAI 2026 hackathon
  • The author did all game design, visual direction, architecture, playtesting, balance, and final review
  • It supports private online matches and solo play against bots
  • The author mentions balance testing, onboarding improvements, and computer opponent development as next steps

Not evidenced: No data on user numbers, retention, engagement, or revenue is provided. No evidence of a user base or monetization.

Back to contents

Competitive Context

The description does not mention:

  • Direct competitors
  • Market positioning relative to other strategy games
  • Similar products in the browser-based strategy game space

Not evidenced: No competitive analysis or market context is provided.

Back to contents

Key Risks & Red Flags

Key risks and red flags based on the self-reported information:

  • Solo developer project: The team size is listed as 1, which may limit scalability and long-term maintenance
  • No traction or monetization evidence: No data on users, revenue, or adoption
  • AI-assisted development: While efficient, it introduces risks of scope creep and lack of clear ownership if not well-managed
  • Limited market validation: The project is described as a personal endeavor with no external user feedback or community growth

Inference: The lack of evidence for traction or monetization raises questions about viability as a commercial product.

Back to contents

Diligence Questions To Ask The Founders

  1. What is the current stage of development, and how many hours have been invested?
  2. Have you playedtest with others beyond yourself? How many people have tried it?
  3. Are there any plans to monetize or generate revenue from the game?
  4. What are your long-term goals for Shapeships — community building, competitive scene, or commercial success?
  5. How do you plan to scale beyond solo development?

Back to contents

Investment/Partnership Verdict

The description provides no evidence of traction, revenue, or user adoption. It is a self-reported account of a solo developer’s project submitted to a hackathon.

Verdict: Not evidenced as a viable commercial opportunity without further data on users, monetization, or market demand.

Confidence level: Low — based entirely on the author's own description, with no external validation or performance metrics.

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.