Verity
Log in Get Verity
The system

One core, written once, everywhere in the house.

The same Rust library runs the desktop player today. Here is what is in your hands today and what is coming next, in that order.

The whole house, one library

The Server holds the library and the setup. The Player, the Bridge (on any PC or Pi with a DAC attached, or as our box) and the network speakers play from it. Your iPhone, iPad or Android phone talks to the Server (or to the Player) at home directly, and on the go through the Verity Relay, which only ever sees encrypted bytes.

Your libraryNAS or PC, stays homeVerity Serverone library · one setupevery device · every zoneCOMINGVerity Playeryour computerVerity Bridgeany PC or Pi, or our boxDACSonos · AirPlay · Caststraight from the serverVerity Relayoutbound only · encryptedCOMINGiPhone · iPadon the go, through the RelayAndroidon the go, through the Relayat home: direct, mDNS

Verity Player Available · 0.1.1

Windows desktop (Tauri 2 + Rust core + a plain-JS interface). Everything on the features page. AirPlay 2 (Apple TV coming), Spotify Connect, and every kind of storage from SMB to S3. TIDAL and Qobuz are coming. Gains a "connect to a server" mode when the server ships, and keeps standalone mode forever.

Verity Server Coming

The same core, headless, on a machine that is always on: a Windows service, a Linux daemon, or a container on a NAS. It owns the database, scanner, analyser, stream server, discovery, zones and every network output. Clients hold no database. A USB DAC on a laptop is published as an output owned by that laptop, greyed OFFLINE when it is away. Found at home by mDNS, reached away through the Relay. Per-device tokens, revocable from Settings.

Verity Bridge, the software Coming

A small program you install on another computer or device: a PC in the study, a laptop, a Raspberry Pi, a NAS. Whatever DAC, sound card or amplifier is plugged into that machine becomes a Verity output, a zone of your system, driven by the Server exactly like the speakers on the network. The Bridge decodes there, keeps the bits intact (DoP or native DSD where the DAC supports it), stays in time with the other rooms, and reports back exactly what the DAC negotiated, so the signal path is truthful to the last node. It also answers as a UPnP renderer, so any other control point can use it too.

Verity box, the Bridge as hardware Coming

The same Bridge software built into a fanless streamer of ours, for the rooms where there is no computer to run it on. USB audio out, I2S, coax and optical S/PDIF straight into your DAC, a good onboard DAC to RCA line out for systems without one, Ethernet first, Wi-Fi as an option, a small status display. Plug it in, name the room on the Server, done.

Verity Relay Coming

Your home end opens an outbound TLS connection to the relay and keeps it alive; no inbound port, no dynamic DNS, no VPN. A client on the go connects with the account token and the relay forwards bytes it cannot read: end-to-end encrypted between client and home. It sees who is connected and how much flows, nothing else. Direct path when both ends can reach each other. A "Can the outside reach me?" page tells you what works and why not.

iPhone, iPad and Android apps Coming

The apps need a Verity Server, or the Verity Player running on your computer, to connect to; they are the remote and the mobile player of your system, not a player on their own. They never need a licence: ten of them connect per licence, more in packs of ten. Browse, search, queue, zones, now playing with the signal path, device setup, Vera. A phone is a zone too (headphones, a portable DAC, AirPlay and Chromecast nearby), with the same honesty. Offline cache of chosen albums for travel.

Web interface Available · redesign coming

Today a remote on port 8770 with a PIN: now playing, queue, browse, search, play here. The redesign makes it a first-class client of the server with the same visual identity as the player, phone to TV.

Licence backend This site

Accounts, keys, activations, signed licence tokens (ed25519, public key compiled into the client), update entitlements, abuse flags with a reason you can read and appeal. The API is documented in the product manual as the contract the player, server, bridge and apps use.

Principles every part follows

  1. The signal path is the product. Every stage that touches audio is named and shown.
  2. Bit-perfect by default. Nothing resamples, dithers or attenuates unless you chose it. Then the path says so.
  3. The library never leaves home. Lookups opt-in and itemised. The licence check knows a key, a fingerprint and a version.
  4. Honest states. Fixed volume, offline outputs, unsupported formats, unpaired receivers are shown as what they are.
  5. One core. Features are written once and run in the player, the server and the bridge.
A crystalline ribbon of bits