Search
BitChord asks the gateway for a track. The gateway checks the providers it is configured to use.
Checking status
Verifying upstream lossless engines and stream routing.
24-bit / 192 kHz Dolby Atmos Pass-through
Checking upstream connectivity…
Checking which engines are serving requests.
Checking…
Checking…
Waiting for the first status update.
Cumulative stream resolution and lossless format mix across sessions.
Since last start
—
Streams served
All-time resolved
—
Hi-Res & Atmos
Studio-master share
—
Active clients
—
Avg latency
Upstream pass-through
Real-time tracks and delivered studio tiers across Qobuz and Tidal — anonymous by design.
Loading play history…
Cumulative stream and catalog counts across sessions — zero personal identifiers stored.
Each column is one hour, stacked by the quality the provider actually returned.
Select a column for the exact reading.
Times are rounded to the minute. No listener is named — sessions are deduplicated with a salted hash that is dropped on restart.
Confih connects BitChord to the music providers it already uses. It does not host music, create accounts or track listeners.
Checks configured Qobuz and Tidal pools and verifies bit-depth before failover.
Returns signed upstream FLAC and Dolby Atmos URLs with zero transcoding.
Local SVG QR codes, self-hosted fonts, and proxied covers under strict 'self' CSP.
Three steps, every time you play a track.
BitChord asks the gateway for a track. The gateway checks the providers it is configured to use.
It picks the best available match and quality, then falls back to the other provider only when the match is safe.
BitChord receives a playable URL with honest codec, bit-depth and sample-rate metadata. Nothing is transcoded.
The public status and play feeds contain aggregate counts: active clients, streams, errors, ranked tracks and quality totals. Neither contains account names, email addresses or a per-listener history.
On the Plays page, timestamps are rounded to the minute and listener sessions are deduplicated with an in-memory salted hash that is dropped on restart (so a returning listener counts again after a restart). Album covers and QR codes are served or generated locally so your browser makes zero third-party requests.
The gateway needs provider credentials to work, but those stay on the server. When you play a track, the stream request still goes to Qobuz or Tidal under their own terms and privacy policies.
This is a personal gateway, not an official service.
Provider names and marks belong to their owners. Quality claims come from what the provider returns, not from marketing copy.
The gateway is free to use. Donations are optional and never unlock extra access. If something is broken, the status page and the repository are the honest places to look, or write to support at bitchord.confih.tech.
Protocol guarantees built for BitChord.
Qobuz and Tidal today. The addon core is provider-agnostic, so more platforms are planned — no dates, no promises.
This gateway is one server, one modest bill and a lot of late evenings chasing provider changes. No ads, no accounts, nothing about you sold — just a quiet bridge between BitChord and the music you already pay for.
A contribution toward server time and bandwidth, from someone who got something out of this. Not a subscription, not a token, not a queue jump — the gateway behaves the same for everyone.
Confih is not a company. It is one machine in a datacenter, a tunnel, two provider subscriptions and me, keeping the queue clear.
Everything here happens after work: the fixes, the retries, watching a token rotate at two in the morning so your next track still plays. Nobody pays me for that, and I would keep doing it anyway. But the bill arrives whether anyone listens that week or not.
If this gateway has been good to your library — if it found you an album you thought was gone, or saved you a subscription — be good to it once. There is no plan to cancel later, and nothing extra you can buy.
— Confih one listener, not a company
A card or wallet you already have, one transfer, nothing recurring. If you use crypto, send only the asset and network listed beside the address — those transfers are irreversible.
No account, no crypto, no amount that buys anything extra. If the gateway saved you a subscription this month, this is the shortest thank-you.
or send crypto directly
Demo data — no live addresses are configured.
Loading donation details…
Four things keep a small gateway alive. None of them are optional.
Each track you play costs a search, a match and a signature on this machine.
Lossless streams pass through this server, and that traffic is the largest line on the bill.
Accounts, statistics and small backups, so a restart never erases what you listened to.
Provider changes, expired tokens and new BitChord releases — the work nobody sees from the player.
Donations are not a subscription. There is no priority queue, no private endpoint and no donation token or credit system. The gateway behaves the same for everyone.
There are also no perks that expose another listener's data, and no way to buy extra quality. Quality is limited by what the providers actually deliver. A thank-you is all you get, and it is genuine.
Donations are optional. These cost nothing and are just as useful.
No ticket system and no chatbot. Two addresses, both read by the same human.
Something is broken, a donation bounced, or you want to tell me the gateway found you an album.
SecurityA vulnerability, a leaked credential or something that exposes another listener. Please do not post exploit details in a public issue.