Meilisearch

Meilisearch is a fast, open-source search engine. Enabling this service gives your project one or more dedicated Meilisearch instances to power search for your application.

Enabling Meilisearch

Meilisearch is an add-on service and is not enabled by default. For now, our support team sets up each Meilisearch instance for your project. Self-service provisioning is on our roadmap, but isn't available yet.

INFO

To use Meilisearch for your project, please contact our support team with your project ID and a brief description of your use case. Our team will set up a dedicated Meilisearch instance for your project and configure the connection details. If you need more than one instance (for example, one per environment), just ask.

Viewing your configuration

Once Meilisearch has been set up for your project, you can view every instance under Services > Meilisearch. For each instance, you'll find:

• The host, the base URL of that Meilisearch instance
• The master key, which grants full, unrestricted access to that instance

WARNING

Never use a master key directly in your application. It grants full access to that instance, including the ability to create and delete API keys. Use it only, from a trusted location, to retrieve or create a more restricted key, then configure your application with that key instead.

Getting the right key for your application

Meilisearch automatically creates a Default Search API Key (search-only, safe for frontend use) and a Default Admin API Key (full access except managing keys themselves, for server-side use) on top of each instance's master key. See Meilisearch's guide to obtaining API keys on a self-hosted instance for how to retrieve them, and details on these and other default keys.

Use an instance's master key from Hubble Studio together with Meilisearch's API keys documentation to retrieve the Default Search API Key for frontend search, or the Default Admin API Key for server-side indexing, and put that key into your application's Meilisearch client configuration instead of the master key. If neither default key fits, create a custom, more restricted key the same way.

Hubble Studio does not create, list, or delete any of these keys for you.

WARNING

Because additional API keys are created and deleted directly against each Meilisearch instance, Hubble Studio has no way of knowing which ones currently exist. Keep track of them yourself, for example in your own secrets management.