Monitor and update your WordPress sites from your own computer, over SSH and WP-CLI.
Nothing to install on your sites, no account, no hosted service.
Status: before 1.0. Vigie does everything listed below; its interface and its command line may still change.
Managing many WordPress sites usually means a dashboard plugin installed on every site, or an online service holding access to all of them. Both add an entry point to the sites they are meant to protect. Vigie takes another route:
- Agentless: it connects with SSH and runs WP-CLI on the server. Nothing is added to your sites.
- Local: a native app on your machine. No account, no hosted service, no open network port.
- Read-only by default: every action that changes a server shows what it will do first, asks for confirmation, and is logged.
- No stored secrets: your SSH keys stay in your SSH agent (1Password, Bitwarden, ssh-agent). Vigie never stores a password.
- Site manager: folders, hosts (one SSH account each) and sites, with colors, notes and tags
across folders. Every WordPress install of an account found for you; hosts imported from
~/.ssh/config, a CSV list, or FileZilla with the add-onvigie-filezilla. - Scans: WordPress, PHP and database versions, pending updates (core, plugins, themes, translations), known vulnerabilities, closed or abandoned plugins, files that differ from wordpress.org, administrators, TLS certificate and domain expiry, and what changed since the previous scan (a new administrator, a plugin installed outside Vigie).
- Multisite networks as one site, with the plugins, theme and administrators of each subsite.
- Safe updates, on one site or many: a backup first, then each item, the site checked after each one, and a rollback on failure; premium plugins included.
- Copies of a site on your computer: its database, its
wp-contentor the whole site, split into archives, resumed when cut off, read only on the server (docs/copies.md). - In the background: in the menu bar once the window is closed, scans at the interval you choose, notifications when a site turns urgent or a long run ends, and a journal of everything.
- Command line:
vigie scan,vigie updateand more, with JSON output and exit codes for scripts and cron. - Assistants: Claude or any other MCP client reads your sites, scans them and, if you allow it, updates them, each action waiting for your yes (docs/assistants.md).
- Add-ons: separate programs that bring hosts from other tools (docs/addons.md).
- English and French, dark and light, following the system.
| System | How |
|---|---|
| macOS (12 or later) | The DMG from the releases, or brew install --cask MarJC5/tap/vigie |
| Linux (x86_64, aarch64) | The AppImage, or the deb, rpm or Arch package, from the releases |
Vigie is not notarized by Apple: open it once, then System Settings, Privacy & Security, Open Anyway; afterwards it opens normally.
On your servers: SSH access with a key, PHP on the command line, and WP-CLI. When an account has no WP-CLI, Vigie offers to install it in its home folder (docs/security.md).
Updates: Settings, About says when a new version is out, with its notes, and installs it
when you click Install and restart; nothing is downloaded before. Each update is signed and
checked against the key built into Vigie. Installed with Homebrew: brew upgrade --cask vigie;
from a Linux package: your package manager.
Add a host with the + at the bottom left: its SSH details, its server key to check, a connection test, then the WordPress installs to add. Select a site, a host or a folder, and scan it. What needs you shows in the site list, in the overview of each site, and as a notification.
The same from a terminal:
vigie tree # the site manager, each site with its status
vigie scan "Clients/Shared hosting" # a site, a host or a folder; everything without a path
vigie scan --tag client-dupont --json # the sites with a tag, as JSON
vigie update "Clients/Shared hosting" # preview, then update, after you confirm
vigie copy "Clients/Shared hosting" --content database # a copy of each site on this computer
vigie export -o vigie-export.json # everything, to move to another computer
vigie mcp # for an MCP client, which starts it (Settings, Assistants)Exit status: 0 all good, 1 needs attention or not fully checked, 2 urgent, 3 error. vigie alone
opens the window. Homebrew links the command; from the DMG, Settings, General, Command
line shows the one command that links it; the Linux packages install /usr/bin/vigie.
Vigie keeps your data on your computer: no account, no hosted service, no telemetry. A security scan asks a few outside services what the server cannot tell (known vulnerabilities, closed plugins, domain expiry), and GitHub whether a new version of Vigie is out, from your computer and only after you agreed: each one is listed with exactly what it receives, and each one can be turned off in the settings. Those services never receive your sites' addresses. If you turn on an assistant (off by default), what it reads, your sites' addresses included, goes to the client you chose and usually on to the provider of its model (docs/assistants.md).
What Vigie reads, asks and sends: docs/security.md. To report a vulnerability: SECURITY.md.
- Security scans: what Vigie reads, asks and sends
- Updates: what Vigie does on a server
- Vigie in the background
- Data: what Vigie keeps, and its export format
- Add-ons
- Copies of your sites
- Assistants: Vigie in an MCP client
- Releasing Vigie
Each page is also in French, in docs/fr.
Issues and pull requests are welcome: CONTRIBUTING.md says how to build Vigie, run its tests and propose a change. Everyone taking part follows the code of conduct.
MIT.
Vigie is not affiliated with or endorsed by the WordPress Foundation. WordPress is a trademark of the WordPress Foundation.