Ranked in these QuestionsQuestion Ranking
Pro Straightforward and config-based, nothing much to code
Tipboard is straightforward to configure — you define your dashboard's layout with YAML, specify what tiles you want in there (text, pie chart, line chart, bar chart, listing, etc.), give it a unique ID, and that's all you need for a complete dashboard. The only step left is to push your data to Tipboard's tiles, which can be done over an HTTP API.
Pro Can build and display multiple dashboards from a single Tipboard instance
As of version 1.3.0, you can define multiple dashboards and serve them from a single Tipboard instance by creating one layout config file for each dashboard, and your dashboard will be available at http://your_url.com/
Pro Open source & self-hosted
You don't have to hand over your data to a third-party — you own your data, and you're in full control over the dashboarding system.
Pro Provides an HTTP API for pushing data to dashboard
Tipboard provides an HTTP API for pushing data in JSON format to the dashboard. This gives you the ability to wire up your data source in any way you like — the only thing you have to do is
POST the data to your tile's endpoint.
Pro Build dashboard layouts with YAML
Tipboard's dashboard layouts are defined in YAML. It follows a grid-based approach where the user defines which tile should go into which column, and which row the column should be in.
Con No Python 3 support
Tipboard is Python 2.7 only.
Con No easy way to deploy
Tipboard's docs covers installation/deployment comprehensively, but they do not offer a way to easily deploy to a PaaS (e.g. Heroku) or similar.