Data sources, connectors & refresh
How this is scored
Which data the product can reach and how it stays current: native connectors to databases and warehouses (PostgreSQL, MySQL, SQL Server, BigQuery, Snowflake), to business applications (accounting, ERP, CRM, shop, help desk, ad platforms) and to files and spreadsheets (Excel, CSV, Google Sheets), live queries versus imported extracts, scheduled and incremental refresh with its minimum interval, joining data from several sources, light data preparation, access to databases behind a firewall (gateway, SSH tunnel, IP allow-list), and a generic REST or custom connector for what is not listed.
0 — Not a reporting product, or data can only be typed or pasted in by hand.
3 — Spreadsheet and file uploads plus a handful of named connectors; refresh schedules, live queries and blending sources are basic or not described.
5 — A published connector list covering the common databases, warehouses, spreadsheets and several named business applications, scheduled refresh with its interval stated, live queries or extracts at the customer's choice, data from two sources combined in one report, and a documented way to reach a database behind a firewall.
8 — Hundreds of maintained connectors or a full SQL layer over every major warehouse, incremental refresh and caching explained, a built-in data preparation or modelling step, a gateway or agent for on-premise sources, a generic REST or custom connector SDK, and connector limits (rows, API calls, history) stated per plan.
10 — Connectivity an organisation can standardise on: every source reachable live or by extract with the trade-offs documented, refresh down to minutes with lineage from report back to source, source changes detected and reported, and connector behaviour, quotas and failure handling published.
The IT Administrator
A published connector list of 90+ integrations covering six named SQL databases (MySQL, MariaDB, PostgreSQL, Amazon Redshift, Snowflake, Microsoft SQL Server), spreadsheets and many business applications, with a per-source refresh table down to 30 seconds for one source and user-configurable database refresh, meets the documented-connector level. What holds it there for me: the only documented route to a database behind our firewall is a publicly accessible host allow-listed against six published IP addresses — SSH tunnelling is stated as unsupported — and a visualization is powered by a single dataset, so data from two or more datasets cannot be combined to build a visualization; dataset limits of 5,000 records, 80 columns and a 4MB data size limit are stated. 5 7 12 13 16