// the find
getredash/redash
Make Your Company Data Driven. Connect to any data source, easily visualize, dashboard and share your data.
Redash is a self-hosted BI tool that lets you write SQL (or NoSQL) queries, visualize results, and build dashboards — all browser-based with shareable URLs. It targets data teams who want to query multiple sources in one place without paying for Looker or Metabase Cloud. The breadth of supported data sources is the headline feature.
1. 35+ native query runners with a clean plugin interface — adding a new data source is well-structured, not a hack. The coverage from Postgres to Salesforce to Prometheus to JIRA JQL is genuinely broad. 2. The REST API covers everything the UI does, so you can automate dashboard creation, seed queries from CI, or build on top of Redash without screen-scraping. 3. Scheduled refreshes combined with multi-destination alerting (Slack, PagerDuty, email, webhooks) make it usable as a lightweight monitoring layer without a separate observability stack. 4. Queries are first-class objects with shareable URLs and peer review built in — which encourages the 'write once, share with the org' pattern rather than spreadsheet proliferation.
1. Databricks acquired the company that built the hosted version; the OSS repo is community-maintained now, and the pace of core investment has slowed noticeably. Betting a production deployment on it means owning more of the maintenance burden than the star count implies. 2. Self-hosting requires orchestrating Postgres + Redis + Celery workers + the web app together — the Docker Compose setup works, but it's four moving parts that all need to stay healthy, and the operational docs assume some familiarity with that stack. 3. No query version history in the UI — overwrite a query and it's gone unless you have database-level backups. For a tool where queries are the primary artifact, this is a real gap. 4. The frontend is aging: class components, LESS stylesheets, older Ant Design, Webpack config that predates Vite by several years. Contributing to the UI side means working in a codebase that hasn't had a modernization pass.