OpenAI 2026 hackathon

Icreate Storefront

Icreate Storefront is a self-hosted local resale marketplace with offers, checkout and fulfillment, secured by password-free email, SMS and authenticator verification.

Solo project by Doanld Merrow · 0 likes · 0 comments

Archive position — measured, not model output

0 likes on Devpost

2,264 of the 7,856 archived projects have more likes, and 5,592 share exactly 0 — so this project's #4,596 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

Icreate Storefront is a self-hosted local resale marketplace built around a password-free authentication system (Icreate Gate). The platform enables local sellers and storefront operators to list products, manage inventory, process offers and negotiations, handle checkout via Stripe, and coordinate fulfillment through pickup or shipping. It is described as a community-driven commerce tool for one-of-a-kind and second-hand goods.

What changed

The project evolved from an identity authentication tool (Icreate Gate) into a full local resale marketplace. The author notes that the original goal was to explore password-free authentication for small companies, but it expanded into a functional storefront system after realizing secure authentication needed to protect something real.

Single most important open question

Is there evidence of traction or adoption beyond the single developer's own implementation? The description contains no data on users, customers, revenue, or usage metrics — only self-reported development and feature descriptions.

Note

This analysis is based entirely on the author’s own description. No external verification or historical data is available. All claims are unverified self-reporting.

Back to contents

What The Product Actually Is

The description states that Icreate Storefront combines:

  • Password-free identity
  • Product listings
  • Price negotiation
  • Checkout and fulfillment

It uses a three-stage verification process:

  1. Single-use email code (via Gmail OAuth)
  2. SMS verification (via Twilio Verify)
  3. Authenticator app code (TOTP)

The system is built with Rust (Axum), Redis for state management, and integrates with Stripe for checkout.

Inference The product is a self-hosted platform designed to support local resale markets using password-free authentication as its core security mechanism.

Back to contents

Positioning & Claim Evolution

The author states that Icreate Storefront began as Icreate Gate — a password-free authentication project. It evolved into a local resale marketplace after recognizing that secure identity was only useful when protecting something real.

Claim

The platform is positioned as a community-driven, local resale marketplace with a focus on trust and physical custody of goods.

Inference This positioning reflects an attempt to differentiate from large-scale online marketplaces by emphasizing local control, verification, and transparency in product ownership.

Back to contents

Target Customer & ICP

The description states that the platform is especially relevant to:

  • Community resale projects
  • Independent second-hand markets
  • Local consignment stores
  • Market operators or hosts in Vancouver

Claim

The target customer includes small-scale sellers, local storefronts, and community-based marketplaces.

Inference The ICP appears to be individuals or organizations operating in a localized, trust-based resale ecosystem where physical product verification is critical.

Back to contents

Business Model & Pricing Evidence

The description states:

  • No listing fees
  • A configurable platform commission of 5% of item price (excluding shipping)
  • Commission recorded server-side but not automated for payouts
  • Stripe-hosted checkout used in test mode
  • Current default is 5% commission, with no mention of seller payout automation or third-party integrations

Claim

The business model uses a commission-based revenue structure.

Inference There is no evidence of actual monetization, customer acquisition, or payment processing beyond test mode.

Back to contents

Technical & Delivery Signals

The system is built using:

  • Rust (Axum framework)
  • Redis for temporary and persistent state
  • Gmail OAuth, Twilio Verify, TOTP for authentication
  • HTML/CSS/JS frontend
  • Stripe-hosted checkout
  • Native deployment without Docker
  • Cross-platform support (Linux, macOS, Windows)

Claim

The platform is technically robust with secure storage, encryption, and multi-factor verification.

Inference The technical stack suggests a focus on security and performance, but no evidence of production-grade infrastructure or scalability.

Back to contents

Traction & Maturity Signals

The description contains no evidence of:

  • Revenue
  • Customers
  • Users
  • Adoption
  • Product-market fit
  • Market traction

Claim

There is no indication of real-world usage or commercial success.

Inference The project appears to be a proof-of-concept or prototype, not yet in production use.

Back to contents

Competitive Context

The description does not mention any competitors. It focuses on the local resale niche and emphasizes trust and physical custody as key differentiators.

Claim

Icreate Storefront targets a specific segment of local resale markets.

Inference Without explicit competitor references, it's unclear how this compares to existing platforms like Facebook Marketplace, eBay, or local consignment apps.

Back to contents

Key Risks & Red Flags

  • No evidence of real users or revenue
  • Platform is described as a prototype with incomplete features (e.g., no automated payouts)
  • Single developer team (1 member)
  • No mention of security audits or production testing
  • Reliance on external services like Twilio, Gmail, Stripe for core functionality
  • Lack of data on scalability or performance under load

Inference The project lacks commercial viability indicators and may be in early development stages.

Back to contents

Diligence Questions To Ask The Founders

  1. What is the actual user base beyond the developer?
  2. Are there any real-world pilots or partnerships with local stores or markets?
  3. How does the platform plan to scale beyond a single developer's implementation?
  4. Has the authentication system been tested in production environments?
  5. What are the plans for automating seller payouts and handling chargebacks?
  6. Is there an existing roadmap for completing missing features like account recovery or full payout automation?

Back to contents

Investment/Partnership Verdict

Not evidenced

There is no evidence of revenue, customers, traction, or commercial viability beyond the author’s own description. The project is described as a prototype with many planned features not yet implemented.

Verdict This is an early-stage idea or proof-of-concept with no demonstrated market traction or business model execution. It cannot be evaluated for investment or partnership potential without further evidence of adoption, revenue, or product-market fit.

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.