Frequently asked questions

A self-hosted dashboard for monitoring a fleet of SQL Server, Oracle, PostgreSQL, and MySQL instances from one place. It runs entirely inside your own infrastructure — zero outbound telemetry — and covers everything from a two-server home lab to a few hundred production instances.

Pull the pre-built images and run "docker compose up -d" — no source checkout, no build toolchain. Open http://localhost:8078 and the setup wizard walks you through creating the first admin account. See the Download page for the exact steps.

SQL Server, Oracle, PostgreSQL, and MySQL, on every edition — engine support isn’t a paid upsell.

Personal is free forever for non-commercial use: up to 2 monitored instances, the built-in admin account only (single user), manual monitoring runs, and no alerting. Lite adds the full alerting bundle, multi-user team accounts, and a commercial-use license. Professional adds unlimited servers, custom reports, a fleet-wide credential manager, DBA deployment tooling, patch-currency tracking, and API access.

Yes — the Evaluation edition unlocks every feature (everything in Professional) for 30 days, no credit card required. At day 30 it automatically downgrades to Personal with no reinstall and no data loss; anything you set up during the trial stays in place, just locked behind whatever tier you end up on.

Use the Add/Edit Server dialog and click Test Connection before saving. If you’re adding a lot at once, import directly from a SQL Server Central Management Server, or bulk-import a CSV/XLSX inventory template instead of adding servers one at a time.

A compact grid of every monitored server, colored green/yellow/red by health status, filterable by engine and environment. It’s built to stay readable at a few hundred servers, not just a dozen. Click into any tile for the four-panel Server Detail dashboard, where each panel can show raw values or a detail grid.

On Personal, monitoring runs are manual by design — you trigger each refresh yourself. Automatic background refresh comes with the paid editions, which also unlock alerting so you don’t have to be watching the dashboard when something crosses a threshold.

Starting at Lite, you can tune warning and critical thresholds per check and per environment (production and dev don’t have to alert the same way), and route notifications through Email, Pushover, Slack, or Microsoft Teams, with suppression rules for known/expected conditions. Turning it on for the first time runs a short migration wizard that sets up the dedicated alerts database your thresholds and notification history live in.

Personal is single-user (the one built-in admin account). Team accounts start at Lite, with seven built-in roles ranging from read-only viewer to full admin, each with its own page access and execution capabilities, issued as real OIDC claims rather than a simple flag.

Full refund within 14 days of purchase, no reason required — request it directly from the receipt Stripe emails you at checkout.

By capability, not server count or seat count. A paid license unlocks a tier of features for one install. Licenses are perpetual: the software keeps working even if maintenance lapses, you just stop receiving updates until it’s renewed. Maintenance renews yearly at 25% of the license’s (non-sale) upfront price after the included period expires.

The license key is the thing you actually hold — one per install you’ve purchased. Behind it, the app generates a hashed fingerprint of that specific machine/install and binds your signed license file to it. Verification happens entirely locally (signature + fingerprint check) on every run — there’s no license server your install has to phone home to.

Yes, but not silently — because there’s no license server tracking activation state in real time, moving a key to a new install goes through an out-of-band reissue: you submit the new machine’s fingerprint through the same channel used for the original purchase, and a new signed license file gets issued bound to it. The old install’s binding isn’t renewed. This keeps reissues tolerant of normal reinstalls/hardware swaps without turning into an unmetered activation pool.

Evaluation state is deliberately persisted in more than one protected location, so removing a single file can’t roll the 30-day clock back. Strict fingerprint locking is reserved specifically for evaluation-abuse prevention, where the stakes of a false lockout are low — paid-license reactivation is handled more tolerantly, since a legitimate customer swapping hardware shouldn’t get punished the same way.

No, by design — this is self-hosted with zero outbound telemetry. The only outbound traffic the app itself generates is to the database engines you point it at, and, if you’ve configured alerting, to whichever notification channels you’ve set up (Email/Pushover/Slack/Teams).

It fetches and stages well-known community scripts you already trust — sp_WhoIsActive, Brent Ozar’s First Responder Kit, and Ola Hallengren’s maintenance solution — directly from their original upstream sources, then lets you run them against a multi-select grid of servers with audit logging. SPP Command Deck bundles and automates running them; it doesn’t author or warrant their behavior.

Every edition already lets you store connection credentials per server. Professional adds a separate fleet-wide Credential Manager view on top of that — see every stored credential across the whole estate at once, with rotation support, instead of checking servers one at a time.

Professional includes API access, so you can pull fleet data or drive actions from your own scripts and tooling instead of going through the dashboard UI for everything.

Professional’s Patching page compares each monitored server’s live build/edition/patch level against the latest known cumulative-update baseline for its engine, so you can see what’s behind across your entire fleet — SQL Server, Oracle, PostgreSQL, and MySQL alike — in one place instead of checking each engine’s own tooling separately.