Metabase
chirashi.metabase
A Docker Compose file for Metabase alone, generated from the catalog and checked by the safety inspector. No account needed.
Business intelligence server for querying databases through a visual question builder or SQL, assembling results into dashboards with filters, scheduled subscriptions and row-level permissions.
Metabase connects directly to existing databases and lets questions be built by choosing tables, filters and aggregations in an interface that generates the SQL underneath, with a native editor for anything the builder cannot express. Questions become dashboard cards with linked filters, and dashboards can be delivered on a schedule or when a result condition is met. A metadata layer of display names, types, hidden fields and foreign key relationships shapes what non-technical users see without changing the database itself. Permissions run down to group, database, table and row level, so access can be scoped without issuing separate database accounts.
You know it worked when
- The setup wizard completes and an administrator can sign in.
- A database connection is added and its schema synchronises.
- A question built in the interface returns rows.
- That question renders on a dashboard with a filter applied.
- A restricted group sees only the tables its permissions allow.
Known sharp edges
- The default embedded application database suits evaluation only, and moving to an external one later is an export and import rather than a configuration change.
- Questions run against the live source database, so an unrestricted native query can put a production system under load.
- Database credentials entered during setup are held by the server and inherited by every user permitted to query that source.
- Scheduled subscriptions deliver query results by email or chat, which moves data outside the deployment boundary.