Standalone QA
Manifest, RPC, offline fixtures, authorisation and token refresh must all pass before integration.
Honest integrations.
No pretend play buttons.
Brimstone separates provider modules from the Core engine. Working services stay working while new ones are built and tested independently.
RIGHT NOW
R1 services & availability
These are integration states, not an assertion of endorsement or commercial partnership by each provider.
| Service | State | What this means |
|---|---|---|
| Spotify | R1 working route | Playlists, queue and compatible Core home outputs; validated routes include Meridian. |
| Bandcamp Collection | R1 regression reference | Collection route retained and protected during R2 provider expansion. |
| Bandcamp Radio | R1 working route | Radio catalogue, station tiles and playback. |
| Internet radio | R1 integrated | Browse worldwide stations and discover by place, name and genre. |
| Apple Music | Native MusicKit route; R2 expansion | Protected playback remains in official MusicKit. Catalogue, saved library, playlists and wider client acceptance are the first R2 module. |
| TIDAL | Partner approval pending | Search and personal library work preserved. Full-track playback is not available for general release until the partner gate and acceptance pass. |
| Amazon Music | Coming Soon | No active account connection or playback route until approved access exists. |
TIDAL: the integration is prepared, but general full-track playback is awaiting provider authorisation and final testing. Protected streaming audio is never extracted or rehosted.
R2 PROVIDER FRAMEWORK
One at a time.
Without breaking what's working.
Each service is its own independent module, built and accepted before it is attached to Core.
- Apple MusicMusicKit catalogue, user library, playlists, official queue and protected playback on eligible platforms.
- AudiusSearch and provider-authorised direct streams.
- SoundCloudCatalogue search, OAuth as needed and authorised playback.
- QobuzLossless / high-resolution playback, subject to partner credentials and service approval.
- TIDALComplete standalone full-track playback acceptance once the right application access is granted.
Transport contract
Search, pagination, queues, playback transport, duration, position and account isolation are tested.
Protect what works
R1 Spotify and Bandcamp regression checks must pass with every addition; failed modules stay isolated.
Deliberate exclusions: YouTube and YouTube Music are not R2 streaming providers. Amazon Music remains Coming Soon; no unauthorised connection buttons or unofficial protected streams.
App/platform output capabilities are controlled by each provider's licences and supported native player. Services can require an active subscription.
BE PART OF BRIMSTONE
See the full development roadmap.
Every module has acceptance gates — and we publish the difference between a working API and customer-ready playback.