SaaS Metrics
TL;DR: I built a website that allows users to track the concerts they've been to. If you have strong opinions about engineering/design or how shows should be tracked (festivals, venues, etc...), I'd love to get your input!For the past ~5 years, I've been tracking the shows I attend on my personal website (https://love-music-will-travel.henryrobbins.com). It's fun to see things like distance traveled and how many times I've been to certain venues. I know many friends who also track their shows through notes, ticket stubs, Excel, etc... It always bummed me out that I couldn't pore through their concert data myself...showcount.com is my solution to that desire. It's essentially a public version of my old personal website, where anyone can make an account and manage a show list (mine is https://www.showcount.com/user/love-music-will-travel).I'm currently on the lookout for other live music lovers and/or data nerds to try out the site and give opinions on various design choices. If any of the following topics are of interest to you, please reach out!- How should venue name/location changes be handled?
- How should music festivals be handled?
- I have an initial version of an AI parser for loading in existing show lists; how can this be made more robust?
- What else should have first-class tracking support (e.g., friends in attendance)?As an aside, this project is also my first experiment with full-on vibe-coding / harness-engineering. I began the project with Cursor and then switched to Claude Code. I've been programming for the better part of a decade, mostly Python and Java. Full-stack development is relatively new to me. I include the tech stack below. Most decisions were made pragmatically based on what I thought would get me to a first version of the site as quickly as possible.- Next.js web app hosted on Vercel
- Fast API backend service (for the AI parsing) hosted on Railway
- Supabase
- Observability through Axiom (logging), PostHog (analytics), and Sentry (monitoring)
- Clerk for user authentication
- Google Maps API for venue locations
- Claude API for the AI parser
- Terraform for infra-as-code
Show HN: A website to track live music attendance
A public platform for users to track concerts, replacing personal notes, spreadsheets, or private websites, enabling sharing and analysis of concert data.
View Origin LinkProduct Positioning & Context
AI Executive Synthesis
A public platform for users to track concerts, replacing personal notes, spreadsheets, or private websites, enabling sharing and analysis of concert data.
Showcount.com targets a consumer niche for live music enthusiasts, addressing the fragmented and private nature of personal concert tracking. While primarily a B2C offering, its underlying technical stack demonstrates modern full-stack development practices, including serverless deployment, managed backend services, and AI integration for data parsing. The use of observability tools like Axiom, PostHog, and Sentry indicates a focus on operational robustness, even for a personal project. The 'AI parser' for existing show lists highlights a common data migration pain point, where AI can streamline onboarding. This project, while not B2B SaaS itself, showcases a practical application of contemporary cloud and AI tooling.
Related Ecosystem & Alternatives
Discover adjacent products, open-source repositories, and developer tools sharing similar technical architecture.
Deep-Dive FAQs
What is A website to track live music attendance?
A website to track live music attendance is analyzed by our AI as: A public platform for users to track concerts, replacing personal notes, spreadsheets, or private websites, enabling sharing and analysis of concert data.. It focuses on Showcount.com targets a consumer niche for live music enthusiasts, addressing the fragmented and private nature of personal concert tracking. While...
Where did A website to track live music attendance originate?
Data for A website to track live music attendance was aggregated directly from the Hacker News community ecosystem, representing raw developer and early-adopter sentiment.
When was A website to track live music attendance publicly launched?
The initial public indexing or launch date for A website to track live music attendance within our tracked developer communities was recorded on April 9, 2026.
How popular is A website to track live music attendance?
A website to track live music attendance has achieved measurable traction, logging over 3 traction score and facilitating 0 recorded discussions or engagements.
Which technical categories define A website to track live music attendance?
Based on metadata extraction, A website to track live music attendance is categorized under topics such as: AI parser, Next.js, Vercel, Fast API.
How does the creator describe A website to track live music attendance?
The original author or development team describes the product as follows: "TL;DR: I built a website that allows users to track the concerts they've been to. If you have strong opinions about engineering/design or how shows should be tracked (festivals, venues, etc...), I'..."
Community Voice & Feedback
No active discussions extracted yet.
Discovery Source
Hacker News Aggregated via automated community intelligence tracking.
Tech Stack Dependencies
No direct open-source NPM package mentions detected in the product documentation.
Media Tractions & Mentions
No mainstream media stories specifically mentioning this product name have been intercepted yet.
Deep Research & Science
No direct peer-reviewed scientific literature matched with this product's architecture.