Polyer

Metabase

Deploy Metabase on Polyer so your team can explore databases and build dashboards with or without SQL. This template runs metabase/metabase:latest on a public domain with a private PostgreSQL 16 service as its application database, stored on a volume. Review the floating latest tag and plan backups for that database.

AnalyticsCoolify open catalog

What you can use it for

  • Give your team charts and dashboards built on your application or analytics databases.
  • Let colleagues answer questions with the visual query builder or write SQL when they need to.

What this template creates

metabasemetabase/metabase:latest
Public endpoint
postgresqlpostgres:16-alpine
Private service Persistent volume

Configuration to review

This template has no additional declared inputs. Review the generated variables, endpoints and resource settings in the deployment form.

How to deploy

  1. Select Configure deployment and sign in or create an account.
  2. Choose a new or existing project and select an available region.
  3. Review services, required inputs, storage and compatibility warnings. Submit the deployment only when the configuration is ready.
  4. Inspect deployment logs, complete the application's setup and test its endpoints before production use.

Operating this application

  • Open the generated domain right after deployment and complete Metabase's setup to create the first admin account, since the setup page is open until you do. Connect data sources with read-only database users where possible.
  • Users, questions and dashboards are stored in the bundled PostgreSQL service, not in the Metabase container; check backup and recovery for that volume and test a restore. The template does not set MB_ENCRYPTION_SECRET_KEY, so saved connection details are not encrypted; if you add one, keep it, because Metabase cannot read them without it.
  • The latest tag can point to a newer Metabase release over time, and Metabase migrates its application database when a new version starts, so back up PostgreSQL before redeploying. Metabase runs on the JVM and can need more memory than lighter services, which affects usage-based billing.

Hosting costs

CPU, memory, storage and network usage contribute to your bill. The selected region affects resource prices. A multi-service template incurs usage for each service; external APIs and software licenses are separate.

Review prices and estimate resource costs

Source and validation

This deployment configuration comes from Coolify's Apache-2.0 licensed open template collection and is adapted through Polyer's compose importer.

Static compatibility analysis is not a live application verification. Test your chosen configuration and recovery workflow before using it for production.

Editorial content reviewed: 2026-10-10

Upstream documentation Template source and license

Choose your next step

Related templates