Products · 02 · Business Intelligence
← All products

Qrly

Ask. Build. Share. Self-service business intelligence, on your own infrastructure.

Connect a database, ask a question, and build a report, a chart or a dashboard — that is the whole system, until you need more. Qrly also carries a full spreadsheet engine, four cache and replication tiers, an approval-gated AI agent workforce, and a productised BCBS 239 risk-data governance module that no other BI platform ships.

40Connection types
13Visualisation types
500Worksheet functions
14Principles governed
The problem

Self-service analytics stops being self-service the moment it matters.

The tool is bought so business users can answer their own questions. Six months later every meaningful number still routes through two data engineers, the important reporting has migrated back into untraceable spreadsheets, and the AI features meant to help are the ones the risk function will not approve — because nobody can say what the model was told, or what it changed.

01
Engineer bottleneck
Every new question is a ticket. The tool's promise dies in the queue.
02
Shadow spreadsheets
The real reporting lives in files with hand-typed columns beside a stale export.
03
Unauditable AI
A model that writes queries and saves content, with no record of the prompt or the change.
04
Governance as a project
Data lineage, critical data elements and quality rules assembled by hand in documents.
The solution

A BI platform that takes governance as seriously as it takes charts.

01
Query without SQL
A point-and-click definition compiled into dialect-correct SQL for around forty database types, with drill-down, calculated fields, and a converter that turns hand-written SQL back into the visual builder.
02
Spreadsheet, properly
Not an export button — a real grid with around five hundred worksheet functions, four conditional-formatting families, and refresh-safe blocks that keep your hand-written columns beside their record when the query reorders.
03
Governed by construction
Every query, every AI prompt, every agent tool call and every schema change is written to an audit table. Schema authoring is off by default at three independent levels.

Capabilities

01Data Connectivity & Querying
  • Around forty connection types — PostgreSQL, MySQL, SQL Server, Snowflake, BigQuery, Redshift, Databricks, Trino, ClickHouse, DuckDB, Synapse, Vertica, DB2, Sybase and more.
  • A visual builder covering tables, joins, filters, aggregations, grouping, sorting and limits — no SQL required — alongside a schema-aware SQL editor with completion, hover and formatting.
  • A converter turns hand-written SQL back into the visual builder, so a hand-written query is not a dead end.
  • Fourteen filter operators plus date helpers for week, month, year and rolling windows; calculated fields usable anywhere a column is, sanitised against anything that is not a read.
  • Nightly schema introspection with cached columns and foreign keys, a data dictionary and an entity-relationship view, plus freshness probes for a 'data as of' status.
  • Per-connection pooling, query timeout, row limits, a concurrency governor with a wait queue, SSH tunnels, TLS modes, and a guard against reaching internal hosts; every credential encrypted at rest.
  • Drill-down in two modes — to underlying rows, or narrowed to the selected group — on visual and native queries alike.
02Dashboards & Delivery
  • Thirteen visualisation types including pivot, funnel, gauge, progress and both regional and point maps, with a semantic model layer for dimensions, measures, rollups and period-over-period comparison.
  • Twelve-column dashboards with drag and resize, dashboard-level filters, auto-refresh, and cascading filters that drive many cards with differing field names.
  • Live dashboards pushed on an interval, or driven by a change notification from the source database itself; a morning briefing that diffs yesterday against today into a banner.
  • Reports for side-by-side comparison or multi-card layout, with revocable public share links, report packages bundling many reports into one workbook, and report bursting per filter value.
  • Alerts on rows returned, goal reached or below goal, delivered by e-mail, chat, webhook or SMS; scheduled deliveries as PDF or CSV with optional written commentary.
  • Streaming results, chunked exports, and output as JSON, CSV, newline-delimited JSON or Parquet.
  • Content marked 'Verified' as a trust signal, flippable only by curators and logged every time.
