Operational dashboard
Real-time operational dashboard
Live aggregations against the OLTP application source. Row-level security injected by the compiler — every user sees only what their grants allow.
Platform · Analytics & Reporting
Operational reporting and analytics, engineered into the runtime.
Page-perfect and pixel-perfect report rendering for regulated and statutory output. Business operational reports against live operational data. Drill-down across hierarchies and drill-across between data sources. Native SQL generation against analytical engines — Vertica, ClickHouse and BigQuery — for query workloads that warrant a columnar back end. All on the same platform, under one security perimeter, with the same audit trail.
Page-perfect, pixel-perfect output
Regulated invoices, statutory filings, audit packs and customer-facing documents rendered with the layout discipline production requires — not the rough sketch a generic BI tool produces.
Business operational reports
The reports the business actually runs the business with — sales registers, ageing schedules, stock movements, production yield, payroll registers — on live operational data, in real time.
Drill-down and drill-across
Drill down through hierarchies (group → company → entity → record), drill across between data sources (operational → analytical → external). Reconstruct any figure to its source in clicks, not project plans.
Native SQL for analytical engines
Queries compile to native SQL against Vertica, ClickHouse and BigQuery — not generic SQL that the engine then has to optimise. Performance characteristics of the chosen analytical engine surface in the result.
Page-perfect and pixel-perfect reporting
Where the layout is the deliverable — regulated, customer-facing or audit-grade output that has to render exactly as designed.
Pixel-perfect rendering
Page layout, font, table formatting, headers, footers, watermarks and pagination controlled at design time. The rendered output is the print artefact — not a screenshot of a dashboard.
Statutory and regulated output
Invoices, payroll registers, fiscal returns, statutory disclosures and customer-facing documents formatted to the standard the regulator or counterparty expects. The fiscal calendar drives the schedule; the engine drives the format.
Multi-format output
Same report definition renders to PDF (PDF/A for archival), XLSX, CSV, HTML, plain text — without redesign per format. Output channel becomes a runtime parameter.
Scheduled and event-driven generation
Reports generated on the fiscal calendar, on operational events, or on demand. Output routed by email, deposited on storage, surfaced in the application — handled by the same runtime.
Business operational reports
The reports the operation depends on every day. Not dashboards — reports, with the rigour and audit trail enterprise operations require.
Real-time operational reports
Sales registers, supplier ageing, stock positions, production yield, work-in-progress, cash flow — all running against live operational data, not against last-night's data warehouse extract.
Audit-grade traceability
Every figure on every report is traceable to its source record. Drill-through lands the analyst at the originating transaction, with timestamps, user identity and approval chain intact.
Multi-entity, multi-currency, multi-fiscal-regime
Group consolidations, entity-level views, currency translation, fiscal-regime parallel reporting (statutory and management views side-by-side). The reporting plane reflects the operational reality.
Role-aware visibility
The same report definition shows different data to different roles. Security expressions injected automatically; the report builder does not need to know the security model to honour it.
Drill-down and drill-across
Reconstructing a figure to its source is a property of the platform, not a feature added to one report at a time.
Drill-down through hierarchies
From group consolidation to legal entity to cost centre to GL account to the originating transaction — in clicks, not in queries. The hierarchy is configured once and applies across every report that touches it.
Drill-across between data sources
From an operational report to an analytical view on Vertica or ClickHouse, from a customer summary to an external CRM record, from an inventory position to the upstream supplier feed. Lateral movement across data sources is a property of the platform.
Cube drill-paths
OLAP cubes with configurable dimensions and hierarchies. Drill into a measure across any dimension; pivot the result; export the view; share it with a colleague. The cube is built once and serves every drill-path.
Audit trail follows the drill
Every drill-through is logged. Who looked at what, when, from where. The exploratory analytics surface is itself audit-grade.
Native SQL generation for analytical engines
When the workload warrants a columnar or MPP analytical engine, the platform generates native SQL against that engine — not generic SQL the engine then has to translate.
Vertica
Native MPP query generation — projection-aware syntax, segmentation hints, hash-distribution joins, optimiser directives. The query plan that runs is the plan the analyst would have written by hand, generated automatically.
ClickHouse
Native columnar SQL — MergeTree-family syntax, partition pruning, sampling clauses, materialised views. The platform compiles to ClickHouse-native, not to a generic SQL the driver then has to reshape.
BigQuery
Native Standard SQL with BigQuery-specific extensions — partitioned and clustered tables, ARRAY / STRUCT semantics, ML model invocation through SQL. Bytes scanned are minimised by query generation, not by manual tuning.
Mix-and-match by workload
OLTP stays on the application's operational engine. OLAP routes to the analytical engine the workload deserves. The same platform serves both; the analyst sees one query surface.
In the product
Analytics and reporting, as the user sees them
Dashboards, drill-down, OLAP and pixel-perfect output — from one platform, addressing three workloads. Placeholder screenshots; real captures land in this same carousel.
1 / 4
Why this matters
Enterprise analytics has fragmented over the past decade — one tool for pixel-perfect statutory output, one for executive dashboards, one for ad-hoc analysis, one for the data warehouse, one for the AI agents that try to read all of the above. Each tool has its own access model, its own pricing, its own lag. The operator paying for them rarely sees a single coherent analytical picture; the auditor sees four different versions of the same number.
Airtool collapses the stack. Page-perfect output, business operational reports, drill-down across the operational and analytical layers, and native query generation against the analytical engines that warrant a columnar back end all run on the same platform, against the same data, under the same security perimeter and the same audit trail. There is one number — visible in the operational report, in the executive dashboard, and in the analytical view — because there is one source of truth.