The Elevarq platform
Infrastructure for operating PostgreSQL.
Elevarq combines read-only diagnostics, deterministic analysis, operational review, and production connection pooling into one PostgreSQL platform. Elevarq Analyzer is the flagship; each product does one job and hands off to the next.
Everything runs in your own infrastructure. See how the platform fits together ↓
One platform, two product families
Diagnostics understand the database. Operations run the infrastructure. Analyzer is the flagship of the diagnostics side.
PostgreSQL Diagnostics
Understand what the database is doing, and why it changed.
PostgreSQL Operations
Run the infrastructure the database depends on, in production.
The products
Each does one job. Together they cover both sides of operating PostgreSQL.
Elevarq Analyzer
Understand why PostgreSQL performance changes over time. Analyzer turns a Signals snapshot into evidence-grounded findings a reviewer can act on — the senior-DBA read of the database most teams don't have on staff.
Explore Analyzer
Elevarq Signals
Collect PostgreSQL evidence safely using a read-only collector — snapshots of execution stats, wait events, and configuration state, with no writes and no telemetry to Elevarq. Free on GitHub and AWS Marketplace.
Explore SignalsElevarq Workbench
Review, approve, and operationalize findings. The reviewer sees the cited evidence, adds implementation detail, and pushes a complete ticket to the tracker your team already uses.
See the workflow
pgAgroal Enterprise
Operate PostgreSQL connection pooling consistently across production Kubernetes environments — fleet inventory, hardened deployment, health-gated upgrades, and compliance evidence, with standard pgagroal underneath.
Explore pgAgroal EnterpriseTwo complementary paths to the same database
Elevarq operates PostgreSQL from two directions: understanding the database, and operating the infrastructure it depends on.
The diagnostics path never touches the query path — Signals reads statistics with a monitoring role. The operations path sits in the live connection path but is standard pgagroal, so the two run against the same database without competing for it.
Why we built both
We started with one recurring production problem: understanding why PostgreSQL performance changes over time. That is Analyzer, and the Signals collector and Workbench that feed and finish it.
Working in production environments surfaced a second problem that kept showing up next to the first — running connection pools consistently across Kubernetes fleets, through upgrades, without each team rebuilding the same safe defaults. That became pgAgroal Enterprise.
Diagnosing the database and operating its infrastructure are different jobs, but the teams doing them are usually the same teams. So both belong in one platform.
What's open source, what's commercial
The collector and the base pooler are free and production-ready. The commercial products are the operational layers built around them.
Open source
Free · production-ready- Elevarq SignalsBSD-3-Clause
- pgAgroal ContainerBSD-3-Clause
Inspect the code, run either standalone against any PostgreSQL — no license, no phone-home. Get Signals from GitHub releases or free on AWS Marketplace.
Commercial
Runs in your infrastructure- Elevarq AnalyzerFlagship diagnostics
- Elevarq WorkbenchReview & operationalize
- pgAgroal EnterpriseFleet operations
Offline-activated licenses, airgap-capable. Your data never leaves your environment.
The commercial products don't fork the open ones — fixes to the open collector and pooler go upstream. See the security page for the data-boundary model.
Start with the flagship, or the free collector.
Explore Analyzer to see how a snapshot becomes an implementable ticket, or download Signals and point it at your own database.
Operating pooling at scale? pgAgroal Enterprise · or talk to us.