Application hosting

Hosting Meilisearch

Meilisearch is a search engine that can be self-hosted as a binary or container. The official guide requires a master key for production and stores an index on disk; capacity depends on indexed data and query load.

Min vCPU
Depends on workload
Min memory
Depends on workload
Min storage
Depends on workload

Must have

Hard prerequisites

No universal server-size prerequisite is published. Check the exact release and configuration before you deploy.

Recommended

Documented guidance

No further general recommendations are published for this version.

Capacity depends on your workload

The cited quick-start material does not establish a production CPU/RAM/disk minimum. Index size, ranking settings, query volume, and update batches affect capacity.

We only compare what providers publish. A RAM figure alone can't confirm compatibility or production capacity.

Deploy with

Supported paths

  • Official self-hosted binary
  • Official container image
  • Meilisearch Cloud is a separate hosted service

The host must provide

Runtime

Master key
Required by the official guide for production deployments
Persistent storage
Writable, persistent location for the search database/index
Client
Use a Meilisearch SDK or HTTP client; public-facing apps should use scoped API keys rather than the master key

Storage

Persistent data

Persist the database/index path across restarts and deployments. Reserve space for index growth and backups; the official quick start does not prescribe one disk size.

Step by step

Meilisearch deployment outline

  1. Install the selected distribution

    Use an official installation option for the host and pin a release appropriate to the deployment.

    Official instructions
  2. Set production authentication

    Configure a private master key before exposing the service. Give public applications only the restricted search keys they need.

    Official instructions
  3. Persist the index

    Place the database/index on persistent storage and include it in backups and restore tests.

    Official instructions

Security

Before you go public

  • A production master key is required; never put it in browser code.
  • Use limited API keys for client access and restrict the management API to trusted services.
  • Keep the index on persistent storage and test restores.

Cost

Beyond the server price

  • Budget for compute, index storage, backups, and outbound traffic as the dataset grows.
  • Self-hosted software infrastructure costs are separate from Meilisearch Cloud pricing.

Matching plans

Plans with published evidence

DigitalOcean

CPU-Optimized Regular Droplet · 2 vCPU / 4 GiB

2vCPU
4 GiBRAM
25 GiBStorage
4 TBTransfer
  • Dedicated CPU
  • SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

DigitalOcean

General Purpose Droplet · 2 Dedicated vCPU / 8 GB

2vCPU
8 GBRAM
25 GBStorage
4 TBTransfer
  • Dedicated vCPU (100% allocatio...
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Google Cloud

Compute Engine e2-medium · 2 vCPU / 4 GB

2vCPU
4 GBRAM
—Storage
—Transfer
  • Shared vCPU (1.00 sustained)
  • Persistent Disk (billed separa...
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Google Cloud

Compute Engine e2-small · 2 vCPU / 2 GB

2vCPU
2 GBRAM
—Storage
—Transfer
  • Shared vCPU (0.50 sustained)
  • Persistent Disk (billed separa...
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CCX13 (Germany and Finland)

2vCPU
8 GBRAM
80 GBStorage
20 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CCX23 (Germany and Finland)

4vCPU
16 GBRAM
160 GBStorage
20 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CCX33 (Germany and Finland)

8vCPU
32 GBRAM
240 GBStorage
30 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CCX43 (Germany and Finland)

16vCPU
64 GBRAM
360 GBStorage
40 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CCX53 (Germany and Finland)

32vCPU
128 GBRAM
600 GBStorage
50 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CCX63 (Germany and Finland)

48vCPU
192 GBRAM
960 GBStorage
60 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CPX11 (US locations)

2vCPU
2 GBRAM
40 GBStorage
1 TBTransfer
  • Shared AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CPX12 (Germany and Finland)

1vCPU
2 GBRAM
40 GBStorage
20 TBTransfer
  • Shared AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Want the full monthly bill? Use the hosting cost calculator. It keeps unknown charges visible.