Vorssaint: a macOS menu bar toolkit for audio, windows, and system monitoring
A one-stop menu bar toolkit for Apple Silicon Macs, combining audio routing, window management, and monitoring in one icon.
GitHub vorssaint/vorssaint-utils Updated 2026-09-05 Branch main Stars 15.3K Forks 539
Swift macOS Menu bar toolkit Audio routing Window management System monitoring Apple Silicon

🧭 Decision Guide

Try it if you

  • You use an Apple Silicon Mac with macOS 14+ and want one place for audio, windows, and system metrics.
    The README's What you need section requires Apple Silicon and macOS 14 Sonoma or newer; Features includes Sound, System monitor, and Windows and the Dock.
  • You need to route music to speakers and calls to a headset separately.
    The README's Per app output section says music can go to speakers while a call goes to a headset.
  • You need live data for CPU, GPU, memory, swap, temperatures, battery, and Network.
    The README's System monitor and Network sections list these metrics, history graphs, session totals, and a speed test.
  • You want to uninstall individual features instead of keeping every module loaded.
    Install only what you use says whole features can be uninstalled, after which they stop loading and use no CPU, memory, or energy.

Skip it if you

  • You use an Intel Mac or macOS 13 or earlier and cannot meet the README's platform requirements.
    The README's What you need section lists only Apple Silicon and macOS 14 Sonoma or newer.
  • You cannot grant permissions but need per-app audio, window previews, or window controls.
    The README's permissions table shows System Audio Recording for Per app volume, Screen Recording for Window previews, and Accessibility for Switcher, Dock, and window controls.
  • You need a Linux, Windows, or Android client rather than a macOS application.
    The project is described as a Free and open-source macOS menu bar toolkit, and the README requires Apple Silicon and macOS 14+.
  • You need mature, stable fan control rather than the Fan Control feature marked beta in the README.
    The README's System monitor entry explicitly labels it as optional Fan Control beta.

Requirements

  • A Mac with Apple Silicon
  • macOS 14 Sonoma or newer
  • Xcode Command Line Tools (required only for building yourself)
  • System Audio Recording for Per app volume
  • Screen Recording for window previews, screenshots, or recordings
  • Accessibility for Switcher, Dock features, or window controls

First step (verbatim from README)

brew install --cask vorssaint

Watch out

  • Uninstalling a feature stops it loading but does not delete settings; reinstalling restores old settings.
    Install only what you use explicitly says Nothing is deleted and installing again brings old settings back.
  • Without System Audio Recording, Per app volume leaves apps on normal system audio.
    The permissions table's Without it entry for System Audio Recording says Apps stay on normal system audio.
  • Window thumbnails may appear as icons when Screen Recording permission is missing.
    When something misbehaves mentions thumbnails showing as icons and points to the troubleshooting guide.
  • Complete uninstallation removes settings and permissions and resets privacy grants.
    Uninstall and When something misbehaves say ./Tools/uninstall.sh removes settings, permissions, and every trace.
  • Network access is limited to visible actions including update checks, speed test, and Homebrew actions.
    Private by default lists the network access scope and states there is no account, analytics, or tracking.

Not stated in the README

  • The README does not specify the minimum Apple Silicon chip model.
  • The README provides no CPU, memory, or battery-consumption figures when all features remain enabled.
  • The README does not specify which Mac models or fan hardware are supported by Fan Control beta.
  • The README provides no feature or performance comparison with specific tools such as Alfred, Bartender, or MonitorControl.
  • The README does not say what the 10 contributors maintain or provide test coverage figures.
  • The README omits the full contents of Keyboard and mouse, Clipboard, Everyday tools, and Energy and display.

💡 Deep Analysis

6
Yes I want to build vorssaint-utils from source on Apple Silicon and macOS 14 Sonoma with only Xcode Command Line Tools, then publish my own GPL v3 fork. Does the project support that workflow?
For: An open-source contributor maintaining a native Swift macOS utility who has only Xcode Command Line Tools and plans to build and maintain a GPL v3 fork

Yes, the project explicitly provides source-build commands, requires only Xcode Command Line Tools, and licenses the source under GPL v3; however, a fork cannot directly reuse the official brand identity.

  • “Build it yourself” says Xcode Command Line Tools are the only requirement, and the build script compiles, generates the icon, and assembles a signed bundle.
  • The README provides the clone, directory-change, and ./build.sh/./build.sh --install workflow for local building or installation into Applications.
  • Project data identifies Swift as the main language and GNU General Public License v3.0 as the license, matching the constraints of a Swift-native fork.
  • The README separates GPL source licensing from the Vorssaint name, icon, and visual identity; a distributed fork needs its own identity.
  • README “Build it yourself”: “Xcode Command Line Tools are the only requirement.”
  • README “Build it yourself”: the script compiles, generates the icon, and assembles the signed bundle
  • Project data: main_language is Swift; license is GNU General Public License v3.0
  • README “Build it yourself”: “forks need their own identity”
