Polyer

Meilisearch

Deploy Meilisearch on Polyer to add typo-tolerant full-text search to websites and applications. The template runs one public Meilisearch service in production mode, protected by a generated master key, with its database on a persistent volume at /meili_data. Review the floating latest tag before deploying.

SearchCoolify open catalog

What you can use it for

  • Add search-as-you-type to a product catalog, documentation site or knowledge base.
  • Index records from your application database so users can search and filter them.

What this template creates

meilisearchgetmeili/meilisearch:latest
Public endpoint 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

  • Use the generated master key only to manage API keys, giving browsers a search-only key and backend services an admin key; production mode also disables the built-in search preview.
  • Keep the source data needed to rebuild your indexes, and back up the /meili_data volume or Meilisearch dumps, testing a restore before you rely on them.
  • The getmeili/meilisearch:latest tag floats, and a newer engine may not open existing data without an upgrade step, so pin a version and follow Meilisearch's upgrade process; memory and disk use grow with your indexes.

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

Choose your next step