03Spreadsheet Engine
  • A hand-written formula engine and virtualised grid — around 500 worksheet functions, cross-sheet references, whole-column ranges, lazy evaluation and cycle detection.
  • Excel's two editing modes, click-and-drag reference picking with range outlining, fill-down with reference rewriting, and row/column reordering that relocates every reference.
  • Four ways to bind data: a saved question, a visual query, ad-hoc SQL, or a natural-language request resolved to SQL once, after which refreshes cost nothing.
  • Refresh-safe blocks: new source columns are appended, removed ones are cleared, your own rows and columns are never overwritten, and key columns return each record to its prior row.
  • Conditional formatting by cell rule, colour scale, data bar and icon set; export keeps formulas as formulas.
04Agentic BI & Proactive Intelligence
  • Four personas — Analyst (read-only), Composer (drafts questions and dashboards), Modeler (builds semantic models), Investigator (root-cause work) — running a reasoning loop over ten tools.
  • Every AI write is a proposal a human must approve by default, shown as a card with accept and reject; row-level data access for AI is off by default.
  • An audit table stores the exact prompt, message and injected context sent to the provider, so users can audit what the model was told.
  • Seven provider families, one fully self-hosted; per-organisation token, session and step budgets; a built-in Model Context Protocol server exposing eight tools.
  • An insights feed detects trend changes, milestones, new records, stale data, correlations, seasonality and anomalies, with severity and de-duplication.
  • Anomaly detection over a rolling window excluding the point being judged; a badged change hands off to the Investigator persona in one click.
  • Investigations produce findings and an executive summary, triggered manually, automatically above a severity threshold, or weekly.
05Performance & Governance
  • Four performance tiers: in-memory, persistent storage that survives a restart, materialised tables written into a database you own, and replication with reload, watermark and change data capture.
  • A typed lineage graph across connections, tables, questions, dashboards, alerts and deliveries, with a printable view and a downloadable report.
  • The BCBS 239 module: fourteen principles, scored self-assessments with sign-off, a critical data element register, quality rules across six dimensions, a risk report register, and a remediation log.
  • Schema authoring with import, dialect compilation and a plan preview, gated by three independent switches all off by default, with every executed statement recorded verbatim.
  • A query audit log capturing actor, query type, full SQL, rows, duration, status and cache state, with retention and an auditor export.
  • Two embed paths — a dashboard SDK with signed embeds, and a scoped embeddable assistant widget — plus an auto-generated database API on a widely used PostgreSQL REST convention.
  • 240 help articles across twelve categories, including forty troubleshooting runbooks and nine administrative operational runbooks.
06Security & governance
  • Group-based access on two ladders — content and data — with the most permissive grant winning
  • Tenant isolation in three layers: scoped columns, request context, and optional database row-level policies with per-request role switching
  • AES-256-GCM at rest for connection passwords, identity secrets and integration tokens; the in-memory query cache stores encrypted bytes
  • Passwords hashed with bcrypt at cost twelve; account lockout on repeated failures
  • API tokens stored hashed, with scopes, per-token rate limits, expiry and rotate-all
  • Injection defence through sanitisers, a parser and prepared statements, on read-only connections; a five-pass sanitiser on white-label content
  • Resource guards throughout: timeouts, row caps, a concurrency governor, per-user daily budgets, agent step and token budgets, abort thresholds
  • Control mapping to a recognised trust services framework, with an explicit statement of what the product does not provide, plus a documented data-subject deletion procedure
■Java 21 on Spring Boot 4 with virtual threads, native-image hints included
■PostgreSQL 14 or later, 86 tables, schema owned entirely by versioned migrations
■Server-rendered vanilla ES6 front end — no package manager, no bundler, no build step
■91 REST controllers with OpenAPI, an agent protocol server, and a database-compatible table and function API
■Single sign-on via OpenID Connect, LDAP and Active Directory — multi-factor authentication and SAML are not yet implemented
■Around 71 MB vendored assets, self-hosted fonts, zero content-delivery-network references

Industries

