Elevarq Professional Cloud is a senior-DBA read of your PostgreSQL and TimescaleDB databases, delivered as fixes your team can ship - running entirely in your own AWS account. Performance and reliability problems build up quietly, and most teams have no senior database expert on hand. Elevarq is built on decades of human PostgreSQL and TimescaleDB expertise that trained its AI and grounds it with deterministic rules - so it finds the risks, explains them with evidence and a confidence score, and prepares the exact change, including the SQL and how to roll it back. Every finding arrives as a ready-to-ship ticket in GitHub, GitLab, Jira, or Linear. It is read-only, never touches your production database, and sends no telemetry; your data never leaves your environment. Up to 5 databases per instance.
Performance and reliability problems build up quietly in PostgreSQL and TimescaleDB, and most teams have no senior database expert on hand - so a checkout query slowed by a missing index, creeping table bloat, or a risky setting goes unnoticed until it becomes a production incident. Elevarq Professional Cloud gives you that expert on demand, running entirely in your own AWS account.
Expert intelligence you can trust
Elevarq is built on decades of human PostgreSQL and TimescaleDB expertise - the judgment of experienced database engineers and the documentation they rely on. That expertise trained Elevarq's AI and grounds it with deterministic rules, so every finding is evidence-based and explainable, not a guess. Elevarq finds the risk, explains it, scores its confidence, and prepares the exact change: the SQL to apply and how to roll it back. Elevarq proposes; your team reviews and decides.
Lands in your team's workflow
Every finding arrives as a complete, ready-to-ship ticket in GitHub, GitLab, Jira, or Linear - reviewed and shipped in your normal ticket workflow, not a separate tool.
Read-only, in your own environment
Deploy one self-contained container on EKS, ECS, or EC2 in your own AWS account.
Works with the PostgreSQL and TimescaleDB you already run - self-managed or managed, including Amazon RDS.
Read-only: Elevarq never touches your production database and sends no telemetry. Your statistics, SQL, findings, reports, and analysis never leave your environment.
Assess - Elevarq's expert-trained, rule-grounded intelligence turns each snapshot into prioritized, evidence-grounded findings on your schedule.
Ship - findings appear in the built-in Workbench UI and as tickets in your issue tracker, each citing the evidence and the exact recommended change.
What Professional Cloud includes
Up to 5 databases per instance, assessed and reported sequentially.
Persistent state (findings, reports, history, settings) retained across upgrades and restorable onto replacement compute.
Pay for what you run
Billed per instance-hour: run one instance or many, start and stop them as your workload changes, and pay only for the hours each runs. Larger, parallel workloads are served by Elevarq Business Cloud.
Highlights
Decades of human PostgreSQL and TimescaleDB expertise trained Elevarq's AI and ground it with deterministic rules - so every finding is evidence-based, not a guess.
Every finding arrives as a ready-to-ship ticket in GitHub, GitLab, Jira, or Linear, with the exact change and rollback.
Read-only and runs entirely in your AWS account - never touches production, sends no telemetry, your data never leaves your environment.
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
This listing bills on a single usage dimension: container hours. You pay for each hour the software container runs in your environment. There are no tiers or instance sizes to choose from here. Your cost scales directly with how long the containers stay running. The product deploys as containers you run in your own infrastructure. Because billing is tied to runtime hours, your total depends on how many hours you keep the containers active over the billing period.
Top-of-mind questions for buyers
What counts as one container hour for billing?
You are billed for each hour a software container runs in your own environment. The product ships as four container components that deploy as a single unit. Each hour any billed container stays active adds to your total. Counting is based on runtime, not on the number of databases analyzed.
Am I charged when the containers are stopped or idle?
Billing meters container runtime hours, so charges accrue only while containers run. If you stop the containers, hours stop accruing. Because analysis runs on a schedule you set, you control how long containers stay active. A busy database does not cost more than a quiet one on the same runtime.
Does the number of databases I analyze change my hourly cost?
No. The one billing dimension is container hours, not databases. Your cost depends on how long the containers run, not how many databases you point them at or how much you use them. There is no per-token billing and no usage cap tied to database activity.
elevarq.com+2
Helpful?
Vendor refund policy
Refund requests made within 14 days of your initial subscription are reviewed on a case-by-case basis. To request a refund, email support@elevarq.com with your AWS account ID and subscription details; we aim to respond within 2 business days. Usage charges (per instance-hour) already incurred are refunded at our discretion via AWS Marketplace.
How can we make this page better?
Tell us how we can improve this page, or report an issue with this product.
Give us feedbackReport a problem with this product or seller
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA).
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
Helm charts are Kubernetes YAML manifests combined into a single package that can be installed on Kubernetes clusters. The containerized application is deployed on a cluster by running a single Helm install command to install the seller-provided Helm chart.
Version release notes
Elevarq Professional Cloud: Analyzer rules engine + built-in Insight AI model (medium-gpu, baked) + Workbench operator UI in one container. Up to 5 databases, sequential reporting. Billed per running instance-hour through your AWS Marketplace subscription - no license keys, no activation.
Additional details
Usage instructions
Deploy Elevarq Professional Cloud on Amazon EKS (metered)
Elevarq installs as ONE container (Analyzer rules engine + built-in medium-gpu AI model + Workbench UI) from a single Helm chart. Your AWS Marketplace subscription authorizes the product and bills per running instance-hour; there is no license file.
Prerequisites
An Amazon EKS cluster (Kubernetes 1.28+) with kubectl configured, a default StorageClass, and at least one NVIDIA GPU node (the medium-gpu model runs on GPU).
Helm 3.8+ (OCI registry support).
No IAM setup for metering: AWS Marketplace injects a metering service account (with aws-marketplace:RegisterUsage) into your EKS deployment automatically.
Snapshot evidence produced by the FREE Elevarq Signals collector (its own AWS Marketplace listing); Signals is the only component that touches database credentials - this product never does.
Step 1 - Authenticate Helm to the Marketplace registry (the login token is fixed to us-east-1 regardless of your cluster region):
aws ecr get-login-password --region us-east-1 | helm registry login --username AWS --password-stdin 709825985650.dkr.ecr.us-east-1.amazonaws.com
Step 2 - Create the namespace and the master-key Secret (the ONE required runtime secret - KEEP IT SAFE):
kubectl create namespace elevarq
kubectl -n elevarq create secret generic elevarq-master-key --from-literal=masterKey=$(openssl rand -hex 32)
Step 3 - Install (AWS Marketplace injects the metering service account automatically):
helm install elevarq oci://709825985650.dkr.ecr.us-east-1.amazonaws.com/elevarq/elevarq-professional-cloud-metered-chart --version 0.1.1 --namespace elevarq
The chart creates PersistentVolumeClaims (Workbench store, instance identity, Analyzer state, snapshot inbox) on the default StorageClass; set storage.*.existingClaim to bring your own.
Step 4 - Ship snapshots and verify:
Ship export ZIPs from Elevarq Signals into the snapshot inbox PVC (mounted at /var/lib/elevarq/snapshots); the analyzer runs per snapshot.
kubectl get pods -n elevarq : the pod becomes Ready once the supervisor has registered usage with AWS (RegisterUsage), booted Insight (first model load takes a while) and Workbench, and started the analyzer runner. A missing/invalid subscription or a mis-scoped IAM role fails closed (the pod does not become Ready).
Access Workbench over HTTPS ONLY: front the ClusterIP Service (port 8080) with a TLS-terminating ingress or load balancer. Only port 8080 is exposed; the Insight API is loopback inside the container.
Connect up to 5 databases; reports run sequentially (one at a time).
Billing
AWS meters each running instance hourly under your subscription; run more instances for more throughput (each adds its own 5-database capacity). Stop the workload to stop metering.
Configuration and support
Documentation is built into the product (Workbench serves it at /docs, offline). Support: email support@elevarq.com with your AWS account ID and product version.
Email support at support@elevarq.com. Documentation covers deployment (EKS/ECS/EC2), IAM setup, connecting databases, workflow integrations (GitHub/GitLab/Jira/Linear), upgrades, and backup/restore.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Read-only PostgreSQL diagnostic signal collector, pre-installed on Amazon Linux 2023. Passwordless RDS IAM, verify-full TLS, least-privilege, no data egress.
Local-first, read-only PostgreSQL diagnostic collector. Passwordless onboarding to Amazon RDS and Aurora over verify-full TLS, with no diagnostic-data egress to Elevarq.
Elevarq pgAgroal Enterprise operates standard pgagroal at fleet scale - hardened,
managed, promptly patched, and supported - so teams get a modern PostgreSQL
connection-pooling platform without running it themselves. It builds on standard
upstream pgagroal as its base: the same fast pooler, plus a closed enterprise control
plane for fleet config, policy and drift detection, Kubernetes lifecycle automation
with zero-downtime rolling drains, coordinated global connection limits, audit and
compliance export, and cloud secrets-manager integration. Images are signed, ship an
SBOM, and are rebuilt and re-scanned on every public pgagroal fix under a documented
CVE-response SLA. Designed for auditability and built to support your compliance
readiness.
Be the first to review this product. We've partnered with PeerSpot to gather customer feedback. You can share your experience by writing or recording a review, or scheduling a call with a PeerSpot analyst.