OpenAI 2026 hackathon

Sneeze

Step inside a sneeze: a source-linked 3D anatomy atlas built from aligned NIH models, with a deterministic six-stage journey, evidence confidence.

Solo project by Ozan Sozuoz · 2 likes · 0 comments

Archive position — measured, not model output

2 likes on Devpost

221 of the 7,856 archived projects have more likes, and 285 share exactly 2 — so this project's #470 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

Company: Sneeze

Tagline: Step inside a sneeze: a source-linked 3D anatomy atlas built from aligned NIH models, with a deterministic six-stage journey, evidence confidence.

Author's Claim: A 3D interactive experience of a sneeze, built for educational or exploratory purposes using open-source anatomical data and modern web technologies.

The description states that Sneeze is an interactive 3D anatomy experience focused on the mechanics of a sneeze, using NIH Human Reference Atlas models. It is described as a single-developer project built with React and WebGL-based libraries, submitted to a hackathon. No revenue, customers, or traction are evidenced.

What Changed: The author describes a personal curiosity-driven project that evolved into an interactive 3D visualization tool. There is no evidence of prior version, product evolution, or commercial activity beyond the hackathon submission.

Single Most Important Open Question: Is there any indication of commercial intent, user adoption, or monetization strategy beyond the initial prototype?

Back to contents

What The Product Actually Is

The description states that Sneeze is a source-linked 3D anatomy experience focused on a six-stage sneeze process, including:

  • Trigger
  • Neural signal
  • Inspiration
  • Compression
  • Release
  • Recovery

It allows users to:

  • Play a slowed 72-second sequence
  • Scrub through time
  • Jump between stages
  • Orbit the anatomy
  • Isolate body systems
  • Adjust skin opacity
  • Inspect source claims

The experience uses NIH Human Reference Atlas geometry for body surface, lungs, trachea, larynx, mouth, and eye. The description notes that neural signals, pressure, diaphragm motion, eyelid closure, and airflow are labeled as explanatory schematics, not "fake 'perfectly measured' animation."

Technology Stack: React, TypeScript, Vite, Three.js, React Three Fiber, Drei, Meshopt for model compression.

Inference: The product is a prototype or proof-of-concept, built in a hackathon context. It is not described as a commercial product or platform with ongoing development or user base.

Back to contents

Positioning & Claim Evolution

The author states that the project was inspired by a personal curiosity: “I sneezed and wondered how it worked.” The positioning is educational and exploratory, aiming to make the mechanics of a sneeze tangible through an interactive 3D experience.

There is no evidence of prior positioning or evolution in claims. The project is described as a single-developer hackathon submission with no indication of market research, branding, or strategic direction beyond its initial form.

Inference: The product is positioned as a curiosity-driven educational tool, not a commercial offering. It does not appear to have evolved from an earlier version or business model.

Back to contents

Target Customer & ICP

The description does not state any specific target customer or ideal customer profile (ICP). It is described as a personal curiosity project with no evidence of user personas, market segmentation, or audience targeting.

Inference: The product may appeal to:

  • Medical students
  • Educators
  • Curious individuals
  • Developers interested in 3D visualization

However, these are speculative inferences. No evidence supports any defined customer segment or commercial targeting.

Back to contents

Business Model & Pricing Evidence

There is no evidence of a business model or pricing strategy. The project is described as a hackathon submission, and no revenue streams, monetization plans, or pricing information are provided.

Inference: The product appears to be non-commercial at this stage. It is not evident whether the author intends to commercialize it or if it has any monetization plan.

Back to contents

Technical & Delivery Signals

The project is built with:

  • React
  • TypeScript
  • Vite
  • Three.js
  • React Three Fiber
  • Drei
  • Meshopt for model compression

It uses NIH Human Reference Atlas geometry and is described as a browser-based 3D experience, likely delivered via WebGL.

Inference: The technical stack suggests a modern, web-native approach to 3D visualization. The use of open-source anatomical models and compression techniques indicates attention to performance and accessibility.

Back to contents

Traction & Maturity Signals

The project is described as a single-developer hackathon submission, with no evidence of:

  • Revenue
  • Customers
  • User engagement
  • Product iteration
  • Market traction

The author states, “Not much, I already sneezed,” suggesting limited follow-up or development.

Inference: The product is at an early prototype stage, with no signs of maturity or traction. It is not evident that it has been used beyond its initial build.

Back to contents

Competitive Context

There is no evidence of competitors or market context in the description. No mention of similar tools, platforms, or products in the 3D anatomy or educational space is provided.

Inference: The project appears to be unique within its own scope, but there is no indication of a competitive landscape or prior market presence.

Back to contents

Key Risks & Red Flags

  • No commercial intent or traction — the product is described as a hackathon submission with no evidence of monetization or user adoption.
  • Single developer — limited capacity for scaling, iteration, or long-term development.
  • No business model — unclear how this would be monetized if at all.
  • Unproven market demand — no indication of target audience or use case beyond personal curiosity.

Back to contents

Diligence Questions To Ask The Founders

  1. What is the intended use case for Sneeze beyond a prototype?
  2. Are there any plans to expand beyond the sneeze model into other anatomical systems or processes?
  3. Is there any interest in partnering with educational institutions or medical organizations?
  4. How would you monetize this product if at all?
  5. What is the long-term vision for Sneeze, and how does it differ from existing 3D anatomy tools?

Back to contents

Investment/Partnership Verdict

Not evidenced — There is no evidence of commercial traction, revenue, or a clear path to monetization. The project is described as a single-developer hackathon submission, with no indication of a business model, target market, or user base.

Confidence Level: Low

Inference: This is a conceptual prototype with no demonstrated commercial viability or strategic direction. It may be an interesting curiosity but does not appear to be a viable investment or partnership opportunity at this stage.

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.