OpenAI 2026 hackathon

Auralis

Auralis turns an audiogram into a guided listening comparison, helping families hear how communication, distance and background sounds can affect everyday conversation.

Solo project by Ondrej Fiala · 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 #2,808 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: Auralis

Self-reported basis: The description is entirely self-reported by the author, unverified, and submitted as part of a hackathon project. No external validation or independent evidence is available.

What it appears to be: A prototype tool that uses AI to simulate how hearing loss affects everyday auditory experiences, designed for family members of people with hearing impairments.

What changed: The author states this was built during a hackathon and includes a plan for future expansion, but no commercial or product development has occurred beyond the prototype stage.

Single most important open question: Is there any evidence that Auralis has traction, revenue, or customer adoption — or even a clear path to monetization?

Back to contents

What The Product Actually Is

The description states that Auralis "turns an audiogram into a guided listening comparison", helping families understand how communication, distance, and background sounds affect everyday conversation. It is described as a tool that guides users through situations as heard by someone with healthy hearing versus the same situation from the perspective of someone with hearing loss.

  • The product is built using audio, codex, gpt-5.6, next.js, node.js, playwright, react, sol, terra, tts, typescript, vercel, web, zod.
  • It was developed in collaboration with ChatGPT and the Codex app, and the author claims to have built it during a hackathon.
  • The system is described as being designed specifically for family members of people with hearing loss.

Not evidenced: No information on whether the tool actually simulates or generates audio, how it uses audiograms, or whether it has been tested with users.

Back to contents

Positioning & Claim Evolution

The author states that Auralis is intended to help families understand the real problems faced by people with hearing loss. It is positioned as a tool for empathy-building, not as a clinical or commercial product.

  • The project grew from the author’s work in audiology.
  • The author claims to have built it during a hackathon, and that the scope was kept within boundaries.
  • Future plans include:
    • Scene generation through GPT Image 2.0
    • Use of GPT Realtime for transforming communication
    • Exploration of hearing aid brands and correction options

Inferred: The positioning is empathetic, not commercial. The author’s claims about future features are speculative and unproven.

Back to contents

Target Customer & ICP

The description states that the application is designed "specifically for family members" of people with hearing loss.

  • The target audience is family members, not end-users or clinicians.
  • The goal is to help them better imagine the difficulty their loved one is dealing with.

Not evidenced: No evidence of customer personas, user research, or actual engagement with target users. No indication of whether family members have been surveyed or tested the tool.

Back to contents

Business Model & Pricing Evidence

The description does not include any information about pricing, monetization, or a business model.

  • The author mentions future features such as hearing aid brand comparisons, but no commercial strategy is outlined.
  • No mention of subscriptions, licensing, or B2B vs. B2C models.

Not evidenced: No evidence of revenue streams, pricing plans, or monetization strategy.

Back to contents

Technical & Delivery Signals

The author states that the project was built using a variety of technologies including:

  • Audio processing
  • GPT-5.6 and Codex
  • Next.js, React, Node.js, Playwright
  • TTS (Text-to-Speech), Sol, Terra, Zod
  • The system was developed in collaboration with AI tools.
  • The author claims to have built the architecture from day one and completed it during a hackathon.

Inferred: The technical stack suggests a modern web-based prototype. However, no evidence of scalability, performance, or production readiness is provided.

Back to contents

Traction & Maturity Signals

The project was submitted as part of a hackathon, and the author states:

  • It was built on time.
  • It is genuinely working.
  • The scope was locked down.
  • The system is not yet production-ready.

Not evidenced: No evidence of user adoption, customer feedback, or product-market fit. No data on usage, retention, or engagement.

Back to contents

Competitive Context

The description does not mention any competitors or market context.

  • It is unclear whether similar tools exist in the market.
  • The author’s claims about future features (e.g., GPT Realtime, hearing aid integration) are speculative and unproven.

Not evidenced: No competitive analysis, no mention of existing solutions, no indication of market size or opportunity.

Back to contents

Key Risks & Red Flags

  • No commercial traction or revenue: The project is a prototype from a hackathon.
  • Unverified claims: All features and future plans are self-reported and unproven.
  • Single founder: The team size is listed as 1, which may limit execution capacity.
  • Lack of user testing: No evidence of real-world user feedback or clinical validation.
  • Speculative roadmap: Future features are not backed by any development or market data.

Inferred: The lack of commercialization and user engagement raises questions about viability and scalability.

Back to contents

Diligence Questions To Ask The Founders

  1. What is the actual use case for family members? Have you tested this with real families?
  2. How does Auralis translate audiograms into audio simulations?
  3. Are there any clinical or audiology partners involved in the development?
  4. What are the specific technical challenges that remain unresolved?
  5. Is there a plan to validate the empathy-building outcome with actual users?
  6. What would be the next step for monetization or product development?

Back to contents

Investment/Partnership Verdict

Not evidenced: No information on revenue, customers, traction, or commercial viability is provided.

  • The project is currently a hackathon prototype, not a product in the market.
  • It is not demonstrated to have any commercial potential at this stage.
  • The author’s claims about future features are speculative and unproven.

Verdict: Not ready for investment or partnership. Auralis shows potential as an idea, but lacks evidence of traction, user adoption, or a clear path to monetization.

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.