Fully Managed Meilisearch
as a Service

Deploy Meilisearch as a fully managed service starting at €9/mo. Get automated backups, SSL, updates, support and monitoring included.

Meilisearch is an open-source search engine written in Rust: typo-tolerant full-text queries, filters and facets, custom ranking rules, and hybrid keyword-and-vector retrieval, combining the response times teams expect from a metered search API with the cost predictability and data control of software you run yourself.

✓Free 7-day trial  ✓99.9% Uptime SLA  ✓No credit card  ✓Cancel anytime

✓Free 7-day trial  ✓99.9% Uptime SLA
✓No credit card  ✓Cancel anytime

Meilisearch

Meilisearch

STARTING AT

€9/month
Automated Backups
Monitoring
Automated Updates
Auto SSL

USAGE

Unlimited
Human Support
Custom Domains
Terminal Access
File Manager Access
Deploy in your region — 21 locations worldwide
GermanyFinlandNetherlandsUKSwedenUnited StatesCanadaSingaporeJapanAustraliaBrazilSouth Africa+9 more →
Meilisearch Preview Image

ABOUT THE SOFTWARE

What is Meilisearch

Meilisearch is an open-source search engine built for typo-tolerant, sub-100ms queries over structured records. It ships as one binary, stores its index in an embedded key-value store, and exposes everything (documents, settings, keys, tasks) through a single HTTP API.

The project is maintained by Meili SAS in France and released under the MIT licence for the community build, which is what runs on DANIAN. A separate enterprise licence covers a small set of files that add horizontal sharding and remote snapshot streaming; those are compiled out of the build we ship, so nothing on your instance depends on a paid grant. The engine is written in Rust and ships as one static binary: no runtime dependencies and no separate database.

Storage sits in an embedded memory-mapped key-value store. That is why it is fast on read and why it behaves unusually on disk: pages freed by deletes are marked reusable internally but never handed back to the operating system, so the store only grows across re-imports. Writes are asynchronous: every upload, settings change, and key operation becomes a task in a queue you can poll, so a healthy process and a stalled index are two different conditions.

FEATURES

What Meilisearch does

Meilisearch is a search engine, not a general datastore. It indexes records you push to it and answers queries in milliseconds, with relevance controls configured per index rather than per query.

Typo tolerance

Matches records despite misspellings, with the edit-distance thresholds configurable per index and disableable on fields such as SKUs where a near miss is wrong.

Filters and facets

Declared filterable attributes support boolean expressions at query time and facet-count distributions for building category counters alongside results.

Custom ranking rules

The relevance pipeline is an ordered, editable list. Insert business signals (price, recency, stock, popularity) at the position where they should override textual relevance.

Synonyms and stop words

Map equivalent terms in both directions and strip high-frequency noise words per index, so vocabulary differences between your catalogue and your customers stop costing results.

Hybrid keyword and vector search

Combine lexical matching with embedding similarity in one request, with a ratio you control, for queries phrased as questions rather than keywords.

Federated multi-index search

Query several indexes in a single request and receive one merged, ranked result set, the basis for a search bar that covers products, articles, and help pages at once.

Tenant tokens

Issue signed tokens that carry a filter, so one shared index can serve many customers while each one can only retrieve its own rows.

Geo filtering and sorting

Records carrying coordinates can be filtered by radius or bounding box and sorted by distance from a point supplied at query time.

WHAT'S ALWAYS INCLUDED

Every app. Fully managed.
Nothing extra to pay for.

Every app on DANIAN ships with the same operational baseline. You do not choose a backup add-on or a monitoring tier. Hosting, patching, backups, SSL, and support are part of the €9, and they apply to Meilisearch the same way they apply to everything else in the catalog.

Automatic updates and patches

Apps run the latest stable version. Security patches applied silently, with rollback if needed.

Daily off-site backups

Multiple daily backups in redundant off-site locations. One-click restore if anything goes wrong.

24/7 uptime monitoring

Continuous monitoring with instant alerting. We respond before you notice.

SSL, firewall, DDoS protection

