Band catalog and publishing
Bands can manage compositions, recordings, releases, artwork, credits and public profiles from Studio.
Public roadmap
Build the scene.
Then scale it.
Underground is being developed in public. This page separates what already works, what blocks the beta and what is intentionally being left for later.
Priorities may move when testing exposes more important reliability, legal or operational work.
The foundation is working
Available now
Discovery and continuous listening
Public discovery, automated home sections and the persistent player turn the catalog into a continuous listening flow.
Shared live events
A concert is stored once, connected to every participating band and exposed through public and Studio views.
Split and compilation releases
Multiple bands can collaborate on one canonical release, contribute their own tracks and expose it in every discography.
Recruitment and scene networking
Bands and artists can publish recruitment listings, discover opportunities and start contextual conversations.
Privacy, moderation and legal foundation
The platform includes reporting, privacy-request workflows, legal documents and operational compliance foundations.
Current priority
Before public beta
Notification flow fixes
Make invitations, lifecycle updates, unread states and actionable destinations consistent across every domain.
Security improvements
Harden authentication, authorization, rate limits, upload boundaries, secrets, headers and sensitive operational workflows.
Email implementation v2
Replace the MVP mail layer with reliable transactional delivery, templates, retries, observability and tested user-facing flows.
Unique band identity
Ensure every band has a stable, collision-safe identity across URLs, invitations, search, imports and future integrations.
CI issues resolved
Remove flaky or inconsistent checks and make lint, typecheck, tests, builds and migrations dependable release gates.
Legal terms validated
Complete qualified Italian and EU review and publish validated production terms, privacy and operational legal documents.
Production deployment hardening
Finalize production secrets, domains, object storage, mail delivery, health checks, backup and restore procedures.
End-to-end smoke testing
Exercise registration, band onboarding, uploads, publishing, collaborations, live invitations, playback and moderation as complete user journeys.
Administration and moderation polish
Make reports, audit history, privacy requests and platform settings reliable enough for daily operation.
Performance and failure recovery
Validate large uploads, transcoding failures, partial outages, queue recovery and public-page performance under realistic data.
After the beta baseline
Next product work
Richer live discovery
Add practical filters for date, location, region, venue and participating band while keeping event creation lightweight.
Venue accounts
Give venues a focused workspace for profiles, events, invitations and discovery without duplicating the band experience.
Scene graph and recommendations
Use real relationships such as played-with, shared venues, geography, genres and collaborations to improve discovery.
Notifications and conversations polish
Improve inbox ergonomics, contextual navigation, unread states and the transition from discovery to collaboration.
Public embeds and sharing
Offer reusable players and release or event cards that bands can place on their own websites.
Listening-first product
Milestone: Player App
Dedicated Player App
Build a focused listening experience on top of the shared API, catalog, discovery queue and playback contracts proven by the platform.
Library, queue and playlists
Turn the current persistent player into a complete listener product with saved music, queue control and portable playback state.
Web first, mobile-ready
Deliver the listening-first web application before native clients, while keeping contracts suitable for future mobile apps.
Not required for launch
Later, deliberately
Native mobile player
A native client can follow once the Player App contracts and real listening behavior are stable.
Merchandise integrations
Support external commerce links first. A native marketplace is intentionally not part of the initial operating model.
Advanced editorial tools
Curated collections, scene spotlights and editorial programming can grow once there is enough active catalog and community data.