Platforms
Same binary, same UI, same fur commands across macOS, Linux, and Windows. The platform-specific layer is invisible by design.
Backend matrix
| Feature | Linux | macOS | Windows |
|---|---|---|---|
| Package install | Nix (Foxora OS) / apt·dpkg / pacman / Flatpak | Homebrew / Foxora registry | Scoop / winget / Foxora registry |
| Service management | systemd | launchd | Service Control Manager |
| Logs | journalctl + stdout capture | log + stdout capture | Event Viewer + stdout |
| Window chrome | Wayland / X11 | Cocoa | Win32 |
| Font rendering | fontconfig | CoreText | DirectWrite |
Per-platform notes
macOS
- Native window via
winiton Cocoa, traffic lights present. - ⌘-prefixed shortcuts.
- Services routed through launchd.
- Install source: Homebrew for system packages, Foxora registry for kits.
Linux
- Wayland preferred, X11 fallback.
- Ctrl-prefixed shortcuts (toggleable to ⌘ for muscle memory).
- systemd backend; on non-systemd distros a user-scope service runner ships in the binary.
- Install source: Foxora registry primary, apt / dnf / pacman fallback, Flatpak for desktop apps.
Windows
- Native Win32 window via
winit. - Ctrl-prefixed shortcuts.
- Services routed through the Service Control Manager.
- Underlying shell: PowerShell by default; WSL / bash optional.
- Install source: Scoop / winget fallback, Foxora registry primary.
What we don't promise
- Linux-specific features (eBPF, cgroups UI) won't appear on macOS / Windows.
- macOS-specific integrations (Keychain, Spotlight) won't appear on Linux / Windows.
- Windows-specific features (WSL control, Hyper-V) won't appear on macOS / Linux.
These are clearly labeled in fur help and hidden on platforms where they don't apply.
Same muscle memory
The bet: fur install postgres && fur service start postgres && fur logs postgres -n 20 work the same on every machine you SSH into.