Pay pennies for the luxury everyone wants

Overview

Winfold is a penny-auction marketplace: users buy credits, spend pennies per bid, and the winning bidder takes home luxury watches, sneakers, electronics, or vacation packages at a fraction of retail. The product is the moment of winning, and everything in the platform (auctions, credits, rewards, affiliates) compounds toward that one feeling.

The challenge

A penny-auction marketplace is naturally a real-time system. Bid latency is the product, the credit balance is the trust contract, payments have to clear before items ship, and the rewards and affiliate engines have to compound user behavior without obscuring the math. The standard 'monolith first, decompose later' advice doesn't fit because the bidding subsystem and the catalog subsystem need to scale independently from day one.

What we built

A distributed backend with one bounded context per concern: auctions, bidding, catalog, credits, payments, orders, rewards, affiliates, notifications, plus a WebSocket gateway that fans real-time bid updates out to every connected client. Stripe carries the credit purchases and seller payouts. The frontend is one consumer surface that hides the distributed shape entirely: the user sees one product, not eighteen services. Motion-driven micro-celebrations on a winning bid because the moment of winning is the loop the entire platform optimizes for.

Surfaces

Shipped screens, in order of the user's day. Browser chrome added for context only.

Delivered

• 01Real-time auction + bidding engine
• 02Credit purchase + balance ledger
• 03Rewards loop + affiliate program
• 04Stripe-billed payment flow
• 05Distributed backend with per-concern services
• 06Consumer marketplace frontend

Tech stack