OpenAI 2026 hackathon

NotAlone

When life feels overwhelming, NotAlone builds an AI team around your needs and boundaries, then gives you one manageable next step. Feeling lost should never mean being left alone.

Solo project by Christian Quintino De Luca · 3 likes · 0 comments

Archive position — measured, not model output

3 likes on Devpost

128 of the 7,856 archived projects have more likes, and 93 share exactly 3 — so this project's #181 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

NotAlone is a self-reported AI-powered support system designed to provide personalized, boundary-aware assistance during difficult life moments. The project was built as part of an OpenAI hackathon and is described as a Flutter + FastAPI application with backend powered by GPT-5.6, Codex, and other open-source tools.

What changed

The author states that the project emerged from personal inspiration around helping people not feel alone during overwhelming times. It introduces concepts like “Human Agency Contract,” “Next Kindest Step,” and “Living Plan adaptation” to tailor AI support to individual needs and consent.

Single most important open question — the commercial due-diligence read

Is there any evidence of real-world usage, user feedback, or product-market fit beyond the hackathon demo? The self-reported description lacks any indication of traction, revenue, customers, or adoption.

Back to contents

What The Product Actually Is

The description states that NotAlone is an AI-powered support system built with Flutter and FastAPI. It uses GPT-5.6, Codex, and other tools to help users navigate difficult life situations by:

  • Listening to the user describe their situation naturally.
  • Building a “Human Agency Contract” that understands capacity, preferred support style, consent, and privacy boundaries.
  • Creating a small team of specialized AI agents tailored to the specific problem.
  • Delivering one manageable next step — the “Next Kindest Step.”
  • Adapting the plan if the user says “This is too much.”

It also claims to show execution traces and fallback behavior for transparency.

Evidence

  • The author describes how it works in detail.
  • It includes technical stack: Flutter, FastAPI, Python, Pydantic, GPT-5.6, Codex, Groq, OpenAI models.
  • The project was submitted to the OpenAI 2026 hackathon.

Inference The product is described as a prototype or proof-of-concept built for a hackathon; no evidence of production deployment or real-world usage exists in the description.

Back to contents

Positioning & Claim Evolution

The author positions NotAlone as a tool that helps people not feel alone during difficult times, emphasizing empathy and human agency over automation. Key claims include:

  • “Feeling lost should never mean being left alone.”
  • “Not to replace people. To help people be there.”
  • “Doing good travels in both directions.”
  • “One step. Then another. But not alone.”

The project evolved from a personal idea into a system that uses AI agents to deliver small, manageable actions based on user-defined boundaries.

Evidence

  • The inspiration and narrative are self-reported.
  • The author describes the evolution of the product through the hackathon process.

Inference This is a strong positioning statement rooted in emotional resonance rather than data or market validation. It reflects an intent to build a compassionate, boundary-aware AI assistant — not a commercial product yet.

Back to contents

Target Customer & ICP

The description does not clearly define a target customer segment or ideal customer profile (ICP). However, it implies that the intended users are individuals who feel overwhelmed or lost in life situations such as:

  • Being stranded abroad
  • Losing documents
  • Facing family problems
  • Feeling emotionally overwhelmed
  • Not knowing where to begin

It also suggests that the user must be able to articulate their situation and consent to AI involvement.

Evidence

  • The author describes various scenarios where users might seek help.
  • It mentions “Human Agency Contract” and “consent and privacy boundaries.”

Inference The ICP is implied to be emotionally vulnerable individuals seeking support, but no explicit segmentation or targeting strategy is described. No user personas, demographics, or behavioral patterns are provided.

Back to contents

Business Model & Pricing Evidence

There is no evidence of a business model or pricing structure in the description. The project is presented as a hackathon submission with no mention of monetization, subscriptions, licensing, or paid features.

Evidence

  • The author does not describe any revenue streams.
  • No pricing information, plans, or monetization strategies are included.

Inference The product appears to be in early-stage development and likely not yet commercialized. It may eventually evolve into a freemium or subscription model, but no such indication exists currently.

Back to contents

Technical & Delivery Signals

The project is built using:

  • Frontend: Flutter
  • Backend: FastAPI, Python, Pydantic
  • AI Tools: GPT-5.6, Codex, Groq, OpenAI/gpt-oss-120b
  • Deployment: Vercel

It includes features like:

  • Dynamic agent runtime
  • Execution traces and fallback behavior
  • Transparent attribution of AI providers
  • Human-in-the-loop design decisions (e.g., name, boundaries, consent model)

Evidence

  • The author lists the tech stack.
  • Describes implementation details such as testing, widget analysis, and deployment.

Inference The technical architecture is functional for a prototype but lacks evidence of scalability or production readiness. The use of open-source tools and traceable AI models suggests transparency, but no performance metrics or infrastructure details are shared.

Back to contents

Traction & Maturity Signals

There is no evidence of traction, revenue, customer adoption, or product maturity beyond the hackathon demo. The project is described as a working public application built during Build Week, with no indication of ongoing usage or user feedback.

Evidence

  • The live demo and source code are linked.
  • Accomplishments list includes a working app and backend tests.
  • No mention of users, retention, engagement, or growth metrics.

Inference This is a pre-product stage prototype. It has not demonstrated real-world usage or market traction.

Back to contents

Competitive Context

The description does not provide any information about competitors or the competitive landscape. The author does not reference existing solutions in mental health support, AI companions, or crisis response tools.

Evidence

  • No competitor analysis or market positioning is mentioned.
  • No mention of similar products or services.

Inference Without knowing the competitive space, it's impossible to assess whether NotAlone addresses a unique need or overlaps with existing offerings. This is an open field for innovation, but also a high-risk area without clear differentiation.

Back to contents

Key Risks & Red Flags

Several risks and red flags are evident from the self-reported description:

  • No traction or user feedback: The project has not been tested in real-world conditions.
  • Unproven commercial viability: No business model or monetization strategy is described.
  • High emotional risk without safety mechanisms: The product deals with vulnerable users; no evidence of ethical safeguards or liability frameworks.
  • Unclear scalability: Built for a hackathon, not production-ready.
  • Over-reliance on AI tools: Uses GPT-5.6 and other models without indicating control over outputs or risks.
  • Lack of transparency in AI behavior: While it claims to show execution traces, no details are given about how this is implemented or audited.

Evidence

  • The author acknowledges the challenge of teaching the product when to do less.
  • No mention of safety, ethics, or regulatory compliance.

Inference This is a conceptually promising idea but lacks any evidence of real-world testing, ethical governance, or commercial viability. It could be risky if scaled without proper safeguards.

Back to contents

Diligence Questions To Ask The Founders

  1. What specific user feedback have you gathered from people who tried the demo?
  2. How do you ensure that AI-generated actions are safe and appropriate for emotionally vulnerable users?
  3. Are there any plans to integrate with mental health professionals or crisis hotlines?
  4. What would be your go-to-market strategy if you were to commercialize this product?
  5. Have you considered how to handle edge cases where the AI fails to understand a user’s needs?
  6. How do you plan to scale beyond the current prototype without compromising user safety and trust?

Back to contents

Investment/Partnership Verdict

Not evidenced.

The description provides no information about financials, funding rounds, headcount, or any commercial activity beyond the hackathon submission. It is unclear whether this represents a viable business opportunity or just an idea with emotional resonance.

Confidence level Low This is a self-reported, unverified account of a hackathon project with no evidence of traction, revenue, customers, or even basic product-market fit.

Next steps

If pursuing further diligence, one would need to validate the concept through user testing, assess the team’s ability to scale, and evaluate potential market demand for such a service.

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.