Monitor SQL Server, Oracle, PostgreSQL, and MySQL fleets from one dashboard. Self-hosted, zero outbound telemetry, unlimited servers on every paid edition.
Latest changes
More…- Oracle's "latest Release Update" is now derived from Oracle's fixed quarterly cadence (19c → 19.33, 26ai → 23.26.4 for Oct 2026) instead of a hand-maintained value that drifted stale — Oracle publishes no machine-readable RU feed, so the schedule is the source of truth.
- MySQL patch baselines now list LTS releases (8.0, 8.4, 9.7) separately from the Innovation track, so a 9.7 server is compared against the latest 9.7.x build instead of being nudged onto a different support track.
- Added a Patch Baselines view under Settings: a read-only table — grouped by SQL Server, PostgreSQL, MySQL and Oracle — of the latest known version/build the Patch Currency check compares your servers against, each with a link to its source.
- Settings → Telemetry now names and links the source behind each Patch Currency fetch — SQL Server builds from sqlserverbuilds.blogspot.com, Postgres from postgresql.org, MySQL and Oracle from endoflife.date — so you can see exactly where the numbers come from.
- Reworked DBA Deployment's script-group selection: the checked scripts are the deploy set directly (no separate confirm step), with Select all / none and a live "Deploying X of Y scripts" readout of exactly what will run.
- Added a "source" link to every DBA Deployment script — third-party sources open their public GitHub page, and SPP's own bundled installers open the exact script that would run, so you can read it before you deploy it.
- SQL Server's percentage-autogrowth checks now skip the system databases (master, tempdb, model, msdb), which ship that way from Microsoft — no more guaranteed false positive on every server.
- Credential Manager now hides each engine's built-in superuser (sa, root, postgres, SYS/SYSTEM) from the account scan, and adds Disable and Enable actions so a departed user's login can be locked out — reversibly, without dropping the account.
- Added an Export button (Excel or CSV) to the Estate Overview that respects your current filters and sort, with columns laid out to drop straight back into the file importer.
- SQL Server's patch-currency check now reports the full installed build next to the CU label, so it lines up with the baseline build you compare it against.
Five ways to see your fleet of servers
Same estate, five layouts — pick whichever reads fastest for how you work, in whichever of the nine themes suits your eyes.
Every engine, one pane of glass
SQL Server, Oracle, PostgreSQL, and MySQL — the same Estate Overview grid, the same alert model, no per-engine tooling to learn.
Self-hosted, zero telemetry
Runs entirely on your infrastructure. Nothing about your estate, usage, or license status is ever sent off-box.
Unlimited servers on every paid edition
Paid licensing is by capability, not server count — monitor 5 servers or 5,000 on the same license. The free Personal edition is capped at 2.
Role-based from day one
A seven-role capability model — viewer through admin — so the right people see the right pages, nothing more.
Built by DBAs, for the multi-engine reality
SPP Command Deck started life as a SQL Server–only monitor. But any medium or large environment eventually ends up with more than one database engine in production — Oracle, Postgres, MySQL creep in alongside SQL Server — and a DBA ends up bouncing between four separate tools just to get a straight answer on fleet health. The big-name platforms that do cover every engine price by the server, per year, which prices out exactly the teams whose estates are big enough to need it and whose budgets haven't kept pace. This app exists to close that gap.
Nine built-in themes
Light and dark, tuned for long shifts staring at a wall of servers. Switch per-user, no reload required.
See the full tour →
Start monitoring in minutes
Personal edition is free forever for non-commercial use. No account, no card, no call.