Real-time SQL Server monitoring, AI-assisted query analysis on the on-prem roadmap, and audit-ready telemetry for utility-scale workloads — deployed inside your perimeter, air-gap capable, never routed through a public cloud. Built for the databases that run grid telemetry, AMI, outage management and customer information at utility scale.
Three pressures that turn utility database observability from an engineering tool into a regulator-level and revenue-level concern.
Smart meters now generate billions of reads per day. The databases ingesting, retaining and reporting on them weren't sized for AMI when they were procured. Performance degrades silently — until a regulator asks for a meter-data report that times out.
SaaS-only monitoring tools cannot run inside critical-infrastructure environments. Shipping grid telemetry to a US public cloud is a non-starter under NIS2, national CI laws and most utility regulators' security baselines.
When the CIS or OMS database slows down, customer-facing outage maps go stale and call centers light up. Legacy tools alert after the SLA is missed — DBAs are the last to know and the first to be blamed.
Four workloads where sovereign deployment, air-gap capability and utility-scale architecture are non-negotiable.
Smart-meter platforms write hundreds of thousands of reads per minute into SQL Server. DPM tracks ingestion latency, blocking and plan-cache regressions in real time — so a spike in inbound meter traffic doesn't silently corrupt the billing window.
When OMS database queries slow down, restoration estimates go wrong and field crews are misdirected. DPM baselines normal OMS query duration and alerts on regression before dispatchers notice the lag.
The CIS is where billing, customer service and outage reporting meet. DPM watches the entire SQL Server estate behind your CIS — clusters, AGs, replicas — from one console, with no cloud relay.
NIS2 requires demonstrable supply-chain risk control over critical ICT services. Avesys runs entirely on your hardware, with on-prem AI inference on the roadmap — NIS2 supply-chain risk addressed by design, not by attestation.
DPM watches every monitored instance against thresholds you set and baselines it learns. When AMI ingestion drifts, an OMS query slows or a CIS plan flips, the alert lands in the channel the on-call DBA already lives in — entirely inside your network.
Three numbers a CISO, a DBA lead and a regulator all care about — the cost, the overhead, the supply-chain path. Avesys moves each one in the right direction.
One number. No per-database tax, no metric-by-metric upsell. Onboarding the next 30 instances costs what onboarding the last 30 cost — easy to model, easy to defend in a budget review.
The agent is engineered to disappear. Sub-1% CPU on production instances means you can monitor your busiest AMI ingestion database the same way you monitor a BI OLAP node — without becoming the cause of the slowdown.
No outbound API calls. No shared cloud tenancy. The console, the collector and the AI roadmap all run inside the utility perimeter — supply-chain risk addressed by design.
Three architectural calls that separate database observability built for regulated, critical-infrastructure utilities from a generic monitoring tool.
No cloud relay. No outbound telemetry. The collector agent sits next to your SQL Server instances and the console runs inside your network. NIS2 supply-chain risk addressed by architecture.
Designed for SQL Server clusters processing AMI meter reads, OMS dispatch and CIS lookups. Sub-1% overhead even during real outages — the worst time to add observability load.
€650 per instance per year. Predictable as your estate grows. Pricing scales linearly with AMI rollouts and acquisitions — no per-database tax, no metric-volume billing, no surprise renewal math.
The founders previously built and operate EST10, an enterprise data management consultancy with five years of experience running mission-critical SQL Server estates for regulated, large-enterprise clients. Avesys is the productization of that experience — built so a utility or grid operator can deploy modern observability without shipping a single byte of grid telemetry to a foreign cloud.
The platform was designed against the bar a serious utility deployment clears — NIS2-aligned, air-gap capable, sub-1% overhead during real outages, and pricing that scales with the estate.
Not a feature checklist against other vendors. The bar a serious utility-grade platform clears — and what we built Avesys to deliver from day one.
Per-instance pricing, every year. Everything DPM ships today — wait stats, blocking, queries, fleet view, alerting, the lightweight collector — included.
One annual fee per monitored instance. Whether the instance powers AMI ingestion, OMS dispatch, CIS or BI — same number, same product, same agreement.
Roughly the SQL Server footprint of a regional electricity or gas utility — AMI, CIS, OMS and BI. Full DPM feature set on every instance.
Same per-instance number — the only thing that changes is how many instances you're monitoring. Procurement-ready: the line item scales linearly with the estate.
Three low-friction ways to start a conversation. Whichever you choose, you'll land on a 15-minute call with someone who has actually been on-call for a utility SQL Server estate.
