Use the phone apps to check status, review findings and get alerts. Use the web app at app.safeguard.sh when you need the full interface with nothing to install. Use the desktop app for local work on a workstation, and the CLI or IDE extensions when you are building. Each surface fits a different moment.
What the download page lists
As of 19 October 2026 the download page lists:
- Mobile: an iOS app (App Store, version 2.0 shown) and an Android app (Google Play, plus an APK, 1.0.2).
- Desktop: version 3.2.2 for Windows, macOS and Linux.
- Web: app.safeguard.sh, no install.
- CLI: version 1.4.0.
- IDE extensions for VS Code, JetBrains and Open VSX editors.
- Browser extensions for Chrome and other Chromium browsers, Firefox and Safari.
The page describes the mobile apps as the same answers on a phone. It does not list a feature table for them, so use the App Store listing for the detail, which names posture, findings with reachability evidence, remediation tracking and alerts.
Decision table
- In a meeting and want status: phone.
- On call and an alert fired: phone first, then a laptop.
- New and want to look around: web.
- On a locked down machine where you cannot install: web.
- Working through findings for hours: desktop or web.
- Writing code: IDE extension.
- Scripting scans in CI: CLI.
- Reading a package page: browser extension.
Phone: glance and respond
The phone shines when the question is short. Did the fix land? Is that alert real? What is our posture this week? It is a poor place for long reading or configuration.
Web: nothing to install
The web app is the quickest way in, and it works from any machine where you can sign in. It suits people who only need occasional access, such as an executive sponsor or an auditor guest.
Desktop: local work
The desktop app is for the workstation. Note the Linux build on the page says it needs the Safeguard CLI installed and on your PATH, so plan for that if you run Linux.
Build tools: where scans start
Most of your scanning begins in the editor and pipeline. The extensions and CLI keep findings close to the change. The phone then reports on what those scans found.
A sensible combination
A common pattern for a small team: developers use an IDE extension and the CLI, the security lead uses the web app and phone, and CI runs the scan on every pull request. Nobody needs everything.
Quick check
Can I do everything from my phone?
No, and you would not want to. The phone listing focuses on posture, findings review, remediation tracking and alerts. Configuration and long investigations are easier on larger screens.
Sources
Last reviewed: 19 October 2026.
