OpenAI 2026 hackathon

Dremads

Dremads helps organizations create, verify, and reward meaningful audience engagement through intelligent campaign workflows powered by AI.

Solo project by Paul Haykeens · 1 likes · 0 comments

View the project on Devpost

Archive position — measured, not model output

1 like on Devpost

505 of the 7,850 archived projects have more likes, and 1,758 share exactly 1 — so this project's #979 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,587
11,758
2284
3–4132
5–975
10+14

Likes on Devpost. ▲ marks this project's group.

Show the figures
LikesProjectsShare of archive
05,58771.2%
11,75822.4%
22843.6%
3–41321.7%
5–9751.0%
10+140.2%
Devpost like counts for all 7,850 archived projects, captured when this archive was built.

User Stories BotA demo video on every pull request

Get a demo video on every new feature

GitHub App that watches your pull requests and records a narrated, captioned demo.
Save time on demo prep and make informed decisions faster with a video walkthrough of every new feature.

Executive Summary

What the company appears to be

Dremads is a self-reported AI-powered engagement platform designed to help organizations create, verify, and reward meaningful audience participation through campaign workflows. It supports three user roles: advertisers, administrators, and participants. The platform currently verifies engagement via quizzes before issuing rewards.

What changed

The project was submitted as a hackathon entry (OpenAI 2026) and evolved from a prototype into a deployed production application. It includes role-based authentication, campaign moderation, wallet integration, fraud prevention, and secure backend APIs.

Single most important open question

Is there any evidence of actual customer adoption or revenue generation beyond the author's self-reported MVP?

Back to contents

What The Product Actually Is

The description states that Dremads is an AI-powered engagement platform enabling organizations to create, manage, verify, and reward audience engagement. It supports three user roles:

  • Advertisers, who fund campaigns.
  • Administrators, who moderate and approve campaigns.
  • Participants, who complete engagement activities and earn rewards.

Engagement verification occurs through interactive quizzes before rewards are issued. The platform includes:

  • Role-based authentication
  • Campaign moderation workflows
  • Wallet and reward management
  • Fraud prevention and duplicate reward protection
  • Secure backend APIs

The system is built using modern full-stack technologies including Next.js, React, NestJS, Prisma ORM, PostgreSQL, Vercel, Railway, and AI tools like Codex and GPT-5.6.

Evidence

  • The author describes the platform's functionality in detail.
  • Technology stack is listed explicitly.

Inference

  • The platform appears to be a web-based SaaS-style tool with campaign lifecycle management features.

Back to contents

Positioning & Claim Evolution

The description states that Dremads aims to move beyond "vanity metrics" such as impressions or clicks, focusing instead on rewarding meaningful participation. It positions itself as a solution for advertisers seeking confidence in campaign outcomes while providing transparent incentives for participants.

It also claims to use AI throughout development and product design decisions, including architecture refinement, debugging, documentation, and engineering challenges.

Evidence

  • The author explicitly states the platform’s intent to reward verified engagement.
  • Claims about AI usage during development are made.

Inference

  • This is a positioning shift from traditional digital advertising metrics toward more authentic audience interaction.
  • The use of AI tools suggests an emphasis on automation and intelligent workflow design.

Back to contents

Target Customer & ICP

The description identifies three main user types:

  1. Advertisers: fund campaigns.
  2. Administrators: review, moderate, approve, activate campaigns.
  3. Participants: discover campaigns, complete activities, earn rewards.

No explicit segmentation or targeting of specific industries or organization sizes is mentioned.

Evidence

  • The roles are clearly defined in the write-up.

Inference

  • The platform targets organizations running engagement campaigns (e.g., brands, publishers, marketers).
  • It may appeal to those looking for more control over campaign outcomes and fraud detection.

Back to contents

Business Model & Pricing Evidence

There is no mention of pricing models, monetization strategies, or revenue streams in the description. The author does not describe how advertisers pay, what rewards cost, or whether there are tiered plans.

Evidence

  • No information on business model or pricing.

Inference

  • Likely a SaaS-style platform with potential subscription or transaction-based models.
  • Absence of pricing data is notable in a commercial context.

Back to contents

