Data & Analytics solution
Run Metabase Locally with FlyEnv
Metabase uses a Java runtime and a database for its application metadata, with a proxy when a local domain is useful. FlyEnv manages those local environment services around Metabase.
Local project stack
Services FlyEnv can manage around Metabase
About Metabase
Metabase is a business intelligence application for exploring data, composing questions, publishing dashboards, and distributing alerts. It keeps its own application metadata separate from the databases that analysts query, so permissions, collections, cards, and connections can be managed independently of business data.
A local Metabase instance runs on Java with an application database such as PostgreSQL for durable metadata. It also needs one or more reachable sample data sources for meaningful development; SMTP, SSO, embedding settings, and a reverse proxy are optional integrations chosen by the deployment.
Core capabilities
- Visual query builder
- SQL editor
- Dashboards
- Alerts and subscriptions
- Collections and permissions
- Embedding
Common use cases
- Operational dashboards
- Self-service data exploration
- Embedded product analytics
- Scheduled business reporting
Metabase separates its metadata from analytical data sources
A durable application database and a realistic query target make local dashboards reproducible; integration services are scenario-dependent.
- Java runtime and Metabase application
- Starts the server and its administration interface.
- Application metadata database
- PostgreSQL or another supported database persists users, cards, dashboards, and connections.
- Connected sample data source
- A reachable project database is needed to build and verify questions, models, and dashboards.
- Optional SMTP or SSO
- Use these only when testing subscriptions, user provisioning, or enterprise authentication.
Project resources
For installation commands, supported versions, and project-specific configuration, refer to the official Metabase documentation.
Typical local stack
The exact services depend on the project, its release, and its local configuration. This is a common local setup, not a fixed requirement.
| Component | Typical role |
|---|---|
| Java | Runs the Metabase application. |
| PostgreSQLMySQL | May store application metadata. |
| NginxCaddy | May proxy a local Metabase domain. |
How FlyEnv helps
Manage the Java runtime
Use the JDK required by the Metabase release.
Run the application database
Keep the configured metadata database local to the project.
Use a local analytics address
Configure a domain and HTTPS for browser testing when useful.
Start dependencies together
Keep the application and local services in one Startup Group.
Set up the local environment
Project installation stays with the upstream documentation. FlyEnv manages the runtimes, databases, web servers, and supporting services around it.
- 1Use the Metabase documentation for installation and supported version guidance.
- 2Select the Java runtime required by the Metabase release.
- 3Start the metadata database when the installation uses one.
- 4Configure a local reverse proxy and domain when browser access needs one.
- 5Enable local HTTPS when integrations require a secure origin.
- 6Save the application and services in a Startup Group when useful.
Related solutions
Ready to run Metabase locally?
Use FlyEnv to manage the runtimes, databases, web servers, and services around your local Metabase environment.