Corkboard (corkboard.wine)

A private network of wine enthusiasts wanted a place to rate wines already tried and track the ones still on the list, something more personal than a general-purpose rating app.

A wine-logging app, invite-only by design, with an uncapped invite chain doing the rest of the growth: a small seed group gets a code, and from there the network grows through invites those users choose to send, with no cap set from the top.

Live and invite-only. Three seed invite codes went out at launch, and each holder is free to invite as many people as they want, so the initial cohort is a seed for however far the network wants to grow on its own.

• Problem definition
• Product design
• Application development
• Deployment
• Client communication
• Maintenance

1. 01Finding a wine is built around how people actually think about a bottle, not a search box. Entry is a progressive drill-down: start with the brand, narrow to the varietal, then the specific bottling, then pick the vintage from a dropdown.
2. 02Something like Josh to Cab to Hearth to 2024, rather than typing the whole thing out and hoping for a match.
3. 03Logged wines land in a poster-style feed: image-forward tiles with details in small text beneath, closer to a film-log layout than a spreadsheet.
4. 04Wines with no photo fall back to a typographic label plate tile instead of a blank space.
5. 05A combined feed shows a user's own entries alongside their invited circle's, so browsing what a friend has tried is part of the app rather than a separate step.

The frontend was built in Claude Code.

The backend runs on a Supabase project owned directly by the client, not a third-party-managed one.

Resend handles invite, confirmation, and password-reset email through Supabase Auth.

The app is hosted on Cloudflare, running at its own domain.

• The invite-only rollout is deliberate, not a workaround: there's no public preview yet, so the only way in right now is through an existing member. A public preview mode is planned.
• Feature requests from users are being held, not folded in immediately. The plan is to open that up one week after the site reaches 10 active users, so there's been enough real use to surface bugs and actual gaps before scope grows.