A Mac can be the server, the local player, or both at once. Quven publishes signed and notarized packages for Intel and Apple silicon: a Bundle for the combined use, and Server-only for a machine you’ve set aside to host the library.
Bundle or Server-only
Which one do you need? If the Mac is also something you watch on, the Bundle: it keeps the server and the native desktop app in one lifecycle. If it’s a Mac mini kept out of the way, a shared machine, or any always-on host you reach from native clients elsewhere in the house, Server-only, which drops the local desktop surface.
Native playback and media tools
The desktop client uses the native full-fidelity playback path for compatible files, which covers track selection and the formats a browser would force through a conversion. The server brings its own media tooling, so there’s nothing you should need to install for it. Where the active codec and the hardware support it, it can use VideoToolbox; where they don’t, there’s a CPU path.
Current release evidence
The public macOS packages are Developer ID signed, notarized and stapled for both architectures. Package and Gatekeeper validation is done. Runtime acceptance is tracked separately for each architecture and each release shape, so a package being available doesn’t mean every hardware smoke test for it has closed.
Before you settle on a Mac as the permanent host, check three things: that the library volumes remount with the same paths after a restart, that the service identity can read them, and that the sleep settings won’t cut off a remote client halfway through a film. And keep first-install acceptance separate from update acceptance. Open the installed application through Gatekeeper, play some representative media, then verify a later update through the coupled lifecycle you intend to use.
A practical host choice. An Apple-silicon Mac mini is attractive when low idle power and a quiet always-on host matter to you. Check which formats your clients actually play before you buy hardware for peak transcode capacity alone.
Frequently asked questions
Will Gatekeeper stop the installer?
No. Every public macOS package is Developer ID signed and notarized, with the ticket stapled, on both architectures. Gatekeeper validation is complete.
Intel or Apple silicon?
Both are built and published. Runtime acceptance is tracked separately for each architecture, so a package being available isn’t the same as every hardware check being closed.
Is a Mac mini a good permanent host?
It’s attractive when low idle power and a quiet always-on machine matter. Before you commit, check that the library volumes remount with the same paths after a restart, that the service identity can read them, and that the sleep settings won’t cut off remote clients.