Self-host Typesense with Levelrail
VerifiedA fast, typo-tolerant search engine API built as a lighter alternative to Elasticsearch.
- Authortypesense
- LicenceGPL-3.0
- Memory512 MiB
- Archarm64
- Services1
How to self-host Typesense
-
Pull the images
One image is pulled on your server.
Show images
typesense/typesense:30.2
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 8108.
-
Fill in the secrets
1 secret is generated and stored encrypted, 1 setting is preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Typesense requirements
- Memory
- About 512 MiB
- Architectures
- amd64 image published, arm64 tested
- Ports
- 8108
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- GPL-3.0, copyleft license
- Verified. Verified on arm64 with image tag 30.2. Our CI ran this exact image version and it answered on its health path. Evidence
- Host ports. It publishes port 8108 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Typesense. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Typesense docs page.
Deploy Typesense your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Typesense from the CLI
levelrail-cli templates deploy typesense --name my-typesense Deploy Typesense with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/typesense/deploy Typesense configuration
Typesense services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| typesense | typesense/typesense:30.2 | 8108 | typesense_data -> /data |
Typesense environment variables
| Variable | Service | Value |
|---|---|---|
| TYPESENSE_API_KEY | typesense | Generated at deploy |
| TYPESENSE_DATA_DIR | typesense | Preset by the template |
Ports and volumes
- Ports
- 8108
- Volumes
- 1 named mount: typesense_data -> /data
Typesense FAQ
How much memory does Typesense need?
The catalog lists about 512 MiB of memory for Typesense.
Does Typesense run on arm64?
For Typesense, arm64 is tested; amd64 is image published.
What licence is Typesense under?
Typesense is licensed under GPL-3.0, which is copyleft, so changes you distribute must be shared under the same terms.
Does Typesense need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does Typesense use?
Typesense listens on port 8108 inside the stack.
Where does Typesense keep its data?
In a named volume: typesense_data mounted at /data.
Can I deploy Typesense on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id typesense for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image typesense/typesense:30.2 is what you deploy there.