Frappe Insights

What Frappe Insights does

• Four database connectors plus files Connect MySQL, PostgreSQL, DuckDB, and BigQuery as data sources, alongside uploaded files and spreadsheets, so reporting starts from the databases the team already holds.[1][2]

• Step-by-step queries without SQL Build queries through a guided sequence of table selection, joins, filters, calculated columns, and pivots, with no SQL required for standard reporting questions.[1][2]

• Automatic chart suggestions Let the chart builder suggest a visualization for each result set instead of choosing a chart type from scratch for every question.[1][2]

• Drag-and-drop filtered dashboards Assemble dashboards by dragging charts into place and apply dashboard-level filters that cut across every chart at once.[1][2]

• Shared operational dashboards Publish dashboards the whole team reads in the browser, aimed at operational reporting rather than one-off personal analysis.[1][2]

• Frappe Framework reporting roots Query data held in Frappe Framework applications directly, which suits teams that already run operations such as ERPNext on the framework.[1][2]

• Ibis queries, ECharts visuals Compose queries on Ibis and render them with Apache ECharts on the Frappe stack, in a Python and Vue codebase the operator's engineers can read.[1]

• AGPL-3.0 open source Run, study, and modify fully open-source code under the AGPL-3.0 licence, with development visible in the public frappe/insights repository.[1][2]

Who will love it

• Teams reporting without SQL specialists A team that holds data in MySQL or PostgreSQL and wants charts without hiring SQL specialists. This is an editorial inference from the documented query builder and connector list.[1][2]

• Frappe shops needing dashboards A team already running operations on Frappe Framework apps that wants dashboards over that data in the same stack. This is an editorial inference from the documented reporting motivation.[1][2]

• Operators wanting data on their servers An operator that wants reporting with data staying in its own databases under an open-source licence. This is an editorial inference from the documented self-hosting paths and licence.[1][2]

Who should avoid it

• Four named connectors only Only MySQL, PostgreSQL, DuckDB, and BigQuery are documented as database connectors, plus files and spreadsheets. Teams whose data lives elsewhere, for example Oracle or SQL Server, will not find a documented path.[1][2]

• Server skills required to run it Installation runs through Docker, a compose file, or Bench on the operator's server, with database credentials and ongoing administration. That is moderate server work, not a signup flow, for a non-technical team.[1][2]

• Thin independent review base Independent user evidence is thin: the G2 product page showed only an aggregate 3.3 out of 5 from 2 reviews when inspected in October 2026, with no original user report usable as a testimonial. Treat fit claims as documentation-based until more firsthand reports appear.[1]

• Managed path means Frappe Cloud Teams that do not want to operate the server must use the managed Frappe Cloud site, which is billed separately from the free software. There is no documented free hosted tier.[1][2]

Setup and compatibility