Technical & Delivery Signals

The platform was built as a full-stack web application using:

  • Frontend: Next.js, React, TypeScript
  • Backend: NestJS, Prisma ORM, PostgreSQL
  • Deployment: Vercel, Railway
  • AI tools used: Codex, GPT-5.6

It includes secure authentication, production deployment, database migrations, and API integration.

Evidence

  • Technology stack is listed.
  • Development process mentions use of AI-assisted tools.
  • Deployment details are provided.

Inference

  • The platform shows technical maturity for a hackathon MVP.
  • Use of AI tools suggests an experimental or rapid-development approach.

Back to contents

Traction & Maturity Signals

The description indicates that Dremads evolved from a prototype to a production-ready application. It includes:

  • Successful deployment
  • Role-based authentication
  • End-to-end campaign workflow
  • Verified engagement before reward issuance
  • Wallet integration
  • Duplicate reward prevention
  • Production-ready database

However, there is no evidence of actual users, customers, or revenue.

Evidence

  • MVP status confirmed.
  • Deployment and feature completion noted.

Inference

  • Platform has reached a functional state but lacks real-world usage data.
  • No traction signals (e.g., active users, signups, retention) are evident.

Back to contents

Competitive Context

No mention of competitors or market positioning beyond the general idea of engagement platforms. The author does not reference similar tools or services in the space.

Evidence

  • No competitive analysis or references to existing solutions.

Inference

  • Likely operates in a niche within digital advertising or engagement marketing.
  • Lack of competitive context is unusual for commercial due diligence.

Back to contents

Open Questions & Risks

  1. No revenue or customer data: The platform exists only as described by the author, with no evidence of traction or monetization.
  2. Unverified claims: All features and capabilities are self-reported without external validation.
  3. Limited team size: Only one member (Paul Haykeens) is listed, raising questions about scalability and execution capacity.
  4. AI dependency: Heavy reliance on AI tools raises concerns about reproducibility and long-term maintainability.
  5. Lack of pricing or monetization strategy: No indication of how the platform will generate revenue.

Evidence

  • No revenue data, customer base, or monetization model.
  • Team size is stated as one person.

Inference

  • High risk of misalignment between stated goals and actual commercial viability.
  • Lack of independent verification increases uncertainty.

Back to contents

Questions the description leaves open

  1. What specific use cases have you identified for advertisers or organizations?
  2. How do you plan to scale beyond the current MVP?
  3. Are there any early adopters or pilot customers using the platform?
  4. What is your go-to-market strategy and how will you acquire users?
  5. How do you intend to monetize this platform?
  6. What are the key technical challenges that remain unresolved in production?
  7. Can you provide evidence of user feedback or product iteration cycles?
  8. How does Dremads differentiate from other engagement or reward platforms?

Back to contents

Overall Assessment

Not evidenced.

The description provides no data on revenue, customers, traction, or financial performance. It describes a functional MVP built by one individual using AI-assisted development tools, but offers no commercial evidence of viability or demand.

Confidence level Low This is a self-reported, unverified account of a hackathon project with no external validation or proof of adoption or monetization.

Back to contents

User Stories BotA demo video on every pull request

Get a demo video on every new feature

GitHub App that watches your pull requests and records a narrated, captioned demo.
Save time on demo prep and make informed decisions faster with a video walkthrough of every new feature.

Source

Submitted to the OpenAI 2026 hackathon on Devpost. Project home on Devpost. Back to the full gallery on Devpost.

This competitive analysis was produced by top-founders.com (opens in a new tab)

Generated by a language model from this project's public Devpost page — its tagline, the author's own write-up and any built-with tags listed there — as captured in August 2026. Short quotations are the author's words. It is an opinion on the idea as a business, not on the people behind it, and it reflects the description as published then. If the project has moved on, request a correction below. The analysis is not independent research and contains no verified traction, revenue or customer data.

An independent guide by KFG International LLC — not affiliated with, endorsed by, or connected to Devpost or OpenAI.

Are you the author of this project? Request removal or a correction (support@kfginternational.com). Requests from authors are acted on within 48 hours, and in any case within seven days. Privacy notice.