Vorssaint: a menu bar toolkit that treats features as installable modules

The problem Vorssaint solves is menu bar crowding, not missing features

Most Mac users who buy utilities buy them one at a time: a volume mixer, a window snapper, a clipboard manager, an uninstaller. Each one adds its own menu bar icon, its own updater, its own permission prompts and its own background process. Vorssaint's pitch is consolidation. The README describes it as "One menu bar icon doing the job of a dozen paid Mac apps," and lists per-app volume, a system monitor, an app switcher, window snapping, Dock previews, clipboard history, text snippets, a file shelf and an uninstaller in one application.

The audience is therefore narrow and specific: people who already know they want three or four of those tools, run macOS as their daily driver, and are bothered by the overhead of running them separately. It is not aimed at someone who wants exactly one utility, and it is not aimed at Linux or Windows users, because the whole design leans on macOS-specific surfaces such as the menu bar, the Dock, Spaces and the green maximize button.

The consolidation claim is the part worth examining, because bundling usually trades one problem for another. A single app that does nine things can be heavier than nine small apps. Vorssaint's answer to that is the Features page, which is the actual design idea here.

How the Features page turns a bundle back into separate tools

The README states that the Features page "installs and uninstalls whole features: what you uninstall disappears from the entire app and stops loading, so it spends no CPU, memory or energy." That is a stronger claim than hiding a panel. The feature is removed from the app's surface and stops consuming resources, and nothing is deleted: reinstalling brings the old settings back.

First setup offers three one-click bundles, Essentials, Windows, and Battery and quiet, plus a visual picker for individual features. Permissions are requested only for the choices made, which matters on macOS because screen recording and accessibility permissions are the usual friction point for tools that capture window thumbnails or synthesize keystrokes. The README also says every feature carries an energy badge describing what it keeps alive while on. That badge is the most useful part of the design for anyone deciding what to enable, because it puts the cost next to the toggle instead of in a support thread.

Beyond features, the rest of the interface is configurable in the same direction: panel sections reorder and hide, a compact layout trades sections for tabs, settings export to a file and import on a new Mac, the app can follow or ignore the system appearance, and the interface is translated into more than a dozen languages.

Installing Vorssaint and enabling a first feature

The README links to an Install section and to the Releases page, and the repository carries a build.sh at the top level plus a Package.swift, so a source build is possible for anyone with the Swift toolchain. The README does not spell out a Homebrew formula, so treat the Releases page as the distribution channel it points at rather than assuming a package manager command.

If you build from source, the repository layout suggests the standard Swift package flow from the checkout root. The exact product name is not given in the README, so run the build first and read the output rather than guessing a binary name.

./build.sh

After launching the app, the first-run flow is the part to pay attention to. You are offered Essentials, Windows, and Battery and quiet as one-click bundles, or you can pick individual features. Choose the smallest set that matches what you actually want, because the permission prompts that follow are derived from that choice. If you only want per-app volume, you should not be asked for screen recording.

The per-app volume feature is the clearest first test of whether the app fits your setup. The README says it works with "No audio driver, no setup," which means it does not install a kernel extension or virtual audio device. Open the mixer, adjust one app's slider, and confirm the change applies without affecting the Mac's overall output. If that works, the rest of the toolkit is likely to behave the same way.

The release channel is beta, and that is the main risk

The three most recent releases are v3.3.3-beta.3 on 2026-08-26, v3.3.3-beta.2 on 2026-08-22 and v3.3.3-beta.1 on 2026-08-22. Every release listed in the repository carries a beta tag. The repository is not archived and the last push was on 2026-08-26, so work is ongoing, but there is no stable release line to fall back on.

That matters more for this class of software than for a library. Vorssaint asks for accessibility and screen recording permissions, hooks into the Dock, captures window thumbnails and synthesizes keyboard shortcuts. Those are the areas where a regression is most visible and most disruptive: a broken app switcher or a Dock preview that stops updating is not a cosmetic bug. The README does not document rollback, and it does not describe a downgrade procedure, so a user who installs a beta and hits a regression has no documented path back other than reinstalling an older asset from the Releases page if one exists.

The beta tag is not automatically disqualifying. It is a statement about the project's own confidence level, and the changelog is the place to check what changed between builds before upgrading.

