Updates & support
Elevarq runs inside your infrastructure. This page describes the ongoing operating relationship — how releases, patches, security advisories, compatibility, upgrades, and support work — so you can plan the software into production with your eyes open.
How Elevarq is maintained
Two maintenance models sit side by side, and the difference matters when you plan support.
Elevarq Signals and the pgAgroal Container are open source. Releases, changes, and fixes are published in the open on their public repositories, and anyone can read the code, file issues, and follow the changelog. Community maintenance carries no individual support commitment.
Elevarq Analyzer, Elevarq Workbench, and pgAgroal Enterprise are licensed commercial products. They ship with a direct support channel to Elevarq; the scope is agreed with each customer as part of the licence, not a one-size-fits-all tier.
Releases and patches
How new versions and fixes reach you.
- Versioned releases. Every product is released under semantic versioning, so a version number tells you whether an upgrade is a patch, a compatible addition, or a breaking change.
- Published changes. Open-source releases carry public release notes on GitHub releases. Commercial releases ship with release notes and the upgrade guidance linked below.
- Security patches are prioritised. When a fix affects the security of a supported version, it is handled through the advisory process below rather than waiting for the next feature release.
We do not publish a fixed release cadence or a guaranteed patch window. Releases are driven by readiness, not a calendar.
Security advisories and vulnerability response
One channel, coordinated disclosure.
To report a vulnerability, email security@elevarq.com. We acknowledge receipt and coordinate disclosure with you. Security fixes for supported versions are prioritised over feature work. See the security page for the full data-handling and deployment posture your reviewers will ask about.
Supported versions and compatibility
What each product runs against, and which versions get fixes.
Elevarq targets supported, in-maintenance PostgreSQL versions; end-of-life PostgreSQL releases are outside the supported range. Container products state their Kubernetes compatibility in their documentation. Fixes — including security fixes — are delivered to currently supported product versions; upgrading to a supported version is the path to receiving them.
See the Analyzer compatibility page and the per-product documentation for the exact supported matrices.
Upgrades, rollback, and deployment
How you move between versions without surprises.
Because Elevarq runs in your environment, you control when and how you upgrade. Documentation covers the upgrade steps, the changes to expect, and how to roll back to the prior version if you need to.
Air-gapped and offline delivery
Elevarq is built to run where the internet does not reach.
Signals collects entirely inside your network and can run fully air-gapped — nothing leaves your environment. Analyzer supports offline licence activation for disconnected deployments. Updates for air-gapped installations are delivered as artifacts you import on your own schedule.
Commercial support channels and scope
What licensed customers get, described honestly.
Licensed customers of Analyzer, Workbench, and pgAgroal Enterprise have a direct support channel to Elevarq for installation, configuration, upgrades, and defect reports. Support scope is agreed with each customer as part of the engagement. We do not publish a 24/7 promise, a service-level agreement, or a response-time target we cannot yet stand behind — where those commitments are needed, we agree them in writing with the customer.
To discuss support for a production deployment, contact us or book a technical review.
Documentation, security, and release notes
Where to go next.