Auto-renewing SSL, hardened firewall rules, DDoS mitigation on every deployment.

Performance and scaling

We monitor resource usage continuously. When your app needs more headroom, we flag it and upgrade with your explicit approval.

Dedicated engineering support

Real engineers by email and ticket. DNS, SMTP & migration help. All included in €9.

WHY MANAGED

Why teams pick managed Meilisearch

Metered search vendors have moved AI ranking and semantic retrieval into higher-priced tiers, charging several times the base rate per thousand requests. Running the engine yourself removes that meter. It also hands you an index whose failure modes are specific and unforgiving.

Installing Meilisearch is easy: one binary, one port, one master key. The second month is the hard part. The indexer targets roughly two thirds of available memory, and the flag meant to cap it is a target rather than a hard ceiling, so a bulk import on an undersized box gets killed part-way through. Disk is the other trap: a few hundred megabytes of records can become several gigabytes of index, and because freed pages are never returned, a nightly full re-import will fill a right-sized volume within weeks.

The key model surprises people too. Every API key derives from the master key, so rotating or losing that one value invalidates every key your applications hold. Front-end code needs a search-scoped key or a tenant token; shipping the master key to a browser hands a stranger write access. Re-indexing in place is the third trap: clearing an index and re-uploading leaves a window where the site returns nothing, which is why the engine has an atomic swap endpoint most first deployments never find.

On DANIAN those decisions are already made. We provision disk at roughly twelve times the records you expect to load, so re-imports and snapshots have room. We cap indexing memory below the container ceiling and hold indexing threads at half the cores, so a large import slows search instead of killing the process. We hold the master key as a managed secret and issue search-scoped keys for browser use. We snapshot before every version change.

REVIEWS

Hear from customers ​like you​​​​​​​

Successful businesses and professionals around the world rely on DANIAN every day

USE CASES

Three teams who run Meilisearch on DANIAN

Three shapes of team account for most Meilisearch instances here: a catalogue that stays searchable while it changes, a documentation site that must never return empty, and an archive added to slowly and queried unpredictably.

6-PERSON ONLINE RETAILER

Left a metered search API when AI ranking moved up a tier

About 1.2 million product records in a region close to their warehouse. Stock and price arrive from their commerce backend every fifteen minutes as partial document updates. Custom ranking puts in-stock items above textual relevance. Full re-builds run nightly into a second index and go live through an atomic swap.

4-PERSON DEVELOPER TOOLS COMPANY

Documentation search that survives a docs deploy

Their static-site build pushes every page into a staging index, waits for the task queue to drain, then swaps it into place. The widget in the browser holds a search-scoped key that cannot write. Roughly 9,000 pages across three product lines, queried from a single federated request.

12-PERSON MEDIA ARCHIVE

Faceted search over scanned material with portable exports

Around 680,000 catalogued items with dates, places, rights status, and coordinates. Facets drive the browse interface; geo filtering drives the map. They take a version-portable dump quarterly and keep it themselves, separate from the snapshots we run, because the archive outlives any single vendor.

COMPARISON

Four ways to run Meilisearch

Metered search bills on two meters at once, records stored and requests served, so the price moves when your catalogue grows and again when traffic does. The four paths below hold the workload steady and vary only who operates it.

PathSmall indexMid indexLarge indexWhat you operate
Metered search API (Algolia)~$20/mo~$280/mo~$605/moNothing. You also cannot see the index, and AI ranking sits in a higher-priced tier.
Self-host on a VPS$24/mo$48/mo$96/moEverything: sizing, disk headroom, key rotation, snapshots, version upgrades, on-call.
Home server€260 once + power€260 once + power€420 once + powerA mini-PC with 16 GB RAM and an NVMe drive, plus your own uplink, UPS, and off-site copy.
DANIAN managed Meilisearch€9/mo€9/mo€9/moNothing. Flat price at every scale point; you keep API and file access to the instance.

Scale points: 100k records / 50k searches per month, 500k records / 250k searches, 1M records / 500k searches.

BY INDUSTRY

