OpenAI 2026 hackathon

OceanEye - open-source interactive 3D atlas of ocean life

Built by one designer with no coding or 3D BG. AI wrote all the code, generated 3d models. Human provided judgment, taste, and content. Each ocean life detail was base on research and source-checked.

Solo project by Woody Li · 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 #5,634 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

What the company appears to be

OceanEye is a self-reported 3D interactive atlas of ocean life, built by one designer with no coding or 3D background. The author states that AI wrote all code and generated 3D models, while human judgment guided content, research, and editorial decisions. It is presented as an open-source project with a live site, e2e tests, dual licensing, and contributor tools.

What changed

The project evolved from a personal experiment into a meaningful product with scientific rigor, according to the author. It moved beyond a demo or prototype to become a structured, curated experience with source-checked content and technical delivery.

Single most important open question

Is there evidence of traction, revenue, or adoption beyond the author’s own account? The description does not include any data on users, engagement, monetization, or market validation.

Note: This analysis is based entirely on the self-reported, unverified project description provided by the author. No external sources, funding rounds, customer data, or performance metrics are available.

Back to contents

What The Product Actually Is

The description states that OceanEye is a 3D atlas of ocean life. Users can dive through five depth zones (from sunlight to hadal) and encounter ten creatures. Each creature has an interactive 3D model and curated insight cards with source links. The site ships pre-made JSON and compressed 3D models, not generated at runtime.

  • Product type: Interactive 3D educational web experience
  • Core features:
    • Five depth zones in ocean exploration
    • Ten interactive 3D creatures
    • Insight cards with source links
    • Pre-built 3D assets and JSON data (not AI-generated on demand)
  • Delivery method: Web-based, self-hosted, using WebGL and React

Inference: The product is a digital educational tool focused on ocean biodiversity. It uses AI for code generation and 3D modeling but emphasizes human curation of content.

Back to contents

Positioning & Claim Evolution

The author describes OceanEye as:

  • A "personal experiment" that evolved into a meaningful product
  • An open-source, contributor-driven 3D encyclopedia of ocean life
  • Inspired by the visual storytelling in Billie Eilish’s concert film
  • Designed to spark curiosity and promote ocean protection

Claim evolution:

  1. Initial claim: Could one person with no coding or 3D background build a full product?
  2. Evolution: The project became more than a demo — it became a curated, science-backed experience.
  3. Future positioning: A Wikipedia-like, open atlas of ocean life.

Claim vs Fact: These are self-reported claims about intent and evolution. No external validation or performance data is provided.

Back to contents

Target Customer & ICP

The description does not state who the target customer is or what their identity or needs are.

  • The author describes the project as educational and inspired by curiosity.
  • It is presented as a tool for learning about ocean life, possibly for students, educators, or nature enthusiasts.
  • No explicit segmentation or persona definition is given.

Not evidenced: No evidence of defined customer personas, use cases, or target markets beyond general interest in ocean biology.

Back to contents

Business Model & Pricing Evidence

The description does not include any information on:

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

It is described as open-source and contributor-driven, but no commercial model is outlined.

Not evidenced: No evidence of a business model or pricing structure.

Back to contents

Technical & Delivery Signals

The author reports the following technical stack:

  • Built with: Blender, Cloudflare Pages, Draco, Gemini, GLSL, glTF, GPT-5.6, Hyper3D Rodin, KTX2, OpenAI Codex, Playwright, React, React Three Fiber, Three.js, TypeScript, Vite, Vitest, WebGL
  • Pipeline includes:
    • Research and visual references
    • AI-generated prompts and models
    • Compression using Draco + KTX2
    • Camera setup and editorial review
  • The site is live with e2e tests, dual licensing, provenance docs, and issue templates

Inference: The project uses a hybrid human-AI workflow. It is technically complex but delivered in a self-hosted, open-source manner.

Back to contents

Traction & Maturity Signals

The description does not include:

  • User metrics or engagement data
  • Customer base or adoption numbers
  • Revenue or monetization
  • Product usage or retention signals

It is described as a personal project with no external validation or traction data.

Not evidenced: No evidence of traction, adoption, or maturity beyond the author’s own account.

Back to contents

Competitive Context

The description does not mention:

  • Competitors
  • Market positioning relative to others
  • Similar products in the space

It is presented as a unique, personal project without comparison to existing tools or platforms.

Not evidenced: No competitive landscape or market positioning data.

Back to contents

Key Risks & Red Flags

  1. Single-person operation: The entire project was built by one person (Woody Li), which raises questions about scalability and long-term maintenance.
  2. No revenue or monetization model: The project is described as open-source and contributor-driven, but no business model is evident.
  3. Unverified content quality: While the author claims source-checking, there is no independent verification of accuracy or editorial rigor.
  4. AI dependency risks: Heavy reliance on AI for code and 3D generation may introduce inconsistency or technical limitations.
  5. No external validation: The project has not been independently verified or tested by third parties.

Inference: Risks are primarily around scalability, sustainability, and lack of commercial traction.

Back to contents

Diligence Questions To Ask The Founders

  1. What is the long-term vision for OceanEye beyond its current scope?
  2. How do you plan to sustain the project if it remains a one-person effort?
  3. Are there any plans for monetization or revenue generation?
  4. How are you ensuring content accuracy and consistency across models?
  5. What is your strategy for community contribution and governance?
  6. Have you considered how to scale beyond the current 10 creatures and five zones?

Back to contents

Investment/Partnership Verdict

The project is described as a personal, experimental endeavor with strong technical execution but no evidence of traction, revenue, or commercial viability.

  • Confidence level: Low
  • Investment potential: Not evidenced. No data on market fit, scalability, or monetization.
  • Partnership opportunity: Not evident. The project is self-contained and not described as a platform or service for others to integrate with.

Conclusion: This is a self-reported, non-commercial project built by one individual. It lacks evidence of commercial traction or business model. It may be a valuable educational tool or artistic endeavor but does not appear to meet standard due-diligence criteria for investment or partnership.

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.