Alternatives to Metabase logo

Alternatives to Metabase

Superset, Looker, Kibana, Grafana, and Power BI are the most popular alternatives and competitors to Metabase.
271
234
+ 1
146

What is Metabase and what are its top alternatives?

Metabase is an easy way to generate charts and dashboards, ask simple ad hoc queries without using SQL, and see detailed information about rows in your Database. You can set it up in under 5 minutes, and then give yourself and others a place to ask simple questions and understand the data your application is generating.
Metabase is a tool in the Business Intelligence category of a tech stack.
Metabase is an open source tool with 18K GitHub stars and 2.4K GitHub forks. Here鈥檚 a link to Metabase's open source repository on GitHub

Metabase alternatives & related posts

related Superset posts

Julien DeFrance
Julien DeFrance
Principal Software Engineer at Tophatter | 16 upvotes 485.5K views
atSmartZipSmartZip
Rails
Rails
Rails API
Rails API
AWS Elastic Beanstalk
AWS Elastic Beanstalk
Capistrano
Capistrano
Docker
Docker
Amazon S3
Amazon S3
Amazon RDS
Amazon RDS
MySQL
MySQL
Amazon RDS for Aurora
Amazon RDS for Aurora
Amazon ElastiCache
Amazon ElastiCache
Memcached
Memcached
Amazon CloudFront
Amazon CloudFront
Segment
Segment
Zapier
Zapier
Amazon Redshift
Amazon Redshift
Amazon Quicksight
Amazon Quicksight
Superset
Superset
Elasticsearch
Elasticsearch
Amazon Elasticsearch Service
Amazon Elasticsearch Service
New Relic
New Relic
AWS Lambda
AWS Lambda
Node.js
Node.js
Ruby
Ruby
Amazon DynamoDB
Amazon DynamoDB
Algolia
Algolia

Back in 2014, I was given an opportunity to re-architect SmartZip Analytics platform, and flagship product: SmartTargeting. This is a SaaS software helping real estate professionals keeping up with their prospects and leads in a given neighborhood/territory, finding out (thanks to predictive analytics) who's the most likely to list/sell their home, and running cross-channel marketing automation against them: direct mail, online ads, email... The company also does provide Data APIs to Enterprise customers.

I had inherited years and years of technical debt and I knew things had to change radically. The first enabler to this was to make use of the cloud and go with AWS, so we would stop re-inventing the wheel, and build around managed/scalable services.

For the SaaS product, we kept on working with Rails as this was what my team had the most knowledge in. We've however broken up the monolith and decoupled the front-end application from the backend thanks to the use of Rails API so we'd get independently scalable micro-services from now on.

Our various applications could now be deployed using AWS Elastic Beanstalk so we wouldn't waste any more efforts writing time-consuming Capistrano deployment scripts for instance. Combined with Docker so our application would run within its own container, independently from the underlying host configuration.

Storage-wise, we went with Amazon S3 and ditched any pre-existing local or network storage people used to deal with in our legacy systems. On the database side: Amazon RDS / MySQL initially. Ultimately migrated to Amazon RDS for Aurora / MySQL when it got released. Once again, here you need a managed service your cloud provider handles for you.

Future improvements / technology decisions included:

Caching: Amazon ElastiCache / Memcached CDN: Amazon CloudFront Systems Integration: Segment / Zapier Data-warehousing: Amazon Redshift BI: Amazon Quicksight / Superset Search: Elasticsearch / Amazon Elasticsearch Service / Algolia Monitoring: New Relic

As our usage grows, patterns changed, and/or our business needs evolved, my role as Engineering Manager then Director of Engineering was also to ensure my team kept on learning and innovating, while delivering on business value.

One of these innovations was to get ourselves into Serverless : Adopting AWS Lambda was a big step forward. At the time, only available for Node.js (Not Ruby ) but a great way to handle cost efficiency, unpredictable traffic, sudden bursts of traffic... Ultimately you want the whole chain of services involved in a call to be serverless, and that's when we've started leveraging Amazon DynamoDB on these projects so they'd be fully scalable.

See more
Looker logo

Looker

166
106
6
166
106
+ 1
6
Pioneering the next generation of BI, data discovery & data analytics
Looker logo
Looker
VS
Metabase logo
Metabase

related Kibana posts

Tymoteusz Paul
Tymoteusz Paul
Devops guy at X20X Development LTD | 15 upvotes 349.3K views
Vagrant
Vagrant
VirtualBox
VirtualBox
Ansible
Ansible
Elasticsearch
Elasticsearch
Kibana
Kibana
Logstash
Logstash
TeamCity
TeamCity
Jenkins
Jenkins
Slack
Slack
Apache Maven
Apache Maven
Vault
Vault
Git
Git
Docker
Docker
CircleCI
CircleCI
LXC
LXC
Amazon EC2
Amazon EC2

Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

