Version v0.43 of Metabase is no longer supported. Check out the docs for the current stable version, Metabase v0.63.
In addition to our Officially supported drivers, many people build and maintain drivers for database integrations.
We have two types of third-party drivers:
To use a Partner or Community driver on a self-hosted Metabase:
You can change the location of the plugins directory by setting the environment variable MB_PLUGINS_DIR.
Partner drivers, like officially supported drivers, are available out-of-the-box on Metabase cloud. No action needed.
Community drivers are not supported on Metabase Cloud.
Partner drivers are available both on Metabase Cloud and on self-hosted Metabases.
To qualify as a partner driver, the driver must:
Current partner drivers:
Partner drivers are available to Cloud customers out-of-the-box.
If you have interest in becoming a partner, please fill the partner form and we will get in touch.
Note: Metabase Cloud doesn’t support community drivers
Anyone can build a community driver. These are the currently known third-party database drivers for Metabase.
You install these drivers at your own risk. The plugins will run as part of your Metabase instance and, as such, will have access to anything it does.
| Database | GitHub Stars | Last release (if available) |
|---|---|---|
| Amazon Athena | ||
| ClickHouse | ||
| CSV | ||
| Cube.js | ||
| Datomic | ||
| DB2 | ||
| Exasol | ||
| Firebird | ||
| Impala | ||
| Materialize | ||
| Neo4j | ||
| Spark Databricks | ||
| Teradata |
If you don’t see a driver for your database, then try looking in the comments of the issue related to the database. You might also find more by searching on GitHub.
If you are having problems installing or using a community driver, your best bet is to contact the author of the driver.
Metabase Cloud doesn’t support community drivers, meaning that (for now) you can only use Metabase Cloud with the officially supported drivers, and the partner drivers listed above.
Check out Guide to writing a Metabase driver.