live
BandHub
Preview unavailable The details below still apply. 
One booking platform running several live band brands.
A multi-tenant booking platform for tribute and cover bands: discovery, buyer intake, owner workflows, moderation, reviews, inquiries, content operations, analytics, imports, and billing readiness.
Deployments: MZTributeBands
The live tenants are the public reference, and the BandHub source stays private.
Read case study brief · what i owned · key decisions · what shipped · evidence · result · implementation
The problem
It started when a working band business needed its aging backend and public sites replaced. The catch was that each brand had to stay distinct, without redoing the catalog, funnel, and operations work for every storefront.
What I owned
- I did the product architecture and full-stack engineering across the shared storefront, catalog, booking funnel, owner tools, administration, imports, and deployment operations.
Key decisions
- Resolve each tenant by hostname into brand, content, and feature configuration stored in the database, so no brand needs its own fork of the app.
- Keep an act’s identity separate from where it’s placed, and let shared catalog memberships handle the placement.
- Roll out each tenant from a manifest: validate, apply, seed, verify.
- Keep funnel, storefront, catalog, owner SaaS, and internal operations as explicit lanes, but ship them all as one deployable application on one database.
What shipped
- One Next.js App Router codebase serves several public band-booking tenants, and site configuration plus hostname resolution decide which one you get.
- It includes public directories and profiles, request flows that know about your shortlist, submit-act moderation, an owner dashboard, admin operations, an audit trail, and import tooling.
- It runs on PostgreSQL and Drizzle ORM, with first-party magic-link auth, Resend email, Cloudflare Turnstile, local media storage and proxy, and optional Stripe billing.
Evidence
- You can see it live: the MZ Tribute Bands production domain runs as its own BandHub storefront on the shared platform.
- Captures from the MZ deployment show the homepage, search and filtering, branded collections, profiles, EPK downloads, and booking inquiries.
- Imports and tenant rollouts are repeatable, and they bring over legacy catalogs, packages, posts, and reviews.
Result
- One running application now serves several public booking brands, each with its own look.
Implementation
- Next.js
- React
- PostgreSQL
- Drizzle
- Multi-tenant
Captures