See more
Tanya Bragin
Tanya Bragin
Product Lead, Observability at Elastic | 10 upvotes 87.7K views
atElasticElastic
Elasticsearch
Elasticsearch
Logstash
Logstash
Kibana
Kibana

ELK Stack (Elasticsearch, Logstash, Kibana) is widely known as the de facto way to centralize logs from operational systems. The assumption is that Elasticsearch (a "search engine") is a good place to put text-based logs for the purposes of free-text search. And indeed, simply searching text-based logs for the word "error" or filtering logs based on a set of a well-known tags is extremely powerful, and is often where most users start.

See more

related Grafana posts

Conor Myhrvold
Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber | 10 upvotes 658.5K views
atUber TechnologiesUber Technologies
Prometheus
Prometheus
Graphite
Graphite
Grafana
Grafana
Nagios
Nagios

Why we spent several years building an open source, large-scale metrics alerting system, M3, built for Prometheus:

By late 2014, all services, infrastructure, and servers at Uber emitted metrics to a Graphite stack that stored them using the Whisper file format in a sharded Carbon cluster. We used Grafana for dashboarding and Nagios for alerting, issuing Graphite threshold checks via source-controlled scripts. While this worked for a while, expanding the Carbon cluster required a manual resharding process and, due to lack of replication, any single node鈥檚 disk failure caused permanent loss of its associated metrics. In short, this solution was not able to meet our needs as the company continued to grow.

To ensure the scalability of Uber鈥檚 metrics backend, we decided to build out a system that provided fault tolerant metrics ingestion, storage, and querying as a managed platform...

https://eng.uber.com/m3/

