Self-host Weaviate with Levelrail
An open-source vector database with hybrid search, built-in modules, and a GraphQL and REST API.
- Authorweaviate
- LicenceBSD-3-Clause
- Memory1 GiB
- Archarm64
- Services1
How to self-host Weaviate
-
Pull the images
One image is pulled on your server.
Show images
semitechnologies/weaviate:1.39.6
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 8080.
-
Fill in the secrets
1 secret is generated and stored encrypted, 7 settings are 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.
Weaviate requirements
- Memory
- About 1 GiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8080
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- BSD-3-Clause, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 8080 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 Weaviate. 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 Weaviate docs page.
Deploy Weaviate your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Weaviate from the CLI
levelrail-cli templates deploy weaviate --name my-weaviate Deploy Weaviate with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/weaviate/deploy Weaviate configuration
Weaviate services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| weaviate | semitechnologies/weaviate:1.39.6 | 8080 | weaviate_data -> /var/lib/weaviate |
Weaviate environment variables
| Variable | Service | Value |
|---|---|---|
| AUTHENTICATION_ANONYMOUS_ACCESS_ENABLED | weaviate | Preset by the template |
| AUTHENTICATION_APIKEY_ALLOWED_KEYS | weaviate | Generated at deploy |
| AUTHENTICATION_APIKEY_ENABLED | weaviate | Preset by the template |
| AUTHENTICATION_APIKEY_USERS | weaviate | Preset by the template |
| CLUSTER_HOSTNAME | weaviate | Preset by the template |
| DEFAULT_VECTORIZER_MODULE | weaviate | Preset by the template |
| PERSISTENCE_DATA_PATH | weaviate | Preset by the template |
| QUERY_DEFAULTS_LIMIT | weaviate | Preset by the template |
Ports and volumes
- Ports
- 8080
- Volumes
- 1 named mount: weaviate_data -> /var/lib/weaviate
Weaviate FAQ
How much memory does Weaviate need?
The catalog lists about 1 GiB of memory for Weaviate.
Does Weaviate run on arm64?
For Weaviate, an arm64 image is published; amd64 is image published.
What licence is Weaviate under?
Weaviate is licensed under BSD-3-Clause, which is permissive, with few conditions on reuse.
Does Weaviate need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does Weaviate use?
Weaviate listens on port 8080 inside the stack.
Where does Weaviate keep its data?
In a named volume: weaviate_data mounted at /var/lib/weaviate.
Can I deploy Weaviate on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Weaviate, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image semitechnologies/weaviate:1.39.6 is what you deploy there.