OpenAI 2026 hackathon

DearPage

DearPage is a digital scrapbook that takes you from idea to memory. You turn loose ideas into events, pictures, and memories. Link with a partner for a place to manage and track your activities.

Solo project by David Torrey · 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 #939 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

DearPage is a self-reported digital scrapbooking tool designed for individuals, couples, close friends, and families to capture and organize life experiences from idea to memory. It supports idea capture, event planning, letter writing, photo organization, and shared archives with a focus on emotional storytelling and relationship-based content sharing.

What changed

The author describes building the entire product using AI tools (Codex, GPT-5.6, Claude), with minimal manual coding. This approach is presented as novel in how it was used to define system architecture, design user experience, and guide iterative development — though no evidence of prior versions or prior use exists.

Single most important open question

Is there any evidence of actual usage, traction, or revenue beyond the author’s personal narrative? The description contains no data on users, adoption, monetization, or product-market fit.

Back to contents

What The Product Actually Is

The description states that DearPage is a private shared-life archive and planner. It allows users to:

  • Capture ideas (e.g., restaurants, concerts, destinations) as loose sparks without immediate scheduling.
  • Promote those ideas into events with calendar details like date, time, location, reminders.
  • Write letters for emotional storytelling, which can be linked to memories.
  • Organize photos dynamically through albums that group images by memory, date, person, place, or tag — without copying or moving them.
  • Create memories from past events, combining ideas, events, letters, and photos into evolving scrapbook pages.
  • Share content via links between people, with a distinction between private and public views.

It is described as working across desktop and mobile, including as a progressive web app. The system is said to connect all these elements into a narrative flow from inspiration to experience to remembrance.

Evidence

  • Author’s own write-up
  • Technology stack: codex, gitlab, gpt-5.6, kubernetes, node.js, postgresql, typescript

Inference The product appears to be built around the concept of a "digital scrapbook" that integrates planning, journaling, and photo management in a way that emphasizes emotional connection over functional utility.

Back to contents

Positioning & Claim Evolution

The author positions DearPage as:

  • A digital scrapbooking tool, but not just for photos — it's about capturing experiences from idea to memory.
  • An extension of the user’s own life experience, designed to be elegant and natural enough that technology fades into the background.
  • A tool for preserving relationships and shared histories through intentional communication and documentation.

It is framed as a solution to fragmentation in how people manage life stories — where ideas disappear into messages, plans live in calendars, and memories are scattered across platforms.

Evidence

  • The author's own write-up
  • Reference to Day One and Google Photos Live Albums as existing tools they did not find suitable

Inference The positioning is rooted in personal narrative rather than market research or competitive analysis. It reflects the author’s emotional journey and desire to reconnect with life, but does not indicate a broader commercial strategy or target segment beyond “individuals, couples, close friends.”

Back to contents

Target Customer & ICP

The description states that DearPage targets:

  • Individuals
  • Couples
  • Close friends
  • Eventually families

It also mentions that the tool works best when used in relationships — with others who are linked together. The shared nature of the experience is central to its design.

Evidence

  • Author’s own write-up

Inference There is no evidence of a defined ideal customer profile (ICP), segmentation strategy, or buyer persona beyond general categories like individuals and couples. No indication of whether this is a B2C or B2B offering, nor how the product would scale beyond one user.

Back to contents

Business Model & Pricing Evidence

The description does not mention any pricing model, monetization strategy, or business model. It only describes the features and functionality of the tool.

Evidence

  • Author’s own write-up
  • No mention of subscriptions, freemium tiers, or paid features

Inference There is no evidence that DearPage has a business model in place or even a plan for monetization. The focus is entirely on the product experience and emotional value.

Back to contents

Technical & Delivery Signals

The author reports:

  • Built nearly completely with AI tools (Codex, GPT 5.6, Claude)
  • Workflow involves brainstorming, designing, and developing in GPT, then verifying with Claude
  • Uses a full-stack developer role to define product, design system, establish boundaries, and guide AI through planning, implementation, testing, and refinement
  • Built using technologies such as Kubernetes, Node.js, PostgreSQL, TypeScript

Evidence

  • Author’s own write-up
  • Technology tags: codex, gitlab, gpt-5.6, kubernetes, node.js, postgresql, typescript

Inference While the use of AI tools is novel in this context, there is no evidence that the tool has been tested or deployed beyond the author’s own environment. No mention of scalability, performance, or production readiness.

Back to contents

Traction & Maturity Signals

There is no evidence of traction, revenue, customers, or adoption. The project is described as a personal endeavor built during a hackathon submission. It was submitted to the OpenAI 2026 hackathon on Devpost and has no archived history or independent verification.

Evidence

  • Author’s own write-up
  • Submission context: hackathon entry

Inference The lack of any traction signals suggests that this is a prototype or concept, not a mature product. No data points exist regarding user engagement, retention, or monetization.

Back to contents

Competitive Context

The author references:

  • Day One (private shared journals)
  • Google Photos Live Albums (automatic collection of photos)

They state they could not find a tool that combined the full progression from idea to memory in one platform.

Evidence

  • Author’s own write-up

Inference There is no evidence of competitive analysis beyond these two tools. No mention of competitors like Notion, Roam Research, or other life planning apps. The competitive landscape remains undefined.

Back to contents

Open Questions & Risks

  1. No traction or revenue: The product has no demonstrated adoption or monetization.
  2. Unverified claims: All descriptions are self-reported and unverified.
  3. AI-driven development without validation: While innovative, the heavy reliance on AI for development raises questions about quality control, scalability, and long-term maintainability.
  4. Lack of business model clarity: No indication of how the product will be monetized or scaled.
  5. Single-person team: The entire project was built by one person (David Torrey), which may limit execution capacity and risk concentration.

Evidence

  • Author’s own write-up
  • Team size: 1

Back to contents

Questions the description leaves open

  1. What specific problems are you solving for users, and how do you know?
  2. How did you validate the need for this product before building it?
  3. Are there any early adopters or beta testers? If so, what feedback have they given?
  4. What is your plan to scale beyond a single user or relationship?
  5. How do you intend to monetize the platform?
  6. What are the technical limitations of relying on AI for development?
  7. Have you considered how privacy and data ownership will be handled in shared spaces?

Back to contents

Overall Assessment

Not evidenced.

The project is described as a personal, hackathon submission with no evidence of traction, revenue, or business model. The author’s narrative is compelling but unverified, and there are no signs that the product has moved beyond concept or prototype stage.

Confidence level Low This analysis is based entirely on self-reported information, and the absence of any external validation or data makes it impossible to assess commercial viability or potential for growth.

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.