Where Vorssaint is the wrong tool

If you want one utility and nothing else, Vorssaint is the wrong shape. A single-purpose window snapper or clipboard manager will be smaller, and you avoid granting permissions to code paths you never enable. The Features page mitigates this by letting you uninstall modules, but the application is still one binary with one permission set, and the README does not describe per-feature sandboxing.

If you are not on macOS, there is no path at all. The feature list is built on the menu bar, the Dock, Spaces and the green maximize button, and the primary language is Swift.

There is a second, subtler case: anyone who needs a documented support contract or a stable release cadence. The release history shows beta releases only, and the README does not describe an LTS branch or a support policy. Teams that standardize on a tool for a fleet of Macs should look at the release history before committing, because the upgrade cost is real when a beta changes how the Dock or the app switcher behaves.

One more boundary: the README describes a Fan Control beta with continuous manual speeds and custom temperature curves. Fan control on Apple Silicon is a sensitive area, and the README does not describe thermal safeguards or an automatic fallback if the app stops responding. If that feature is why you are interested, verify its behavior yourself before relying on it.

Vorssaint versus Raycast and versus single-purpose Mac utilities

The most common comparison for a menu bar toolkit is Raycast, which people also search for alongside Vorssaint. The difference in approach is structural. Raycast is an extensible launcher: its core is a command palette, and its reach comes from an extension ecosystem and a scripting model. Vorssaint is not a launcher. It is a fixed set of native macOS utilities, each installable and uninstallable as a module, with no extension marketplace described in the README. If your need is a keystroke-driven command surface that you extend with your own scripts, Raycast is the closer fit. If your need is per-app volume, a system monitor with history graphs, Dock previews and window snapping that behave like system features, Vorssaint is aimed at exactly that.

Against single-purpose utilities, the trade is inverted. A dedicated clipboard manager or a dedicated window manager will do less, but it will also ask for fewer permissions and carry a smaller surface. Vorssaint's bet is that the Features page makes the bundle behave like separate tools. That bet is testable: uninstall a feature and check that its permission is no longer in use and its process is gone. The README claims the feature "stops loading," so that is the claim to verify rather than take on faith.

The related searches also list Boring notch and DockDoor. Both are narrower than Vorssaint: the first concerns the notch area, the second concerns Dock behavior. Vorssaint covers Dock previews and Dock clicks as one module among many, so it competes with them only if you already want several other features in the same app.

Licence, upgrade cost and what to check before you commit

Vorssaint is licensed under GPL-3.0 per the repository. That is a copyleft licence, and it is worth understanding before you build on the code rather than just run it. Running the app on your own Mac does not trigger distribution obligations. Redistributing a modified build, or shipping it inside a product, does, and the GPL-3.0 terms govern that. The repository also carries a TRADEMARKS.md file, which typically separates the code licence from the project name and logo. This is not legal advice; read LICENSE and TRADEMARKS.md yourself if you plan to redistribute anything.

The upgrade cost is the practical question. Releases arrive frequently, with three beta builds inside four days in August 2026, and the README does not describe an automatic update mechanism, a staged rollout or a downgrade path. Settings can be exported to a file and imported on a new Mac, which helps with migration but is not a backup of the app version itself. If you run Vorssaint on a machine you depend on, keep the older release asset around before upgrading, because that is the only rollback the README supports.

The privacy posture is the other thing the README is explicit about: no account, no telemetry and no subscription, with everything running locally. That claim is verifiable in a way the feature claims are not, since a local-only tool that asks for no account has nowhere obvious to send data. Check it the same way you would check any of this: watch what the app requests at the network level after install.

Editorial conclusion

Adopt Vorssaint if you want several small Mac utilities behind one menu bar icon and you are willing to accept a beta build: the newest release is v3.3.3-beta.3, published on 2026-08-26, and the README does not document a rollback path. Do not adopt it if you need a stable channel, a non-Mac platform, or a documented way to revert an upgrade. Before installing, check the Releases page for a non-beta build, read the energy badge on each feature you enable, and confirm which permissions your chosen bundle requests.

Frequently asked questions

Official sources

1. Official documentation
2. Official README
3. Project repository
4. Release notes