How Metabase Works

Metabase solves the "everyone needs data but not everyone writes SQL" problem. Its architecture is built around a visual query builder that translates clicks into database queries — and the driver abstraction layer underneath is what makes it work across 20+ database types.

46,416 stars Clojure 10 components 5-stage pipeline

What metabase Does

Open-source business intelligence tool for data visualization and analytics

Metabase is a comprehensive web-based BI platform that enables users to create dashboards, ask questions about data, and build embedded analytics. It combines a TypeScript/React frontend with backend APIs, offering both self-hosted and cloud options with enterprise features.

Architecture Overview

metabase is organized into 5 layers, with 10 components and 3 connections between them.

Core Frontend
Main React application with Redux state management
Enterprise Features
Premium features including embedding SDK and advanced analytics
Embedding SDK
React SDK package for embedding Metabase in other applications
E2E Testing
Comprehensive Cypress testing suite with multiple host applications
Build Infrastructure
Multiple Rspack configurations for different build targets

How Data Flows Through metabase

Data flows from databases through the backend API to the React frontend, with enterprise features adding embedding capabilities and advanced analytics. The embedding SDK allows external applications to consume Metabase components.

1Database Connection

Backend connects to various databases and exposes data through REST APIs

2Frontend State Management

Redux/RTK Query manages API calls and application state in the React frontend

3Enterprise Extensions

Enterprise features extend base functionality with advanced analytics and embedding

4SDK Distribution

Embedding SDK packages Metabase components for external consumption

5External Integration

Host applications integrate Metabase components using the SDK with authentication

Technology Choices

metabase is built with 10 key technologies. Each serves a specific role in the system.

React
Frontend framework with hooks and context
Redux Toolkit
State management with RTK Query for API calls
TypeScript
Type safety across frontend and enterprise code
Rspack
Fast bundler with multiple configuration targets
Cypress
E2E testing with extensive helper utilities
Emotion
CSS-in-JS styling solution
Mantine
React components library for UI
D3
Data visualization and charting
Chalk
CLI output formatting and colors
Jest
Unit testing framework

Key Components

Who Should Read This

Data teams looking for self-service analytics, or engineers evaluating Metabase for embedded analytics.

This analysis was generated by CodeSea from the metabase/metabase source code. For the full interactive visualization — including pipeline graph, architecture diagram, and system behavior map — see the complete analysis.

Explore Further

Frequently Asked Questions

What is metabase?

Open-source business intelligence tool for data visualization and analytics

How does metabase's pipeline work?

metabase processes data through 5 stages: Database Connection, Frontend State Management, Enterprise Extensions, SDK Distribution, External Integration. Data flows from databases through the backend API to the React frontend, with enterprise features adding embedding capabilities and advanced analytics. The embedding SDK allows external applications to consume Metabase components.

What tech stack does metabase use?

metabase is built with React (Frontend framework with hooks and context), Redux Toolkit (State management with RTK Query for API calls), TypeScript (Type safety across frontend and enterprise code), Rspack (Fast bundler with multiple configuration targets), Cypress (E2E testing with extensive helper utilities), and 5 more technologies.

How does metabase compare to superset?

CodeSea has detailed side-by-side architecture comparisons of metabase with superset, redash. These cover tech stack differences, pipeline design, and system behavior.

Visualize metabase yourself

See the interactive pipeline graph, architecture diagram, and system behavior map.

See Full Analysis