OpenFans

Company: OpenFans

Self-reported purpose: A platform to verify fan authenticity for live event ticketing using photo uploads and metadata analysis, aiming to reduce botting and scalping.

What changed: The project was submitted as a hackathon entry (Devpost, OpenAI 2026) with no prior traction or commercial activity.

Single most important open question: Is there any evidence of real-world adoption, user feedback, or product-market fit beyond the author's self-reported claims?

The description is entirely self-reported and unverified. No revenue, customers, or traction data are available. The project appears to be a proof-of-concept built in Swift with AI assistance (Codex), but no further development or commercialization is evidenced.

The description states that OpenFans is a system for verifying fan authenticity for live event ticketing by analyzing user behavior and photo metadata. It claims to link supportive actions such as:

• Attending past concerts
• Following an artist's social profiles
• Having a number of streams
• Purchasing merch

It uses photo uploads as part of the verification process, with metadata analysis (e.g., time added to gallery) to detect potential spoofing.

Inference: The product appears to be a mobile app or software tool that integrates with Apple’s Photos framework and leverages AI for metadata processing. It is not clear whether it functions as a standalone app or integrates into existing ticketing platforms.

Not evidenced: No details on how the verification process works technically beyond metadata use, nor what constitutes a “fan” in practice.

The author states that OpenFans was built to address the problem of not being able to fight for concert tickets despite being a true fan, especially when facing bots and scalpers. It positions itself as a solution that uses social behavior and photo verification to prove fandom.

Claim: The product aims to reduce botting and scalping by verifying real fans through metadata and behavioral signals.

Inference: This is a repositioning of the ticketing problem from “fair access” to “authenticity verification,” using a hybrid of user behavior and digital proof.

Not evidenced: No evidence of prior positioning, branding, or messaging beyond this hackathon submission. No mention of how it differs from existing fan verification systems or platforms.

The description states that OpenFans targets fans who are trying to get concert tickets but are blocked by bots and scalpers. It also implies a focus on artists and event organizers who want to ensure fair ticket distribution.

Claim: The target is fans, artists, and event organizers in the live music industry.

Inference: The ICP likely includes individuals who attend concerts regularly, follow artists, and have digital footprints (e.g., streams, social media engagement).

Not evidenced: No evidence of customer personas, user segments, or how the product would be monetized. No mention of artist or venue partnerships.

The description does not provide any information on pricing, monetization, or business model. It only describes a product concept and its use case.

Claim: Not stated.

Inference: If commercialized, it might involve licensing to ticketing platforms or charging fees for verification services, but this is speculative.

Not evidenced: No revenue streams, pricing models, or monetization strategies are described.

The project was built using Swift and Codex (Ultra mode), with no prior Swift experience by the author. It involved:

• Metadata analysis of photos via PhotosKit
• Handling media permission access
• Self-signing an app

Claim: The team built a functional MVP in one week with zero Swift experience.

Inference: This suggests a rapid prototyping approach, possibly using AI tools for development assistance.

Not evidenced: No details on scalability, backend infrastructure, or integration with ticketing systems. No mention of security or privacy considerations beyond metadata use.

The project is described as a hackathon submission (Devpost, OpenAI 2026). It has no known traction, revenue, or user base. The team size is listed as zero, and there are no mentions of customers, partners, or product usage.

Claim: The project was built in one week with no prior experience in Swift.

Inference: This indicates a very early-stage prototype, likely not yet ready for market.

Not evidenced: No evidence of user testing, feedback loops, or any form of product development beyond the hackathon.

The description does not mention competitors. It implies that current solutions are vulnerable to bots and scalpers, but does not compare OpenFans to existing tools in the space.

Claim: The product addresses a gap in current ticketing systems.

Inference: The competitive landscape likely includes ticketing platforms like Ticketmaster, StubHub, or secondary marketplaces, which may already have anti-bot measures.

Not evidenced: No evidence of competitor analysis, market positioning, or differentiation from existing tools.

• Unproven concept: The product is a hackathon prototype with no real-world testing.
• No team: Team size is listed as zero; no members are named.
• No traction or revenue: No evidence of users, customers, or monetization.
• Technical limitations: Metadata verification may be easily bypassed or misused.
• Privacy concerns: Use of photo metadata raises privacy issues without clear safeguards.

Inference: The project is in a very early phase and lacks commercial viability or scalability.

1. What specific user behaviors are being used to verify fandom, and how are they weighted?
2. How does the system prevent false positives or spoofing of photos?
3. Have you tested this with real users or event organizers?
4. What is your plan for monetization or scaling beyond a hackathon prototype?
5. Are there any legal or privacy implications of collecting and analyzing user photo metadata?