Make Your Company Data Driven. Connect to any data source, easily visualize, dashboard and share your data.
Go to file
2016-06-14 14:23:56 +03:00
.github Update ISSUE_TEMPLATE.md 2016-05-05 22:30:10 +03:00
bin Update Heroku pre_compile hook 2016-06-14 14:23:56 +03:00
docs Add section about monitoring 2016-06-08 15:47:00 +02:00
migrations Feature: UI for query parameters 2016-06-14 10:09:16 +03:00
rd_ui Deduplicate parameter names 2016-06-14 14:00:38 +03:00
redash Merge pull request #1119 from getredash/feature/params_ui 2016-06-14 12:00:53 +03:00
setup Update version reference in bootstrap scripts. 2016-05-22 10:33:46 +03:00
tests Merge pull request #1119 from getredash/feature/params_ui 2016-06-14 12:00:53 +03:00
.bowerrc Add Heroku support 2016-06-03 12:21:09 +10:00
.coveragerc Exclude settings.py from coverage report. 2014-02-06 20:55:14 +02:00
.dockerignore Fix .dockerignore file: 2015-11-23 11:38:15 +02:00
.env.example Remove references to deprecated config 2016-03-12 18:22:53 +02:00
.gitignore Add Heroku support 2016-06-03 12:21:09 +10:00
.landscape.yaml landscape.io configuration file 2014-10-19 13:41:29 +03:00
bower.json Update bower.json 2016-06-08 08:57:51 +03:00
circle.yml Take into account that node_modules moves to root 2016-06-06 09:24:13 +03:00
CONTRIBUTING.md Update CONTRIBUTING.md 2016-06-01 15:55:50 +03:00
docker-compose-example.yml redash static assets path should be pointed at dist, not app 2016-03-10 11:36:42 -08:00
Dockerfile Merge pull request #1077 from nabilblk/master 2016-06-13 15:22:53 +03:00
gulpfile.js Fix paths in Gulp build pipeline 2016-06-08 10:00:05 +03:00
LICENSE BSD 2-Clause 2016-02-10 11:32:00 +02:00
Makefile Add Heroku support 2016-06-03 12:21:09 +10:00
manage.py manage.py support group operations. 2016-04-10 22:08:36 +09:00
package.json Fix paths in Gulp build pipeline 2016-06-08 10:00:05 +03:00
Procfile.dev Vagrant file to use the redash/dev box 2014-12-30 07:45:30 +02:00
Procfile.heroku Update Heroku support as per comments 2016-06-06 11:39:10 +10:00
README.md Remove reference to Google Groups and add Discourse instead 2016-05-22 10:33:46 +03:00
requirements_all_ds.txt move hive depencencies into req_all_ds.txt 2016-06-09 22:29:46 +00:00
requirements_dev.txt Move datasource requirements from bootstrap to own requirements file 2015-07-27 11:46:53 -07:00
requirements_oracle_ds.txt Better number handling 2015-10-21 10:05:38 -04:00
requirements.txt move hive depencencies into req_all_ds.txt 2016-06-09 22:29:46 +00:00
Vagrantfile Ama: Consolidate vagrant_provision script, move files to more intuitive locations, include command from #1021. 2016-05-09 17:13:33 -05:00

More details about the future of re:dash : http://bit.ly/journey-first-step


Join the chat at https://gitter.im/getredash/redash Documentation

re:dash is our take on freeing the data within our company in a way that will better fit our culture and usage patterns.

Prior to re:dash, we tried to use traditional BI suites and discovered a set of bloated, technically challenged and slow tools/flows. What we were looking for was a more hacker'ish way to look at data, so we built one.

re:dash was built to allow fast and easy access to billions of records, that we process and collect using Amazon Redshift ("petabyte scale data warehouse" that "speaks" PostgreSQL). Today re:dash has support for querying multiple databases, including: Redshift, Google BigQuery, PostgreSQL, MySQL, Graphite, Presto, Google Spreadsheets, Cloudera Impala, Hive and custom scripts.

re:dash consists of two parts:

  1. Query Editor: think of JS Fiddle for SQL queries. It's your way to share data in the organization in an open way, by sharing both the dataset and the query that generated it. This way everyone can peer review not only the resulting dataset but also the process that generated it. Also it's possible to fork it and generate new datasets and reach new insights.
  2. Dashboards/Visualizations: once you have a dataset, you can create different visualizations out of it, and then combine several visualizations into a single dashboard. Currently it supports charts, pivot table and cohorts.

re:dash is a work in progress and has its rough edges and way to go to fulfill its full potential. The Query Editor part is quite solid, but the visualizations need more work to enrich them and to make them more user friendly.

Demo

You can try out the demo instance: http://demo.redash.io/ (login with any Google account).

Getting Started

Getting Help

Reporting Bugs and Contributing Code

  • Want to report a bug or request a feature? Please open an issue.
  • Want to help us build re:dash? Fork the project, edit in a dev environment, and make a pull request. We need all the help we can get!

License

See LICENSE file.