Security work does not happen in one place. You read a notification on the train, triage at a desk, fix code in a terminal, and glance at a wall screen in the afternoon. A tool that only works in one of those moments gets used in one of those moments.
Safeguard is built to run across all of them with the same account and the same data. This post is a map: what each surface is for, and how to choose.
For current downloads of anything below, use the download page.
What it is
Every surface talks to the same Safeguard. A finding you see on your watch is the finding you see in the web app and the one the CLI reports. Nothing is a lite copy with its own data.
The web app at app.safeguard.sh is chat-first. You ask Griffin, the platform answers, and the platform can be driven from chat. Voice commands are supported. Every other surface is a different way into that same system.
The map
| Surface | Best for |
|---|---|
| Web app | Everything. The full workspace, and the default place to start. |
| Desktop | A dedicated window for Safeguard, with the option to connect to a local runner. |
| Phone | Notifications, quick questions, voice. |
| Tablet | Triage and review in a meeting or on a couch. |
| Watch | Seeing a critical alert and a quick decision. |
| TV | A wall display for awareness. |
| Headset | Large canvas sessions and group walkthroughs. |
| Browser extension | Security context beside the page you are reading. |
| IDE extension | Insight as you write code. |
| CLI | Scans and gates in terminals and CI. |
| MCP | Safeguard from inside Claude, ChatGPT, Cursor or your own agent. |
How to choose
Ask what your hands and eyes are doing.
- Typing code: IDE or CLI.
- In a pipeline: CLI, with SARIF or JUnit output.
- Away from a desk: phone, then watch.
- In a meeting: tablet or headset.
- Passing by a screen: TV.
- Already inside an AI assistant: MCP.
Control for admins
More surfaces means more places to keep tidy. Tenant admins can switch off any client type, including desktop, mobile, CLI, runners, IDE, browser extension and MCP clients. If you do not want watches or TVs in your environment, you can say so once, centrally.
Try it yourself
Write down the five places you were last time a security issue interrupted you. Match each to a surface in the table. The gaps are where your current process loses time.
Quick check
Does each surface have its own copy of your data?
No. All surfaces use the same Safeguard account and data.
How do you restrict which surfaces people can use?
Tenant admins can switch off any client type centrally.
