--- title: "Deploy Metabase — Analytics Platform" description: "Deploy your own analytics platform in 1 click. Simple, fast, ready to use." category: "Storage" url: https://railway.com/deploy/metabase-railway-template --- # Deploy Metabase — Analytics Platform Deploy your own analytics platform in 1 click. Simple, fast, ready to use. **[Deploy Metabase — Analytics Platform on Railway](https://railway.com/template/metabase-railway-template)** - **Creator:** INF Labs - **Category:** Storage - **Total deploys:** 1 ## Template content ### Postgres https://devicons.railway.app/i/postgresql.svg - **Image:** ghcr.io/railwayapp-templates/postgres-ssl:18 ### metabase https://devicons.railway.app/metabase - **Image:** metabase/metabase:latest - **Health check:** /api/health - **Public domain:** Yes ## Documentation # Deploy and Host Metabase Analytics Platform on Railway Metabase is an open-source business intelligence and analytics platform that helps teams explore data, build dashboards, ask questions, and share insights without requiring complex BI infrastructure. It provides an accessible interface for both technical and non-technical users to analyze data and create interactive visualizations. ## About Hosting Metabase Analytics Platform ![Metabase](https://imgur.com/JQhexIv.png) This template deploys Metabase with a dedicated PostgreSQL application database for persistent configuration and metadata. Metabase uses its application database to store user accounts, dashboards, questions, collections, settings, permissions, and other application metadata. PostgreSQL is the recommended application database for production deployments, while the default embedded H2 database is intended primarily for local or demonstration use. The application service itself does not require a persistent volume because important Metabase state is stored in PostgreSQL. Railway handles both services within the same project, making the stack easy to deploy and manage. Railway supports provisioning PostgreSQL alongside applications with minimal configuration. ## Common Use Cases * Build interactive business intelligence dashboards * Explore databases without writing SQL for every question * Create charts, reports, and visualizations * Track KPIs and operational metrics * Share analytics dashboards across teams * Perform ad-hoc data exploration * Build internal reporting portals * Connect multiple databases and data warehouses * Embed dashboards and analytics into applications * Provide self-service analytics for business users ## Metabase vs Other Analytics Platforms | Platform | Self-Hosted | Visual Dashboards | SQL Support | Ease of Use | Best Fit | | ------------------- | -------------------- | ----------------- | ------------------ | ----------------- | ------------------------------------------------- | | **Metabase** | ✅ Yes | ✅ Yes | ✅ Yes | ✅ High | Self-service BI, internal dashboards, analytics | | **Apache Superset** | ✅ Yes | ✅ Yes | ✅ Strong | ⚠️ More technical | Advanced analytics and data teams | | **Grafana** | ✅ Yes | ✅ Yes | ✅ Via data sources | ⚠️ Technical | Monitoring, observability, time-series dashboards | | **Redash** | ✅ Yes | ✅ Yes | ✅ Strong | ✅ Moderate | SQL-centric analytics and visualization | | **Power BI** | ⚠️ Primarily managed | ✅ Yes | ✅ Yes | ✅ High | Enterprise Microsoft ecosystem | Metabase is particularly suitable when you want a balance between an intuitive dashboard experience and direct SQL access without operating a heavier enterprise BI stack. ## Dependencies for Metabase Analytics Platform Hosting * **Metabase** — analytics, dashboard, visualization, and query interface * **PostgreSQL** — persistent application database * **Railway Private Networking** — internal communication between the application and database * **Railway Public Networking** — HTTPS access to the Metabase interface The PostgreSQL service in this template is used as the **Metabase application database**. It stores Metabase's internal state and is separate from external databases or warehouses that you may later connect for analytics. ### Deployment Dependencies * Metabase Documentation: https://www.metabase.com/docs/latest/ * Configuring the Metabase Application Database: https://www.metabase.com/docs/latest/installation-and-operation/configuring-application-database * PostgreSQL Connection Documentation: https://www.metabase.com/docs/latest/databases/connections/postgresql * Railway PostgreSQL Documentation: https://docs.railway.com/databases/postgresql * Railway Templates: https://docs.railway.com/guides ## Implementation Details This template uses a simple two-service architecture: ```text ┌─────────────────┐ │ User │ └────────┬────────┘ │ ▼ Railway HTTPS Proxy │ ▼ ┌─────────────────┐ │ Metabase │ │ │ │ Dashboards │ │ Queries │ │ Analytics │ └────────┬────────┘ │ Private Network │ ▼ ┌─────────────────┐ │ PostgreSQL │ │ │ │ Application DB │ │ + Volume │ └─────────────────┘ ``` Metabase connects to PostgreSQL using environment variables such as: ```env MB_DB_TYPE=postgres MB_DB_HOST= MB_DB_PORT= MB_DB_DBNAME= MB_DB_USER= MB_DB_PASS= ``` Metabase reads its application database configuration during startup. PostgreSQL is the recommended backend for production application metadata. ## Persistent Storage The Metabase service itself does **not require a persistent volume** in this template. Persistent application state is stored in the PostgreSQL service, including: * User accounts * Dashboards * Questions * Collections * Permissions * Application settings * Metadata about connected databases * Query and visualization configuration The PostgreSQL service should use persistent storage so this information survives restarts and redeployments. ## Connecting Your Data The PostgreSQL database included with this template is used for **Metabase's internal application data**. To analyze your own data, add databases separately from the Metabase Admin interface. Metabase supports connecting to PostgreSQL and many other database systems as external data sources. Database connections can be added from the administration interface after deployment. Typical data sources include: * PostgreSQL * MySQL * MariaDB * SQL Server * BigQuery * Snowflake * Redshift * ClickHouse * Other supported databases and warehouses ## Getting Started After deployment: 1. Open the public Railway domain assigned to the Metabase service. 2. Complete the initial Metabase setup wizard. 3. Create the administrator account. 4. Configure your organization details. 5. Add the database or data warehouse you want to analyze. 6. Start creating questions, charts, and dashboards. The bundled PostgreSQL application database is configured automatically by the template, so you do not need to manually configure Metabase's internal database. ## Why Deploy Metabase Analytics Platform on Railway? Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it. By deploying Metabase Analytics Platform on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway. ## Similar templates - [Garage S3 Storage](https://railway.com/deploy/garage-s3-storage) — Ultra-light S3 server: fast, open-source, plug-and-play. - [Redis](https://railway.com/deploy/redis-1) — Self Host Latest Redis with Railway - [EasyImg](https://railway.com/deploy/easyimg) — Simple self-hostable Nuxt.js personal image hosting system. Open this page in a browser: https://railway.com/deploy/metabase-railway-template