git clone https://github.com/vorssaint/vorssaint-utils.git
Not stated in the README:The README does not state whether source builds use the maintainer’s Apple Developer ID or require the local builder to configure a signing identity.;The README does not specify a review or compliance process for name, icon, and UI changes when distributing a fork.
Yes I use an Apple Silicon Mac on macOS 14 Sonoma and need multi-display window switching, window snapping, per-app volume, and separate output for music and calls. Can Vorssaint replace those separate tools?
For: A macOS developer on Apple Silicon and macOS 14 Sonoma who uses separate tools for window layouts and per-app audio, and wants fewer menu bar apps and subscriptions

Yes, because it combines window management and per-app audio routing in one native menu bar app without requiring an additional audio driver.

  • The README’s “Sound” section lists per-app volume, volume above 100%, per-app output routing, and quick output switching; music and calls can be sent to different devices.
  • The “Windows and the Dock” feature set includes snapping, half-screen, one-third, six-zone and corner layouts, multi-display switching, and restoring window history.
  • The project requires Apple Silicon and macOS 14 Sonoma or newer, matching your environment.
  • Per-app volume and output routing require System Audio Recording, while window controls generally require Accessibility; those features remain unavailable without authorization.
  • README “Sound”: “Send your music to the speakers and a call to your headset at the same time.”
  • README “Windows and the Dock”: snapping, layouts, multi-display switching, and window-history restoration
  • README “What you need”: “A Mac with Apple Silicon” and “macOS 14 Sonoma or newer”
  • README “Private by default” permission table: System Audio Recording for per-app volume and output routing; Accessibility for window controls
brew install --cask vorssaint
Not stated in the README:The README provides no compatibility matrix for specific window managers, shortcut tools, or unusual window types.;The README provides no measured CPU, memory, or energy data when window and audio modules run together.
Yes I need to migrate Vorssaint settings to another Apple Silicon Mac running macOS 14 Sonoma and later remove settings, the login item, and permissions after a project ends. Does the README cover both operational paths?
For: A macOS developer migrating window, audio, and monitoring settings across multiple Apple Silicon Macs on macOS 14 Sonoma while needing complete permission revocation and uninstallation

Yes, the README provides both settings export/import and a complete uninstall command, covering the two operational paths you specified.

  • “Install only what you use” says settings can be exported to a file and imported on a new Mac; uninstalling a feature does not delete its settings, so reinstalling can restore them.
  • “Uninstall” provides a Homebrew command to remove the application itself.
  • For complete cleanup of settings and permissions, the README gives ./Tools/uninstall.sh; “When something misbehaves” further says it quits the app, removes the login item, resets privacy grants, and deletes every trace.
  • Official builds are Apple Developer ID signed and notarized, and the README says permissions survive updates, which supports a cross-version maintenance workflow.
  • README “Install only what you use”: “settings export to a file and import on a new Mac”
  • README “Uninstall”: `brew uninstall --cask vorssaint` and `./Tools/uninstall.sh`
  • README “When something misbehaves”: quits the app, drops the login item, resets privacy grants, and deletes every trace
  • README “Install”: “your permissions survive updates”
./build.sh --install  # the same, then install into Applications and launch
Not stated in the README:The README does not say whether the export file includes permission state, login-item state, or sensitive configuration.;The README does not say whether differences between Apple Silicon chip models affect module settings or permission restoration during migration.
Yes I use an Apple Silicon Mac and mainly want CPU, GPU, memory, temperature, battery health, power draw, and network-rate monitoring while minimizing background usage. Can I install only the monitoring features I need?
For: An advanced user who regularly carries an Apple Silicon Mac and cares about battery health and power draw, wanting only monitoring and Battery and quiet features enabled

Yes, because Vorssaint’s feature-installation model lets you enable only the modules you need and removes unused features from the loading scope.

  • “Install only what you use” offers Essentials, Windows, and Battery and quiet bundles, as well as a visual picker for individual features.
  • Uninstalled features disappear from the entire app and stop loading; the README explicitly says they then spend no CPU, memory, or energy, while reinstalling restores previous settings.
  • “Know what your Mac is doing” lists CPU, GPU, memory, swap, temperatures, battery health, remaining time, cycle count, power draw, fan speed, live network rates, and a speed test.
  • Menu bar readouts can be limited to the metrics you care about and shown as values or compact usage bars.
  • README “Install only what you use”: “stops loading, so it spends no CPU, memory or energy”
  • README “Install only what you use”: Essentials, Windows, Battery and quiet, and the visual picker
  • README “Know what your Mac is doing”: listed monitoring metrics
  • README “Menu bar readouts”: values or compact usage bars
