Brimstone is built in the open as far as release and testing information permits. We won't call a prototype a product, or a provider approval a completed playback route.
Debian and macOS Core, real music and video playback, Spotify and Bandcamp working routes, Meridian/Sooloos compatibility, and dedicated Control clients under test.
Published and QA builds vary by platformApple Music first, followed by Audius, SoundCloud, Qobuz and TIDAL acceptance, one at a time. No provider can destabilise another accepted module.
Locked technical planGig Guide, personal concert scrapbook, proposed printed memories and colour customisation in Core. Buildroot and Howard Electronics prototypes continue separately.
Roadmap / engineeringNo provider-specific rewrite of the underlying Core just because someone wants another streaming service.
Each standalone module must pass manifest and RPC contract checks, offline fixtures, authentication and refresh, search/pagination, queues, transport and playback state, account isolation, redacted diagnostics, supported-platform checks and manual playback acceptance.
The next wave connects listening with the stories that music carries.
Artist, venue, date and location discovery, linking to authorised concert and ticket listings.
Learn more →Event-centred personal photos, clips and memorabilia; printed concert books are a proposed later step.
Learn more →R2 theme customisation, accessibility, and per-user presentation preferences without touching playback behaviour.
New hardware and software are accepted on their own merits, not because an attractive render exists.
A purpose-built appliance direction with separate OS/Core updates, recoverability and isolated audio output roles.
Learn more →Build identifiers, checksums, signatures, hardware requirements and known limitations accompany published packages.
Learn more →