Elevarq Analyzer

Workbench is the surface you install and operate. It never connects to your databases: it stores its own state in an embedded database, ingests findings produced upstream, and presents them for you to triage and push into your ticket system. The component that reads your PostgreSQL is the Signals collector, using a read-only least-privilege role.

Everything is one-way and read-only toward your data: Signals reads statistics, Workbench pushes findings outward. Nothing writes back to your databases. This manual is organised the way you actually use docs — pick the box that matches what you need right now.

The four components

Elevarq is a platform of focused components. These four names appear throughout the manual:

• Elevarq Signals — the open-source, read-only collector that gathers the statistics PostgreSQL already exposes into a portable snapshot. Runs next to your database; never modifies it.
• Elevarq Analyzer — the commercial analysis engine that turns a Signals snapshot into prioritised, explained findings.
• Elevarq Workbench — the self-hosted, single-tenant web UI you install and operate: review findings, triage them, and push them to your tracker. When this manual says “deploy” or “the container”, it means Workbench.
• Elevarq Insight — the enrichment layer inside the Analyzer that explains findings and ranks recommendations. It is part of the pipeline, not a separately-installed product.

New here? Begin with the Get started tutorial. For background on what an evaluation looks like and how to read a finding, see the evaluation guide.