Weaviate hosting

A vector database with hybrid search and built-in vectorization modules.

Vector & dataBSD-3-Clausefrom $11.99/mo
In short

Weaviate hosting at AIHostBox means a dedicated, single-tenant Weaviate instance on our infrastructure: we install it, pin it to a reviewed release, put it behind TLS on your domain, back it up nightly and keep it patched. Plans start at $11.99 per month and the admin account, the data and any API keys are yours.

Hybrid searchVectorizer modulesGraphQLMulti-tenancy

Weaviate is an open-source vector database written in Go by Weaviate B.V. and released under the BSD-3-Clause licence. It stores your objects and their vectors together, so a single query can filter on properties, rank by semantic similarity and blend in BM25 keyword scores. That hybrid search, tunable with a single alpha parameter, is its best-known feature, and the reason teams pick it when pure vector search keeps missing exact product codes or names.

The second difference is its module system. Rather than embedding documents in your own pipeline, you can enable a vectoriser such as text2vec-openai or text2vec-ollama and let Weaviate create the vectors on import, then use generative modules to answer questions over the results. A database like this is meant to be always on and reachable by every service that writes to it, which is exactly the job a laptop does badly.

Weaviate hosting plans

PlusRecommended minimum
4 GB RAM · 2 vCPU · NVMe
$11.99/mo
Order
ProTeams & heavier load
8 GB RAM · 3 vCPU · NVMe
$18.99/mo
Order

Every plan is a dedicated single-tenant instance with NVMe storage, nightly off-box backups, TLS and managed patching. Quarterly, semi-annual and annual terms are discounted at checkout. Model tokens are not included — you bring your own key.

How we run Weaviate

We run a single Weaviate node from the official cr.weaviate.io image, exposing REST and GraphQL on port 8080 and gRPC on 50051, with PERSISTENCE_DATA_PATH on NVMe storage; there is no separate database, as Weaviate stores objects, vectors and indexes itself.

What we configure for you

  • AUTHENTICATION_ANONYMOUS_ACCESS_ENABLED=false and API keys via AUTHENTICATION_APIKEY_ALLOWED_KEYS
  • AUTHORIZATION_ENABLE_RBAC with a root user, if you want per-key roles
  • ENABLE_MODULES and DEFAULT_VECTORIZER_MODULE for the vectoriser you choose
  • BACKUP_FILESYSTEM_PATH or BACKUP_S3_BUCKET for Weaviate’s native backup API
  • GOMEMLIMIT or LIMIT_RESOURCES so imports slow down instead of running out of memory
  • CLUSTER_HOSTNAME fixed, so the node keeps its identity across restarts

Which plan fits

Plus (4 GB) holds roughly 700,000 vectors at 384 dimensions, or about 175,000 at 1,536 dimensions, before quantisation and with room left for the operating system. Pro (8 GB) holds around two and a half times as much and gives headroom for large batch imports. Beyond that, product quantisation or a bigger plan is needed.

The honest limits

This is a single node, so replication across nodes and automatic failover are not part of these plans. Vectoriser modules that run a model locally use the same CPU and RAM as the database, so API-based embeddings are usually the better choice here.

What people run Weaviate for

Search that needs both

Exact keyword matches and semantic similarity in one ranked result.

Ingestion without a pipeline

Let the module embed documents as they arrive.

Per-customer isolation

Use multi-tenancy to keep each customer’s objects in its own shard inside one collection.

Licence and version policy

ItemPosition
Upstream licenceBSD-3-Clause
Sold as managed hostingYes
TenancySingle tenant — one customer per instance
PatchingCritical advisories within 24 hours, high severity within 72

Our full position on licences, including the applications we decline to sell, is on the licensing page.

Reading on Weaviate

Works well with Weaviate

More Vector & data we host

Questions

Weaviate hosting: your questions

Which client libraries and APIs can I use?
Weaviate serves a REST API and GraphQL on port 8080 and a gRPC API on port 50051, which the current Python client uses for queries and batch imports. Official clients exist for Python, TypeScript, Go and Java, and most RAG frameworks, including LangChain, LlamaIndex, Langflow and Dify, have Weaviate integrations.
How is access controlled?
We turn anonymous access off and enable API-key authentication with AUTHENTICATION_APIKEY_ENABLED, AUTHENTICATION_APIKEY_ALLOWED_KEYS and AUTHENTICATION_APIKEY_USERS. Role-based access control is available through AUTHORIZATION_ENABLE_RBAC, so you can give an ingestion service write access and a front-end read-only access with separate keys.
How much data fits in memory?
Weaviate’s own rule of thumb is about twice the raw size of your vectors. One million 384-dimension vectors need roughly 3 GB; the same count at 1,536 dimensions needs about four times that. Product quantisation cuts memory substantially at some cost to recall, which is worth testing on your data.
Which vectoriser should I use without a GPU?
On CPU plans, the practical options are an API-based module such as text2vec-openai with your own key, or text2vec-ollama pointed at an Ollama instance running a small embedding model. The transformer inference container works on CPU too, but it competes with Weaviate for the same RAM.
How do backups and restores work?
Besides our nightly off-box copy of the data directory, Weaviate has its own backup API. With the backup-filesystem or backup-s3 module enabled, POST /v1/backups/{backend} creates a consistent backup and /restore brings one back, so you can snapshot before a risky schema change or move collections to another instance.

Run Weaviate without running a server

A dedicated Weaviate instance, deployed and maintained by us. Month to month, cancel whenever.