Metabase Hosting

How Metabase works

Metabase connects to a supported analytical or operational data source and presents its tables through a browser interface. Users can build questions with the graphical query builder or write native queries where the connected database supports them. Results become tables, charts, maps, or other visualisations that can be saved for later use.

Saved questions can be combined into dashboards with filters and linked interactions. Collections organise questions, models, and dashboards for different teams, while permissions determine which groups can access databases or content. The PostgreSQL container in the catalogue stores Metabase’s own application configuration; it does not replace the external data source being analysed.

Key Metabase features

The query builder lets non-SQL users select data, filter rows, summarise measures, group results, and create visualisations. Analysts can use native queries for greater control, then expose trusted results to colleagues through dashboards and saved models.

Dashboard filters let viewers change dates, categories, or other parameters without editing each question. Collections and permissions organise content, and embedding or APIs can integrate approved analytics into other applications. Feature availability depends on the connected database and deployed edition.

Metabase vs Tableau

Metabase is a self-hosted business-intelligence application focused on approachable queries, saved questions, dashboards, and SQL access. Tableau is a commercial analytics platform spanning visual exploration, governed data access, sharing, embedded analytics, cloud services, and enterprise administration.

Tableau may suit organisations that need advanced visual analysis, mature enterprise governance, vendor support, and a broader managed analytics ecosystem. Metabase is more attractive when teams want a direct self-hosted interface for common database questions and dashboards without adopting the full scope of an enterprise analytics platform.

Who uses Metabase

Product teams track adoption and funnels, operations groups monitor throughput, finance teams review revenue and costs, and managers use dashboards for recurring performance checks. Analysts can prepare trusted questions that colleagues explore through filters rather than writing their own SQL.

Metabase is not a data warehouse and does not repair poor source data. Query speed, freshness, and accuracy depend on the connected systems, database permissions, modelling choices, and the complexity of each question.

Self-hosting Metabase: requirements and cost

Resource use depends on active viewers, dashboard complexity, query concurrency, result size, cache behaviour, and the responsiveness of connected data sources. PostgreSQL stores Metabase users, settings, permissions, questions, dashboards, and other application metadata. AvaHost provisions this application database, but it remains unmanaged. Email alerts and dashboard subscriptions are unavailable because hosted application email is disabled.

Metabase has no separate software charge for the hosted core application, and the database-memory adjustment moves it to Plan 4 at €20. Metabase hosting supplies one-click setup, an analytics domain, automated HTTPS, automatic application updates, and scheduled backups. External databases, warehouse capacity, and query costs remain outside the application plan.