---
title: "Deploy Meilisearch"
description: "A fast search engine with a modern admin UI for easy management."
category: "Storage"
url: https://railway.com/deploy/meilisearch-railway-template
---

# Deploy Meilisearch

A fast search engine with a modern admin UI for easy management.

**[Deploy Meilisearch on Railway](https://railway.com/template/meilisearch-railway-template)**

- **Creator:** INF Labs
- **Category:** Storage

## Template content

### meilisearch-ui

- **Image:** riccoxie/meilisearch-ui:latest
- **Public domain:** Yes

### meilisearch https://www.gravatar.com/avatar/26a7f7da104e1eaa43e3f365a13b027a?s=120&r=g&d=404

- **Image:** getmeili/meilisearch:latest
- **Public domain:** Yes

## Documentation

# Deploy and Host Meilisearch on Railway

Meilisearch is a fast, open-source search engine designed for modern applications. It provides typo-tolerant full-text search, filtering, faceting, customizable ranking, and powerful search APIs with a developer-friendly experience.

This Railway template includes **Meilisearch with a web-based administration UI**, making it easy to manage indexes, documents, settings, and search configuration directly from your browser.

## About Hosting Meilisearch

This template deploys a complete self-hosted Meilisearch environment on Railway using the official Meilisearch Docker image together with Meilisearch UI.

Meilisearch runs as the primary search engine and stores indexes and application data on a persistent Railway Volume. Meilisearch UI provides a browser-based dashboard for managing the deployed instance.

The stack is lightweight and self-contained. It does not require PostgreSQL, Redis, or any external database because Meilisearch manages its own indexes and persistent data.

## Included Services

* **Meilisearch** — Full-text search engine and search API
* **Meilisearch UI** — Web-based interface for managing Meilisearch
* **Railway Volume** — Persistent storage for indexes and Meilisearch data

## Common Use Cases

* Add fast full-text search to websites and applications
* Build product search for e-commerce platforms
* Search documentation, articles, and knowledge bases
* Implement autocomplete and instant search
* Create searchable application databases
* Build faceted and filtered search interfaces
* Manage and inspect Meilisearch indexes visually
* Develop search APIs for web and mobile applications

## Dependencies for Meilisearch Hosting

* Meilisearch
* Meilisearch UI
* Persistent Railway Volume

No PostgreSQL or Redis instance is required.

## Meilisearch Web UI

The template includes **Meilisearch UI**, an open-source administration dashboard that provides:

* Index management
* Document management
* Search testing
* Index settings management
* Multiple Meilisearch instance support
* Singleton instance support
* Browser-based administration

After deployment, open the public domain assigned to the **Meilisearch UI** service.

The UI can then connect to the Meilisearch instance deployed by this template.

## Persistent Storage

Meilisearch stores its indexes and database files in:

```text
/meili_data
```

A Railway Volume is mounted to this directory so your indexes and documents persist across deployments and container restarts.

Do not remove the volume if you want to retain your Meilisearch data.

## Important Environment Variables

### Meilisearch

`MEILI_MASTER_KEY`

The master administrative key for the Meilisearch instance. The template automatically generates this value during deployment.

Keep this key private because it provides administrative access to your Meilisearch instance.

`MEILI_ENV`

Runs Meilisearch in production mode.

`MEILI_NO_ANALYTICS`

Controls anonymous Meilisearch telemetry.

### Meilisearch UI

The UI can be configured to connect to the Meilisearch instance using singleton mode.

The important configuration includes:

* `SINGLETON_MODE`
* `SINGLETON_HOST`
* `SINGLETON_API_KEY`

For security reasons, avoid exposing a Meilisearch master key unnecessarily in browser-side configuration.

## After Deployment

1. Wait for both **Meilisearch** and **Meilisearch UI** services to become healthy.
2. Open the public URL of the Meilisearch UI service.
3. Connect the UI to your Meilisearch instance if it is not already configured.
4. Use your Meilisearch API key when authentication is required.
5. Create your first index.
6. Add documents and test your search queries directly from the UI.
7. Use the Meilisearch public endpoint from your applications, SDKs, or APIs.

## Security Notice

Meilisearch should always be protected with a strong master key when exposed publicly.

Do not expose your master key in frontend applications or client-side JavaScript.

For production applications, create scoped Meilisearch API keys with only the permissions required by each application.

The included Meilisearch UI communicates with Meilisearch from the browser. When using the UI from another domain, ensure the deployment configuration permits the required cross-origin requests.

## Meilisearch vs Alternatives

| Feature                       | Meilisearch | Elasticsearch | Typesense | PostgreSQL Full-Text |
| ----------------------------- | ----------- | ------------- | --------- | -------------------- |
| Full-text search              | ✅           | ✅             | ✅         | ✅                    |
| Typo tolerance                | ✅           | ✅             | ✅         | Limited              |
| Instant search                | ✅           | ✅             | ✅         | Limited              |
| Faceted search                | ✅           | ✅             | ✅         | Limited              |
| Simple deployment             | ✅           | ❌             | ✅         | ✅                    |
| Built for application search  | ✅           | ⚠️            | ✅         | ❌                    |
| Dedicated search API          | ✅           | ✅             | ✅         | ❌                    |
| Lightweight self-hosting      | ✅           | ❌             | ✅         | ⚠️                   |
| Web admin UI in this template | ✅           | ✅             | ⚠️        | ❌                    |

Meilisearch is particularly useful when you want a dedicated application search engine without the operational complexity commonly associated with larger search infrastructure.

## Why Deploy Meilisearch 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.

Deploying Meilisearch on Railway provides:

* Persistent storage using Railway Volumes
* Automatic HTTPS domains
* Simple environment variable management
* Easy container upgrades and redeployments
* Integrated logs and monitoring
* A ready-to-use Meilisearch administration UI
* No external database required

This template provides a straightforward way to run your own production-ready Meilisearch search infrastructure with a visual management interface.


## 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/meilisearch-railway-template