QUERY
Ask anything about your infrastructure
Finding data is one thing. Getting meaningful answers is another.
The Problem
Even with an observational CMDB surfacing real data, raw data doesn't answer real questions. “What breaks if this node goes down?” “What changed since last Tuesday?” “Which infrastructure is going stale?” These require joining data across sources, traversing relationships, and reasoning about impact. Standard SQL wasn't designed for this.
The Solution
ParaQL is a dedicated query language designed for infrastructure intelligence. It understands relationships, impact paths, change history, and staleness natively. Ask in plain English or write precise structured queries. Either way, you get meaningful answers, not raw rows.

Real questions, real answers
ParaQL is built for the questions infrastructure teams actually ask.
What breaks if this host goes down?
SELECT name, ci_type, depth, path,
criticality, criticality_score
FROM IMPACT(proxmox.node, name LIKE '%pve%')
ORDER BY depth, criticality_score DESCWhat changed in the last 24 hours?
SELECT ci_name, change_type, changed_at FROM changes WHERE changed_at > NOW() - INTERVAL '24 hours' ORDER BY changed_at DESC
Show me the full infrastructure stack
SELECT node.name, vm.name, os.name FROM proxmox.node node <-[runs_on]- proxmox.vm vm <-[runs_on]- os.linux os
Which infrastructure is going stale?
SELECT name, ci_type, source, last_seen,
stale_for() AS staleness,
criticality, relationship_count() AS rels
FROM *
WHERE last_seen IS STALE BY INTERVAL '4 hours'
AND status = 'active'
ORDER BY criticality_score DESC
LIMIT 50How is each source contributing?
SELECT source, COUNT(*) AS total_cis,
SUM(relationship_count()) AS relationships,
SUM(change_count(INTERVAL '7 days')) AS changes_this_week
FROM *
WHERE status = 'active'
GROUP BY source
ORDER BY total_cis DESCNatural language
Ask in plain English. Parascope translates to ParaQL and returns real results, not documentation links.
Purpose-built syntax
IMPACT analysis, relationship traversal, staleness detection, and change counting are first-class operations, not bolted-on extensions.
Temporal queries
Query infrastructure state at any point in time. Compare snapshots, find when configurations diverged, audit past posture.
API-first
Every query available via REST API. Build dashboards, reports, and automations on top of your infrastructure data.
Search & Filter
Before you query, you need to find. Full-text search and logical filters let you locate any CI across your entire estate, combining conditions across type, source, attributes, and time.
Show me OpenStack instances or Proxmox VMs where the name contains “test” and memory exceeds 4 GB, created this month
Combine type filters, attribute conditions, and time ranges with AND/OR logic. Results update instantly as you refine.
Full-text search
Search across every CI by name, type, source, tag, or any attribute. Results ranked by relevance.
Logical filters
Combine conditions with AND/OR across CI type, source, status, criticality, and any configuration attribute.
Saved views
Save filter combinations as named views. Share across your team for consistent reporting and monitoring.