Search that runs on your own server.

Meilisearch is a server role of its own in Depfloy — provisioning one sets up the service, the firewall and private-network access, so search is not something bolted onto the app server.

Start free trial Read the docs
Meilisearch
Version provisioned
1.11
Runs on
A server you own
Scheduled backups
Supported
Its own server role

Search sits alongside app, database, cache and load balancer as a first-class role, which means it gets its own machine sizing and its own monitoring.

The index is backed up

Rebuilding an index from source is slow and sometimes lossy. A backup schedule dumps the index itself, with retention and restore.

Keys stay in project env

The master key and host are managed as project environment variables, written to the server before the build so search is configured at deploy time.

Search is the feature people notice when it breaks and never when it works. Giving it its own server role means its memory is its own problem, not the application’s.

FAQ

Meilisearch questions

Does this work with Laravel Scout? +
Yes. Point SCOUT_DRIVER at meilisearch and set the host and key in the project's environment; the rest is standard Scout.
How much memory does it need? +
It depends on index size, but search is memory-bound — this is a workload worth putting on its own server so it cannot squeeze the app.
Is the search endpoint public? +
Only if you open it. The usual setup keeps it on the private network with the app querying it internally.

Six other services, provisioned the same way.

Each one is installed, firewalled and monitored from the same console.

PostgreSQL MySQL Redis Valkey ClickHouse

Run Meilisearch on your own server.

7 days free, no credit card. Your provider bills you for the machine; we bill a flat plan.

Start free trial How releases work