Meilisearch for specific industries

Search infrastructure inherits the rules of whatever it indexes. A product catalogue, a public documentation portal, a cultural archive, and a multi-tenant application each put a different constraint on how the index is configured and who is allowed to query it.

Marketplaces and retailers trading inside the single market fall under the Platform-to-Business Regulation, which requires the main parameters that determine result ordering to be described in plain language and kept current. Meilisearch suits that duty because ranking is an explicit ordered list of rules rather than a learned black box, so the description you publish can be generated from the settings you actually run. On DANIAN the ranking-rules and filterable-attributes settings stay exportable through the API on request, so a change to result ordering leaves a dated record you can point at. A working pattern: price and stock updates arrive as partial document edits every fifteen minutes, while the nightly rebuild runs into a shadow index and goes live through an atomic swap. On a catalogue of a million records that keeps the search bar answering through a rebuild that would otherwise leave minutes of empty results.

Public-facing documentation is increasingly written against WCAG 2.1 AA, and for public-sector suppliers against the harmonised standard EN 301 549, both of which reach the search box: results must be reachable by keyboard, announced to assistive technology, and readable without colour alone. That is front-end work, but it rests on a back end that never returns an empty page mid-deploy. On DANIAN the key we issue for a documentation instance is search-scoped, so a widget on a public page cannot write, delete, or read the key list. The pattern that works: the docs build pushes into a staging index, polls the task queue until it drains, then calls the swap endpoint. For a portal of 9,000 pages that swap is one task, so the site moves to the new index between two requests rather than across a rebuild window.

Archives run their catalogues against records-management practice such as ISO 15489-1, which treats the finding aid as something that must remain readable and transferable for decades, longer than any search vendor can be assumed to exist. Meilisearch answers with two export shapes, and the distinction matters: a snapshot is an exact copy of the store that only the same engine version opens, while a dump is a portable description any later version can re-import. On DANIAN we run snapshots for recovery, and archives typically take their own dump quarterly and keep it themselves. For roughly 680,000 items a dump re-imports in minutes rather than seconds, so that restore is planned as a maintenance window, not a hot failover.

An application that indexes several customers' data in one place is holding an access-control problem, and the OWASP Application Security Verification Standard is the usual yardstick: every request must be constrained server-side, never by a filter the client could edit. Meilisearch fits because tenant tokens are signed server-side and carry the filter inside the token, so a browser holding one cannot widen its scope. On DANIAN the parent search key is a managed secret and no write-capable key goes in a client bundle. The pattern: your backend mints a short-lived tenant token per session, scoped to one filterable field. One shared index then serves every customer, keeping a thousand-tenant product on one €9 instance.

FAQ

Frequently asked questions

Three sets below: how the engine behaves in production and how we configure it, how records and settings move from wherever they live now, and how billing, support, and the platform work.

01

Technical and configuration

Indexing decides this, not searching. Serving queries is cheap; building the index is memory-hungry, and the engine targets roughly two thirds of available memory while it works. We start instances with enough headroom that a bulk import of a million records finishes rather than being killed part-way.
The embedded store never returns freed pages to the operating system. Deletes and re-imports mark space reusable internally, so the file only grows. A few hundred megabytes of records commonly becomes several gigabytes on disk. We provision at roughly twelve times your expected corpus, plus snapshot headroom.
We cap indexing memory below the container ceiling rather than trusting the default, and hold indexing threads at half the cores. The engine treats that setting as a target, not a hard limit, so the ceiling has to sit under the real one. The result is a slower import, not a dead process.
Yes, and it is the most useful thing to know here. Clearing an index and re-uploading leaves a live window returning nothing. Build into a second index instead and call the swap endpoint, which exchanges the two atomically as one task.
Every API key derives from the master key, so resetting it invalidates all of them and every application holding one stops until reissued. We hold the master key as a managed secret rather than in an environment file you might rotate by accident, and reissue derived keys on request.
A search-scoped key is; a master or admin key never is. We issue a key limited to search on named indexes for anything that ships to a browser. If one index serves multiple customers, use a tenant token: it is signed on your server and carries the filter inside it.
No. Both sit under a separate enterprise licence from the project and are compiled out of the community build we run, so nothing on your instance depends on a paid grant. A single well-sized instance covers catalogues far larger than most teams bring us. If you outgrow it, we will say so.

