macOS
- Built with
- SwiftSwiftUI
- Runs on
- Apple silicon
- Built around
- How macOS handles files, permissions and privacy.
Desktop software that asks before it acts
Native software for macOS and Windows that handles files carefully. Plumb, our own Mac app, is written this way.
Mac, Windows and the command line
Windows
- Built with
- .NETWinUI
- Runs on
- Windows
- Built around
- A clean, signed install that feels at home on Windows.
Cross-platform
- Built with
- TauriElectron
- Runs on
- macOS, Windows and Linux
- Built around
- One app everywhere, renderer locked down, Node kept out of it.
Command-line tools
Fast, dependency-free CLIs with human and JSON output.
File and system utilities
Previews, dry runs and a way back before anything irreversible.
Signing and distribution
Code signing, notarisation and installers, planned from the first build.
Tools we use: Xcode, Visual Studio, nm and otool and Ghidra.
Plumb is built this way
Plumb
- 29 built-in protection rules that no setting, flag or environment variable can turn off.
- No background service and no login item.
Desktop software can reach files, other apps and sometimes the whole machine. We decide what it may touch before we write it.
Nothing irreversible by surprise
Designed against NIST SSDF and OWASP Desktop App Security Top 10.
From install to every run
Install
Signing and notarisation
Notarised on macOS, signed installers on Windows, from your accounts.
Updates
Signed updates
Over HTTPS, verified before they install.
Privilege
Least privilege
No admin password, helper or background service unless a feature needs one.
Files
File handling
Symlinks never followed blindly, and a dry run before anything irreversible.
Processes
Messages between processes
Validated at the boundary. Each helper does one job.
Web views
Locked-down web views
No Node in the renderer, isolated contexts, strict CSP.
Questions
Is Plumb built this way?
Yes. A native SwiftUI app for Apple silicon, in development and not on sale yet. It removes nothing without a review and a dry run, and needs no administrator password.
Tauri or Electron?
Tauri when a small install and a locked-down renderer matter most. Electron when you need its ecosystem. Either way: no Node in the renderer, a strict CSP, and every message between processes validated.
Tell us about your desktop app.
Mac, Windows or both, and what it may touch on the machine. Then a written quote.