The public platform combines a record label, releases, editorial, events, a Spotify-powered music library, merchandise commerce, media infrastructure, and purpose-built administration.
It operates across four production hostnames rather than presenting every concern through one application shell.
Separation without fragmentation
The label site and standalone store have different browsing and conversion goals. Administration needs authenticated control over artists, releases, products, categories, media, and connected commerce.
A shared data and media layer keeps the surfaces coherent while allowing each hostname to optimise its own navigation and release cycle.
Promotion discipline
The system combines a managed database, object storage for media, a payment provider and ticketing through eventOS. Preflight checks run before production promotion so schema, content, storage, and provider configuration failures are caught before deployment.
The architectural lesson is that a product family can share state and operations without forcing every audience into one interface.