Sound City

The story

1. problem

   A scene scattered across sources

   Chicago house and techno discovery is fragmented across venue calendars, Resident Advisor, ticketing pages, promoters, and social posts. Finding smaller nights often means already knowing which rooms, artists, and sources to watch.

2. build

   Ingest broadly, publish carefully

   Next.js route handlers, Neon Postgres, and Drizzle model city-aware events, venues, artists, source evidence, and verification dates. Refresh targets produce reviewable suggestions; a maintainer accepts or rejects changes. The system avoids broad crawling and never turns a parser result directly into a public listing.

3. result

   Discovery with receipts

   The product pairs a dense event finder with source links, last-verified timestamps, taste signals, venue context, and an auditable refresh queue. Its industrial warehouse interface stays specific to Chicago club culture while the data workflow protects trust.