brew install --cask vorssaint
Not stated in the README:The README provides no measured CPU, memory, or battery-consumption benchmarks for individual monitoring modules or combinations.;The README does not specify the exact modules included in Battery and quiet or how it differs from individual selection.
It depends I need per-app volume, output routing, window thumbnails, and recording, but I do not want an account or data leaving my Mac. Do Vorssaint’s permissions and network behavior fit that constraint?
For: A privacy-sensitive developer handling meetings and recordings on Apple Silicon and macOS 14 Sonoma who needs audio routing and window previews without accounts or analytics

It depends: the default privacy model fits your requirement, but audio and capture features require relatively powerful macOS permissions.

  • “Private by default” explicitly says there is no account, analytics, or tracking, and that the app is local-first.
  • Network access is limited to visible operations such as update checks, speed tests, Homebrew actions, temporary screenshot or recording links, and feedback you explicitly send; it is therefore not an absolute no-network application.
  • System Audio Recording is used for per-app volume and output routing, while Screen Recording is used for window previews, screenshots, text copying, and recordings. Those features are unavailable without the permissions.
  • Permissions are optional; the app explains their purposes, shows which features use them, and identifies permissions that are no longer needed for quick revocation.
  • README “Private by default”: “no account, analytics or tracking”
  • README “Private by default”: network is used only for update checks, speed tests, Homebrew actions, temporary screenshot or recording links, and explicit feedback
  • README permission table: purposes of System Audio Recording and Screen Recording, plus behavior without them
  • README “Private by default”: every permission is optional and the app shows when it is no longer needed
brew install --cask vorssaint
Not stated in the README:The README does not identify the service, retention period, access control, or data residency for temporary screenshot or recording links.;The README does not state whether audio routing and window previews recover immediately after permission changes or require an app restart.
It depends I want to use the Fan Control beta on my Apple Silicon Mac with continuous manual speeds and custom temperature curves. Is it suitable for my daily production machine?
For: An advanced Apple Silicon Mac user considering manual fan control who needs continuous speeds, temperature curves, and live RPM without compromising noise, power, or thermal behavior

It depends, because the README confirms the required control features but labels Fan Control as beta, so it cannot establish suitability for every production machine.

  • “Know what your Mac is doing” lists optional Fan Control beta, continuous manual speeds, custom temperature curves, and live RPM, covering your requested controls.
  • The system monitor also exposes temperature, power draw, and fan speed, allowing you to observe the control outcome.
  • Project insights state that manual speeds and temperature curves may affect noise, power use, or thermal management; the README provides no hardware compatibility matrix.
  • The latest project data marks the release as v3.3.3-beta.4, with 5 releases in total, so stability information remains limited.
  • README “Know what your Mac is doing”: “an optional Fan Control beta with continuous manual speeds, custom temperature curves and live RPM”
  • README “System monitor”: temperature, power draw, and fan speed
  • Project insights “common_pitfalls”: Fan Control is beta and may affect noise, power, or thermal management
  • Project data: latest_release is v3.3.3-beta.4 and release_count is 5
brew install --cask vorssaint
Not stated in the README:The README does not specify supported Apple Silicon chip models, Mac model coverage, or sensor differences.;The README provides no fail-safe behavior, default fallback strategy, temperature limits, or long-term stability data for Fan Control beta.

✨ Highlights

  • Volume mixer supports per-app volume, exact percentages, and over 100% gain
  • System monitor covers CPU, GPU, memory, temperatures, and battery
  • Features can be uninstalled entirely, stopping their CPU, memory, and energy use
  • No account, telemetry, or subscription; the code uses GPL v3.0

🔧 Engineering

  • Per app output can send music to speakers and calls to a headset simultaneously
  • App switcher provides window thumbnails, minimized windows, and multi-window switching
  • Window layout supports halves, thirds, sixths, corners, and moving across displays
  • Network provides live rates, session totals, and a built-in speed test

⚠️ Risks

  • The README requires Apple Silicon and macOS 14 Sonoma or newer
  • Per app volume needs System Audio Recording; without it, apps stay on normal system audio
  • Window previews and screenshots need Screen Recording; otherwise those captures are unavailable
  • Fan Control is still marked beta and includes manual speeds and temperature curves
  • Official builds come only from the maintainer; forks need their own name, icon, and look

👥 For who?

  • Heavy menu bar users on Apple Silicon Macs running macOS 14+
  • Audio and meeting users needing Per app output and multi-input muting
  • Mac users frequently managing multiple windows, displays, and Dock thumbnails
  • Users wanting one menu bar icon instead of several paid utilities