02

Migration and onboarding

21 datacenter locations across six continents. You choose the region at provisioning. Application data sits in the region you choose; pick whichever is closest to your users or matches your data-residency preference.
Yes. Request a region migration from the dashboard and we run the move in the background. The system emails you when the migration completes; total transfer time depends on data volume but typical instances finish in a few hours. There is no extra charge for a region change.
Yes. Full data export is available at any time, in a portable format you can bring to any infrastructure.
Yes. Attach any domain or subdomain you control and the certificate is issued and renewed automatically. If you would rather not touch DNS, tell us the registrar and we will give you the exact record to add, or walk through it with you.

03

Billing, support, and platform

€9 covers everything we do for that app: hardware in the region you choose, daily off-site backups with one-click restore, automatic security patches and version upgrades, 24/7 monitoring, SSL and firewall, and engineering support on email and the ticket section in the client portal. There are no setup fees or hidden line items. For more info see our Pricing page.
If you decide to continue, we charge €9/app/month from day 8. If you don't, the trial ends and you can export your data. No card is required for the trial, and we never auto-charge you without explicit consent.
No. The €9/month is flat regardless of how many users log into your app. Add 5 users or 50; the price doesn't change.
24/7 email and ticket support, both staffed by engineers who run the systems. We handle DNS configuration, SMTP setup, app integrations, performance tuning, troubleshooting, and migration help. Response time is typically under an hour. There is no tier system — every customer gets the same support.
Yes. Cancel from the dashboard. We don't charge a cancellation fee, we don't lock data, and we will export your data to you on request before deletion. data to you on request before deletion.
Every customer instance is backed up daily to a separate region from the primary. We test restores. You can request a restore at any backup point within the retention window — usually 7 days for daily backups.
Your application data sits in the region you choose at provisioning — 21 datacenter locations across six continents. Account-level data (billing, account email, support ticket history) is processed centrally. Application data region is picked by you, per app.
99.9% uptime SLA on every app, every tenant. Service credits are documented at danian.co/service-level-agreement. The status page is located at status.danian.co.
When your tenant approaches the resource ceiling — the base tier holds 1 vCPU/RAM, 30 GB storage — we notify you. Resource upgrades happen with your explicit consent; we will not upgrade your tenant or charge you without it.
We wait. We don't suspend the app or delete your data on the first failed charge. We email you, you fix the card on file, and we continue.
Invoices can be downloaded from the billing dashboard in PDF the day each charge succeeds. EU VAT is added where applicable and the VAT-reverse-charge regime applies for VAT-registered businesses with a valid number.
150+ open-source apps across automation, team chat, file sync, analytics, AI, password management, email marketing, dev tools, project management, smart home, CMS, and federated social. See the full catalog →
Yes. Every instance comes with a web-based terminal and a file manager in your DANIAN management dashboard. Useful for managing your data and customizations.
Resources scale with your usage. If your app needs more vCPU, RAM, or storage, we add it — and we ask first before any change to your plan. €9 is the floor; resource-heavy workloads may price higher, but you'll always know in advance.
Yes. We have both a Partner program and an Affiliate program available. Anybody can sign up.
No contract. No minimum commitment. Cancel anytime from the dashboard with one click. The 7-day free trial requires no credit card. After the trial converts to paid, you can still cancel at any month without notice or penalty.

DEPLOY IN YOUR REGION

21 datacenter locations on six continents

Pick the region closest to your users.

United States, Germany, Finland, Singapore, Australia, Brazil, Canada, Netherlands, UK, Spain, Italy, France, Sweden, Malaysia, India, Japan, Mexico, Poland, South Korea, Chile, South Africa and more coming soon

Global Reach Map

Try managed Meilisearch for 7 days

No card. Cancel from the dashboard.