(GitHub : https://github.com/m3db/m3)

See more
Grafana
Grafana
Kibana
Kibana

For our Predictive Analytics platform, we have used both Grafana and Kibana

Kibana has predictions and ML algorithms support, so if you need them, you may be better off with Kibana . The multi-variate analysis features it provide are very unique (not available in Grafana).

For everything else, definitely Grafana . Especially the number of supported data sources, and plugins clearly makes Grafana a winner (in just visualization and reporting sense). Creating your own plugin is also very easy. The top pros of Grafana (which it does better than Kibana ) are:

  • Creating and organizing visualization panels
  • Templating the panels on dashboards for repetetive tasks
  • Realtime monitoring, filtering of charts based on conditions and variables
  • Export / Import in JSON format (that allows you to version and save your dashboard as part of git)
See more
Power BI logo

Power BI

58
42
0
58
42
+ 1
0
A business analytics service
    Be the first to leave a pro
    Power BI logo
    Power BI
    VS
    Metabase logo
    Metabase
    Redash logo

    Redash

    126
    96
    1
    126
    96
    + 1
    1
    Easily query an existing database, share the dataset and visualize it in different ways
    Redash logo
    Redash
    VS
    Metabase logo
    Metabase
    Periscope logo

    Periscope

    41
    43
    9
    41
    43
    + 1
    9
    Periscope plugs directly into your database and lets you run, save and share analyses over billions of data...
    Periscope logo
    Periscope
    VS
    Metabase logo
    Metabase
    Tableau logo

    Tableau

    227
    116
    0
    227
    116
    + 1
    0
    Tableau helps people see and understand data.
      Be the first to leave a pro
      Tableau logo
      Tableau
      VS
      Metabase logo
      Metabase
      Data Studio logo

      Data Studio

      148
      112
      0
      148
      112
      + 1
      0
      Your data is powerful. Use it
        Be the first to leave a pro
        Data Studio logo
        Data Studio
        VS
        Metabase logo
        Metabase
        Chartio logo

        Chartio

        44
        30
        6
        44
        30
        + 1
        6
        A powerful Business Intelligence tool anyone can use
        Chartio logo
        Chartio
        VS
        Metabase logo
        Metabase
        Amazon Quicksight logo

        Amazon Quicksight

        39
        45
        1
        39
        45
        + 1
        1
        Fast, easy to use business analytics at 1/10th the cost of traditional BI solutions
        Amazon Quicksight logo
        Amazon Quicksight
        VS
        Metabase logo
        Metabase

        related Amazon Quicksight posts

        Julien DeFrance
        Julien DeFrance
        Principal Software Engineer at Tophatter | 16 upvotes 485.5K views
        atSmartZipSmartZip
        Rails
        Rails
        Rails API
        Rails API
        AWS Elastic Beanstalk
        AWS Elastic Beanstalk
        Capistrano
        Capistrano
        Docker
        Docker
        Amazon S3
        Amazon S3
        Amazon RDS
        Amazon RDS
        MySQL
        MySQL
        Amazon RDS for Aurora
        Amazon RDS for Aurora
        Amazon ElastiCache
        Amazon ElastiCache
        Memcached
        Memcached
        Amazon CloudFront
        Amazon CloudFront
        Segment
        Segment
        Zapier
        Zapier
        Amazon Redshift
        Amazon Redshift
        Amazon Quicksight
        Amazon Quicksight
        Superset
        Superset
        Elasticsearch
        Elasticsearch
        Amazon Elasticsearch Service
        Amazon Elasticsearch Service
        New Relic
        New Relic
        AWS Lambda
        AWS Lambda
        Node.js
        Node.js
        Ruby
        Ruby
        Amazon DynamoDB
        Amazon DynamoDB
        Algolia
        Algolia

        Back in 2014, I was given an opportunity to re-architect SmartZip Analytics platform, and flagship product: SmartTargeting. This is a SaaS software helping real estate professionals keeping up with their prospects and leads in a given neighborhood/territory, finding out (thanks to predictive analytics) who's the most likely to list/sell their home, and running cross-channel marketing automation against them: direct mail, online ads, email... The company also does provide Data APIs to Enterprise customers.

        I had inherited years and years of technical debt and I knew things had to change radically. The first enabler to this was to make use of the cloud and go with AWS, so we would stop re-inventing the wheel, and build around managed/scalable services.

        For the SaaS product, we kept on working with Rails as this was what my team had the most knowledge in. We've however broken up the monolith and decoupled the front-end application from the backend thanks to the use of Rails API so we'd get independently scalable micro-services from now on.

        Our various applications could now be deployed using AWS Elastic Beanstalk so we wouldn't waste any more efforts writing time-consuming Capistrano deployment scripts for instance. Combined with Docker so our application would run within its own container, independently from the underlying host configuration.

        Storage-wise, we went with Amazon S3 and ditched any pre-existing local or network storage people used to deal with in our legacy systems. On the database side: Amazon RDS / MySQL initially. Ultimately migrated to Amazon RDS for Aurora / MySQL when it got released. Once again, here you need a managed service your cloud provider handles for you.

        Future improvements / technology decisions included:

        Caching: Amazon ElastiCache / Memcached CDN: Amazon CloudFront Systems Integration: Segment / Zapier Data-warehousing: Amazon Redshift BI: Amazon Quicksight / Superset Search: Elasticsearch / Amazon Elasticsearch Service / Algolia Monitoring: New Relic

        As our usage grows, patterns changed, and/or our business needs evolved, my role as Engineering Manager then Director of Engineering was also to ensure my team kept on learning and innovating, while delivering on business value.

        One of these innovations was to get ourselves into Serverless : Adopting AWS Lambda was a big step forward. At the time, only available for Node.js (Not Ruby ) but a great way to handle cost efficiency, unpredictable traffic, sudden bursts of traffic... Ultimately you want the whole chain of services involved in a call to be serverless, and that's when we've started leveraging Amazon DynamoDB on these projects so they'd be fully scalable.

        See more
        Shiny logo

        Shiny

        35
        18
        0
        35
        18
        + 1
        0
        An R package that makes it easy to build interactive web apps
          Be the first to leave a pro
          Shiny logo
          Shiny
          VS
          Metabase logo
          Metabase
          Google Datastudio logo

          Google Datastudio

          30
          17
          2
          30
          17
          + 1
          2
          A reporting and data visualization tool
          Google Datastudio logo
          Google Datastudio
          VS
          Metabase logo
          Metabase
          Microsoft SSRS logo

          Microsoft SSRS

          28
          18
          0
          28
          18
          + 1
          0
          A server-based report generating software system
            Be the first to leave a pro
            Microsoft SSRS logo
            Microsoft SSRS
            VS
            Metabase logo
            Metabase
            Qlik Sense logo

            Qlik Sense

            19
            5
            0
            19
            5
            + 1
            0
            A business intelligence and visual analytics platform
              Be the first to leave a pro
              Qlik Sense logo
              Qlik Sense
              VS
              Metabase logo
              Metabase
              GoodData logo

              GoodData

              17
              18
              0
              17
              18
              + 1
              0
              We help businesses monetize big data.
                Be the first to leave a pro
                GoodData logo
                GoodData
                VS
                Metabase logo
                Metabase
                QlikView logo

                QlikView

                16
                10
                0
                16
                10
                + 1
                0
                A Business Intelligence platform for turning data into knowledge
                  Be the first to leave a pro
                  QlikView logo
                  QlikView
                  VS
                  Metabase logo
                  Metabase
                  Cube.js logo

                  Cube.js

                  15
                  22
                  13
                  15
                  22
                  + 1
                  13
                  Open Source Analytics Framework
                  Cube.js logo
                  Cube.js
                  VS
                  Metabase logo
                  Metabase
                  Power BI Embedded logo

                  Power BI Embedded

                  12
                  9
                  0
                  12
                  9
                  + 1
                  0
                  Embedded BI reporting engine for your application
                    Be the first to leave a pro
                    Power BI Embedded logo
                    Power BI Embedded
                    VS
                    Metabase logo
                    Metabase