Deploy Weaviate
Weaviate vector database with API key auth, RBAC and a persistent volume
Just deployed
/var/lib/weaviate
Deploy and Host Weaviate on Railway
Weaviate is an open-source vector database written in Go. It stores objects together with their vector embeddings and runs fast nearest-neighbour, keyword (BM25) and hybrid search over them, with filters, multi-tenancy and built-in modules that call embedding and LLM providers for you. Developers use it as the retrieval layer for RAG and semantic search.
About Hosting Weaviate
Hosting Weaviate means running one stateful server that keeps its collections, indexes and schema on disk, so the data directory needs persistent storage that survives restarts and redeploys. The node needs a fixed name, because its Raft schema store is keyed on it and a container's hostname changes on every deploy. The API must be protected with an API key before it is exposed to the internet. This template builds the official Weaviate image (pinned by version and digest) from a GitHub repo, puts data and backups on a Railway volume, generates a 48-character API key, turns anonymous access off, and serves the REST and GraphQL API on a public HTTPS domain.
Common Use Cases
- Retrieval-augmented generation (RAG): store document chunks with embeddings and fetch the relevant context for an LLM
- Semantic and hybrid search over products, documentation or support tickets
- Recommendations, deduplication and classification on text or image embeddings
Dependencies for Weaviate Hosting
- Weaviate v1.40.5, the official
semitechnologies/weaviateimage - A Railway volume for collections, the schema and backups
Deployment Dependencies
- Weaviate documentation: https://docs.weaviate.io/weaviate
- Weaviate environment variables: https://docs.weaviate.io/deploy/configuration/env-vars
- Weaviate releases: https://github.com/weaviate/weaviate/releases
- Template source and changelog: https://github.com/aalfath/weaviate-railway-template
Implementation Details
- The API key is in the service variable
AUTHENTICATION_APIKEY_ALLOWED_KEYS. Send it asAuthorization: Bearer KEYon every request. It belongs to the useradmin, the RBAC root user, who can create further users and roles. Anonymous access is off, and the container refuses to start without a key. - From outside Railway, the REST and GraphQL API is at
https://YOUR-DOMAIN. The gRPC port (50051) is only on the private network. The v4 Python and v3 TypeScript clients need gRPC for queries, so run them inside Railway, or add a TCP proxy for port 50051 yourself (plain gRPC, no TLS). - Other Railway services connect over the private network: host
${{Weaviate.RAILWAY_PRIVATE_DOMAIN}}, HTTP port 8080, gRPC port 50051, key${{Weaviate.AUTHENTICATION_APIKEY_ALLOWED_KEYS}}. - API-based modules (OpenAI, Cohere, Anthropic, Google, Voyage AI and others) are enabled: pick a vectorizer per collection and pass your provider key as a request header or service variable such as
OPENAI_APIKEY. Filesystem backups go to/var/lib/weaviate/backupson the volume. - Any other Weaviate setting can be added as a service variable, for example
DISABLE_TELEMETRY=true. - Updates: a new Weaviate version in the template repo shows up as an "update available" notice in your project. Take a backup first, and upgrade one minor version at a time.
Why Deploy Weaviate on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying Weaviate on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content

