OpenAI 2026 hackathon

Anastasis — Your app died. Your data didn't.

Your app died. Your data didn't. Anastasis watches a 2-min screen recording, reads your export, and Codex rebuilds the app you actually used, with data migrated, live on a URL you own.

Team of 2 · 0 likes · 0 comments

View the project on Devpost

Archive position — measured, not model output

0 likes on Devpost

2,263 of the 7,850 archived projects have more likes, and 5,587 share exactly 0 — so this project's #2,645 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

Anastasis is a self-reported tool that claims to resurrect dead or overpriced web apps using AI. The authors describe it as a system that takes a 2-minute screen recording and an export ZIP file, then uses GPT-5.6 vision and Codex to rebuild the app with data migrated, live on a URL owned by the user.

What changed

The project is presented as a hackathon submission (Devpost entry for OpenAI 2026). No prior version or commercial product is evidenced. The authors describe it as a proof-of-concept that works end-to-end in production, including AI-driven app rebuilding, verification gates, and deployment.

Single most important open question

Is there any evidence of real-world usage, customer feedback, or traction beyond the hackathon demo? The description states no revenue, customers, or adoption data exist beyond the authors' own claims.

Back to contents

What The Product Actually Is

The description states that Anastasis watches a 2-minute screen recording and reads an export ZIP file to rebuild a web app using AI. It uses GPT-5.6 vision for observation, Codex for code generation, and Kubernetes-based infrastructure for deployment.

Inference This is a tool that attempts to reverse-engineer a web application from user behavior (video) and data exports, then rebuilds it with the same functionality and data, but under the user’s control.

Evidence

  • “Anastasis watches a 2-min screen recording, reads your export, and Codex rebuilds the app you actually used”
  • “GPT-5.6 vision watches frame batches from the recording and writes exhaustive observation notes”
  • “Codex (gpt-5.6-sol) generates the entire app from scratch — schema, migration, API routes, UI”

Not evidenced

  • No actual product or live URL is provided.
  • No real-world use cases or customer data are described.

Back to contents

Positioning & Claim Evolution

The authors state that Anastasis addresses two core problems:

  1. Apps shutting down (e.g., due to acquisition)
  2. Overpriced tools where users only use 20% of features

They claim the tool flips the control dynamic — “what if your workflow could never be taken away from you again?”

Inference The positioning is that of a data-portability and user-control solution, aimed at empowering users to retain ownership over their workflows and data.

Evidence

  • “Every one of us has lost an app we loved. A company gets acquired, a service shuts down, and you're left holding a ZIP file of your own data useless without the app that made it meaningful.”
  • “We wanted to flip that: what if your workflow could never be taken away from you again?”

Not evidenced

  • No mention of competitors or market positioning beyond self-description.
  • No evidence of prior product iteration or evolution.

Back to contents

Target Customer & ICP

The description implies the target is users who have lost access to apps they depend on, or those who feel overcharged for software they don’t fully use.

Inference The ideal customer is someone with a valuable but dead or expensive app, who wants to regain control of their data and workflow.

Evidence

  • “Every one of us has lost an app we loved.”
  • “The tool that charges $30/month while you use 20% of its features.”

Not evidenced

  • No stated customer segments, personas, or buyer journeys.
  • No evidence of market research or early adopter feedback.

Back to contents

Business Model & Pricing Evidence

No pricing model or monetization strategy is described. The authors do not state whether the tool will be free, subscription-based, or offered as a service.

Inference The business model is unclear and likely under development, if at all.

Evidence

  • No mention of pricing, subscriptions, or monetization.
  • The tool is presented as a hackathon demo with no commercial intent stated.

Not evidenced

  • No revenue streams, pricing tiers, or customer acquisition costs.

Back to contents

Technical & Delivery Signals

The authors describe a complex technical stack including GPT-5.6 vision, Codex, Kubernetes (k3s), Docker, Next.js, and Cloudflare. They also detail challenges such as OOM issues, sandboxing, and ephemeral pod handling.

Inference The project is technically ambitious, with a focus on AI-driven code generation and deployment automation.

Evidence

  • “GPT-5.6 vision watches frame batches from the recording and writes exhaustive observation notes”
  • “Codex (gpt-5.6-sol) generates the entire app from scratch”
  • “Production infra: a 2-node k3s cluster across two VPSes, in-cluster registry, Kaniko image builds per resurrection”

Not evidenced

  • No evidence of scalability or production stability beyond demo.
  • No mention of performance benchmarks or infrastructure costs.

Back to contents

Traction & Maturity Signals

The project is described as a hackathon submission and is presented as a working end-to-end demo. The authors claim to have built a complete, live, verified app with 412 records migrated.

Inference This is a proof-of-concept, not a commercial product or market-ready solution.

Evidence

  • “A complete, live, end-to-end resurrection in production”
  • “Browser upload → AI pipeline → interactive clarification → verified build → containerized → deployed”

Not evidenced

  • No customer base, usage metrics, or adoption data.
  • No evidence of product iteration or feedback loops beyond the demo.

Back to contents

Competitive Context

No mention of existing competitors or market players is provided. The authors do not reference similar tools or platforms in the space of app resurrection or data portability.

Inference The competitive landscape is unknown and likely unexplored in this description.

Evidence

  • No references to similar products, services, or platforms.
  • No mention of existing solutions for data portability or app migration.

Not evidenced

  • No competitive analysis or positioning against other tools.

Back to contents

Open Questions & Risks

Several technical and commercial risks are implied in the description:

  1. AI Reliability: The system depends heavily on AI for code generation, which may fail or misinterpret data.
  2. Scalability: The demo is built on a 2-node k3s cluster; no evidence of scaling beyond that.
  3. User Dependency: The system requires user input during ambiguous cases, which may slow adoption.
  4. Lack of Traction: No evidence of real-world usage or customer feedback.

Inference The tool is experimental and not yet proven in a commercial context.

Evidence

  • “When the AI hits genuine ambiguity… it pauses mid-build and asks you instead of silently guessing.”
  • “This project fought back, and every fix came from a real failed run.”

Not evidenced

  • No evidence of user feedback or product-market fit.
  • No indication of long-term viability or scalability.

Back to contents

Questions the description leaves open

  1. What is the actual data loss scenario you're solving for? Is this a niche use case or broader market need?
  2. How does the system handle ambiguous or conflicting data between the video and export?
  3. Have you tested with real-world apps, or is it limited to demo cases?
  4. Are there any legal or compliance issues around rebuilding apps that may be proprietary or copyrighted?
  5. What are your plans for monetization or product development beyond this hackathon project?

Back to contents

Overall Assessment

Not evidenced.

The description does not provide sufficient evidence of traction, revenue, customer adoption, or a clear path to commercialization. It is a self-reported hackathon demo with no verified commercial activity.

Inference This is an early-stage idea with technical ambition but no demonstrated market readiness or business model. It may be worth exploring further if the founders can demonstrate real-world usage or traction beyond the demo.

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.