Who it works for
  • Banking & insurance
    A productised BCBS 239 module for risk data teams, with critical data element ownership, quality scoring and an attestation calendar.
  • Internal audit & compliance
    Auditors are first-class users: audit exports, permission evidence, prompt records and a printable governance dossier.
  • Pharma & life sciences
    Full query audit with retention, verified-content trust signals, and AI that proposes changes rather than writing them.
  • Energy & utilities
    Operational reporting across mixed estates, with replication and materialisation keeping analytical load off production systems.
  • Public sector & sovereignty
    Self-hosted with no external asset fetch and a fully on-premise assistant option, for public bodies, defence and financial infrastructure.
  • Software vendors & MSPs
    Signed embeds with locked parameters, a scoped assistant widget, per-client branding and custom domains on one deployment.
  • Data platform teams
    Change data capture, materialisation into tables you own and an auto-generated database API, alongside the reporting.
  • Legacy enterprise estates
    SQL dialects for databases modern tools ignore, such as DB2 and Sybase, and API samples in eleven languages including COBOL and RPG.
  • Multilingual mid-market
    Five languages at complete coverage, editable in the product, with machine translation for adding more.

Use cases

Example scenarios
01 · Banking & insurance

A BCBS 239 self-assessment kept in a register instead of documents

Challenge
A bank's risk data team assembles its BCBS 239 self-assessment by hand: principle scores in a document, critical data elements in a spreadsheet, lineage in diagrams, and sign-offs scattered over email before every supervisory review.
Approach
The BCBS 239 module holds the fourteen principles with scored self-assessments in a draft, submit and approve chain, a critical data element register with owner and materiality, quality rules scored across six dimensions and element-to-element lineage. A risk report calendar with attestation and a remediation issue log complete it, and the dossier prints from the same data.
Result
The review pack comes out of the register the team maintains all year, each sign-off shows who approved what, and AI-drafted content is recorded separately from human actions. Qrly supports the compliance work; it does not itself guarantee compliance.
02 · Energy & utilities

Operational dashboards without querying production systems

Challenge
At a utility, analysts pull figures straight from operational databases and paste them into spreadsheets. Heavy queries slow down systems that were never meant for analytics, and nobody is sure how fresh the numbers in the weekly report are.
Approach
Qrly replicates the relevant source tables into a reporting database, using change data capture where the source supports it, and materialises heavy questions into tables the utility owns. Dashboards on top show when their data was last refreshed, and alerts go out by email, chat or SMS when a metric crosses its goal.
Result
Production systems no longer carry analytical queries, and everyone reading a dashboard can see how current the data behind it is.
03 · Software vendors & MSPs

Customer-facing analytics embedded in a software product

Challenge
A software vendor builds a custom report screen every time a customer asks for a new figure. The development backlog fills with reporting requests, and each customer must only ever see its own data.
Approach
Dashboards are built in Qrly and embedded in the vendor's application through the dashboard SDK, with signed embeds whose customer parameter is locked. Per-tenant branding and a custom domain keep the vendor's look, and the embeddable assistant widget is scoped to named connections and questions.
Result
A new report request becomes a dashboard configured in Qrly rather than a development ticket, and each customer sees only the data its locked parameter allows.
Licence

Per deployment. Never per seat.

Licensed per tenant, not per viewer, with unlimited users. The annual licence is based on your own turnover ex VAT, charged in marginal tranches like income tax so there are no cliffs, starting at a €900 minimum and capped at a 25% yearly increase. Hosting, hardware and AI provider costs are yours; consultancy, setup, migration and training are quoted separately.

Annual licence by turnover, ex VAT
TurnoverPer year
Up to €500k€900
€1M€1,500
€5M€2,500
€25M€5,500
€100M€13,000
€500M€37,000
€1B€52,000

Illustrative: a per-viewer licence at €12 a month bills four hundred readers €57,600 a year; at €5M turnover this is €2,500.

What it does

  • 01A no-code query builder compiles to correct SQL across roughly forty database types — with a converter that turns hand-written SQL back into the visual builder.
  • 02A real spreadsheet engine with around 500 functions sits on top of live, governed data — not a static export.
  • 03Every AI write is a human-approved proposal, logged in a full prompt-and-context audit trail; BCBS 239 governance ships as a built-in module.

At a glance

CategoryBusiness Intelligence
LicencePer deployment, unlimited users, from €900 a year
For whomBanking · Insurance · Regulated enterprise · Embedded analytics

Connect one database.

Give us read access to a single schema. We will build the dashboard your team actually asks for every Monday, and hand you the deployment.Start the conversation →