The product
Bandgrid brings bands, venues, and events into one application. Visitors can browse public content, while authenticated workflows support management and subscriptions.
My work spans the application’s data model, web experience, deployment, and maintenance. This is an example of the broader application ownership described on my resume.
One decision: keep related workflows in one application
The current application uses AdonisJS, TypeScript, PostgreSQL, and server-rendered Edge views, with browser assets built through Vite. Public pages and authenticated workflows live in the same application.
That keeps ordinary product changes close to the data and server-rendered interface they affect. It also means boundaries and authorization rules need to be clear inside the application; a single deployment does not remove that responsibility.
Data relationships support the experience
An event relates to the artists and venue involved. Public discovery needs to respect whether content is visible, while management workflows need to distinguish the people allowed to change it.
The engineering work is therefore more than presenting an event card: it involves consistent relationships, input validation, visibility, and authorization across different entry points.
Scope and limits
This note describes an event-discovery and management product. It does not claim that Bandgrid processes ticket payments, has a particular number of customers, or achieves a measured performance improvement.