Windows, Linux, Docker.
Windows service via the bundled installer. Linux via systemd unit. Docker image with documented compose.
A small Windows or Linux agent. Holds the real connection string locally. Opens outbound TLS to the cloud. Runs documentation scans, ad hoc queries, and scheduled exports. Nothing inbound, explicit result delivery only.
Windows service via the bundled installer. Linux via systemd unit. Docker image with documented compose.
Persistent SignalR connection over HTTPS. No inbound ports. No firewall changes beyond outbound 443.
The browser seals the connection string with the agent public key. The cloud stores the envelope. The agent opens it locally.
What the agent does
Read information schema and provider catalogs to feed the documentation and the change history.
Execute saved or freeform SELECT statements you authored, under read-only role and timeout.
Run a saved query on schedule, format as CSV or Excel, push it to the cloud for delivery to Slack or email.
Capacity
A team that runs three databases does not need three agents. Concurrency caps protect the agent host and the customer database from spikes during scheduled run windows.
Default cap on a 4 vCPU host. Tunable.
Avoid hammering one database with parallel diagnostics.
Per-connection schedule. Run-now button when you do not want to wait.
FAQ
Outbound 443 to the control plane. Nothing inbound. The agent opens a long-lived SignalR connection and keeps it warm with heartbeats.
Yes. Many teams run it as a sidecar on the database host or on a small jump host with network access to the database.
Replace the binary, restart the service. The agent reports its version on connect; the cloud blocks versions below MinAgentVersion.
Yes. Multiple agents can be enrolled. The cloud picks one for each scheduled run via a lease. Two agents racing to scan the same database will not duplicate work.
Windows, Linux, Docker. Outbound 443. The first scan finishes in under ten minutes.